{ "$schema": "https://schemastore.azurewebsites.net/schemas/json/sarif-2.1.0-rtm.5.json", "version": "2.1.0", "runs": [ { "tool": { "driver": { "name": "CWE V4.4", "informationUri": "https://cwe.mitre.org/data/published/cwe_v4.4.pdf" } }, "columnKind": "utf16CodeUnits", "taxonomies": [ { "guid": "7D699257-C37D-4A10-9C98-D7DB481F1A8B", "name": "CWE V4.4", "organization": "MITRE", "shortDescription": { "text": "The MITRE Common Weakness Enumeration" }, "version": "4.4", "releaseDateUtc": "2021-03-15", "downloadUri": "https://cwe.mitre.org/data/xml/cwec_v4.4.xml.zip", "informationUri": "https://cwe.mitre.org/data/published/cwe_v4.4.pdf", "taxa": [ { "id": "CWE-1", "name": "DEPRECATED: Location", "fullDescription": { "text": "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." } }, { "id": "CWE-2", "name": "7PK - Environment", "fullDescription": { "text": "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.\"" }, "relationships": [ { "target": { "id": "CWE-700" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-5" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-6" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-7" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-8" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-9" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-11" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-12" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-13" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-14" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-3", "name": "DEPRECATED: Technology-specific Environment Issues", "fullDescription": { "text": "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)." } }, { "id": "CWE-4", "name": "DEPRECATED: J2EE Environment Issues", "fullDescription": { "text": "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." } }, { "id": "CWE-5", "name": "J2EE Misconfiguration: Data Transmission Without Encryption", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-319", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-6", "name": "J2EE Misconfiguration: Insufficient Session-ID Length", "shortDescription": { "text": "The J2EE application is configured to use an insufficient session ID length." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-334", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-7", "name": "J2EE Misconfiguration: Missing Custom Error Page", "shortDescription": { "text": "The default error page of a web application should not display sensitive information about the software system." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-756", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-8", "name": "J2EE Misconfiguration: Entity Bean Declared Remote", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-9", "name": "J2EE Misconfiguration: Weak Access Permissions for EJB Methods", "shortDescription": { "text": "If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the software system." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-266", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-10", "name": "DEPRECATED: ASP.NET Environment Issues", "fullDescription": { "text": "This category has been deprecated. It added unnecessary depth and complexity to its associated views." } }, { "id": "CWE-11", "name": "ASP.NET Misconfiguration: Creating Debug Binary", "shortDescription": { "text": "Debugging messages help attackers learn about the system and plan a form of attack." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-489", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-12", "name": "ASP.NET Misconfiguration: Missing Custom Error Page", "shortDescription": { "text": "An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses." }, "relationships": [ { "target": { "id": "CWE-756", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-13", "name": "ASP.NET Misconfiguration: Password in Configuration File", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-260", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-14", "name": "Compiler Removal of Code to Clear Buffers", "shortDescription": { "text": "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.\"" }, "fullDescription": { "text": "This compiler optimization error occurs when:1. Secret data are stored in memory.2. The secret data are scrubbed from memory by overwriting its contents.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." }, "relationships": [ { "target": { "id": "CWE-733", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-15", "name": "External Control of System or Configuration Setting", "shortDescription": { "text": "One or more system settings or configuration elements can be externally controlled by a user." }, "fullDescription": { "text": "Allowing external control of system settings can disrupt service or cause an application to behave in unexpected, and potentially malicious ways." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-642", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-16", "name": "Configuration", "fullDescription": { "text": "Weaknesses in this category are typically introduced during the configuration of the software." } }, { "id": "CWE-17", "name": "DEPRECATED: Code", "fullDescription": { "text": "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." } }, { "id": "CWE-18", "name": "DEPRECATED: Source Code", "fullDescription": { "text": "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." } }, { "id": "CWE-19", "name": "Data Processing Errors", "fullDescription": { "text": "Weaknesses in this category are typically found in functionality that processes data. Data processing is the manipulation of input to retrieve or save information." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-130" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-166" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-167" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-168" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-178" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-182" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-186" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-229" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-233" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-237" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-241" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-409" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-471" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-472" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-601" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-611" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-624" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-625" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-776" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1024" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-20", "name": "Improper Input Validation", "shortDescription": { "text": "The product receives input or data, but it does\n not validate or incorrectly validates that the input has the\n properties that are required to process the data safely and\n correctly." }, "fullDescription": { "text": "Input validation is a frequently-used technique\n\t for checking potentially dangerous inputs in order to\n\t ensure that the inputs are safe for processing within the\n\t code, or when communicating with other components. When\n\t software does not validate input properly, an attacker is\n\t able to craft the input in a form that is not expected by\n\t the rest of the application. This will lead to parts of the\n\t system receiving unintended input, which may result in\n\t altered control flow, arbitrary control of a resource, or\n\t arbitrary code execution.Input validation is not the only technique for\n\t processing input, however. Other techniques attempt to\n\t transform potentially-dangerous input into something safe, such\n\t as filtering (CWE-790) - which attempts to remove dangerous\n\t inputs - or encoding/escaping (CWE-116), which attempts to\n\t ensure that the input is not misinterpreted when it is included\n\t in output to another component. Other techniques exist as well\n\t (see CWE-138 for more examples.)Input validation can be applied to:raw data - strings, numbers, parameters, file contents, etc.metadata - information about the raw data, such as headers or sizeData can be simple or structured. Structured data\n\t can be composed of many nested layers, composed of\n\t combinations of metadata and raw data, with other simple or\n\t structured data.Many properties of raw data or metadata may need\n\t to be validated upon entry into the code, such\n\t as:specified quantities such as size, length, frequency, price, rate, number of operations, time, etc.implied or derived quantities, such as the actual size of a file instead of a specified sizeindexes, offsets, or positions into more complex data structuressymbolic keys or other elements into hash tables, associative arrays, etc.well-formedness, i.e. syntactic correctness - compliance with expected syntax lexical token correctness - compliance with rules for what is treated as a tokenspecified or derived type - the actual type of the input (or what the input appears to be)consistency - between individual data elements, between raw data and metadata, between references, etc.conformance to domain-specific rules, e.g. business logic equivalence - ensuring that equivalent inputs are treated the sameauthenticity, ownership, or other attestations about the input, e.g. a cryptographic signature to prove the source of the dataImplied or derived properties of data must often\n\t be calculated or inferred by the code itself. Errors in\n\t deriving properties may be considered a contributing factor\n\t to improper input validation.\n\t Note that \"input validation\" has very different\n\t meanings to different people, or within different\n\t classification schemes. Caution must be used when\n\t referencing this CWE entry or mapping to it. For example,\n\t some weaknesses might involve inadvertently giving control\n\t to an attacker over an input when they should not be able\n\t to provide an input at all, but sometimes this is referred\n\t to as input validation.Finally, it is important to emphasize that the\n\t distinctions between input validation and output escaping\n\t are often blurred, and developers must be careful to\n\t understand the difference, including how input validation\n\t is not always sufficient to prevent vulnerabilities,\n\t especially when less stringent data types must be\n\t supported, such as free-form text. Consider a SQL injection\n\t scenario in which a person's last name is inserted into a\n\t query. The name \"O'Reilly\" would likely pass the validation\n\t step since it is a common last name in the English\n\t language. However, this valid name cannot be directly\n\t inserted into the database because it contains the \"'\"\n\t apostrophe character, which would need to be escaped or\n\t otherwise transformed. In this case, removing the\n\t apostrophe might reduce the risk of SQL injection, but it\n\t would produce incorrect behavior because the wrong name\n\t would be recorded." }, "relationships": [ { "target": { "id": "CWE-22", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-770", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-21", "name": "DEPRECATED: Pathname Traversal and Equivalence Errors", "fullDescription": { "text": "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)." } }, { "id": "CWE-22", "name": "Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')", "shortDescription": { "text": "The software 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 software 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." }, "fullDescription": { "text": "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.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 software may add \".txt\" to any pathname, thus limiting the attacker to text files, but a null injection may effectively remove this restriction." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-23", "name": "Relative Path Traversal", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory." }, "relationships": [ { "target": { "id": "CWE-22", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-24", "name": "Path Traversal: '../filedir'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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 \"/\"." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-25", "name": "Path Traversal: '/../filedir'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.Sometimes a program checks for \"../\" at the beginning of the input, so a \"/../\" can bypass that check." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-26", "name": "Path Traversal: '/dir/../filename'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-27", "name": "Path Traversal: 'dir/../../filename'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-28", "name": "Path Traversal: '..\\filedir'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-29", "name": "Path Traversal: '\\..\\filename'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-30", "name": "Path Traversal: '\\dir\\..\\filename'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-31", "name": "Path Traversal: 'dir\\..\\..\\filename'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-32", "name": "Path Traversal: '...' (Triple Dot)", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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)." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-33", "name": "Path Traversal: '....' (Multiple Dot)", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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)." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-34", "name": "Path Traversal: '....//'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-35", "name": "Path Traversal: '.../...//'", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory.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 software could be susceptible to CWE-34 but not CWE-35, or vice versa." }, "relationships": [ { "target": { "id": "CWE-23", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-36", "name": "Absolute Path Traversal", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This allows attackers to traverse the file system to access files or directories that are outside of the restricted directory." }, "relationships": [ { "target": { "id": "CWE-22", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-37", "name": "Path Traversal: '/absolute/pathname/here'", "shortDescription": { "text": "A software system that accepts input in the form of a slash absolute path ('/absolute/pathname/here') without appropriate validation can allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-36", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-160", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-38", "name": "Path Traversal: '\\absolute\\pathname\\here'", "shortDescription": { "text": "A software system that accepts input in the form of a backslash absolute path ('\\absolute\\pathname\\here') without appropriate validation can allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-36", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-39", "name": "Path Traversal: 'C:dirname'", "shortDescription": { "text": "An attacker can inject a drive letter or Windows volume letter ('C:dirname') into a software system to potentially redirect access to an unintended location or arbitrary file." }, "relationships": [ { "target": { "id": "CWE-36", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-40", "name": "Path Traversal: '\\\\UNC\\share\\name\\' (Windows UNC Share)", "shortDescription": { "text": "An attacker can inject a Windows UNC share ('\\\\UNC\\share\\name') into a software system to potentially redirect access to an unintended location or arbitrary file." }, "relationships": [ { "target": { "id": "CWE-36", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-41", "name": "Improper Resolution of Path Equivalence", "shortDescription": { "text": "The system or application 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-42", "name": "Path Equivalence: 'filename.' (Trailing Dot)", "shortDescription": { "text": "A software system that accepts path input in the form of trailing dot ('filedir.') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-162", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-43", "name": "Path Equivalence: 'filename....' (Multiple Trailing Dot)", "shortDescription": { "text": "A software system that accepts path input in the form of multiple trailing dot ('filedir....') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-42", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-163", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-44", "name": "Path Equivalence: 'file.name' (Internal Dot)", "shortDescription": { "text": "A software system that accepts path input in the form of internal dot ('file.ordir') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-45", "name": "Path Equivalence: 'file...name' (Multiple Internal Dot)", "shortDescription": { "text": "A software system that accepts path input in the form of multiple internal dot ('file...dir') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-44", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-165", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-46", "name": "Path Equivalence: 'filename ' (Trailing Space)", "shortDescription": { "text": "A software system that accepts path input in the form of trailing space ('filedir ') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-162", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-289", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-47", "name": "Path Equivalence: ' filename' (Leading Space)", "shortDescription": { "text": "A software system that accepts path input in the form of leading space (' filedir') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-48", "name": "Path Equivalence: 'file name' (Internal Whitespace)", "shortDescription": { "text": "A software system that accepts path input in the form of internal space ('file(SPACE)name') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-49", "name": "Path Equivalence: 'filename/' (Trailing Slash)", "shortDescription": { "text": "A software system that accepts path input in the form of trailing slash ('filedir/') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-162", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-50", "name": "Path Equivalence: '//multiple/leading/slash'", "shortDescription": { "text": "A software system that accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-161", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-51", "name": "Path Equivalence: '/multiple//internal/slash'", "shortDescription": { "text": "A software system that accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-52", "name": "Path Equivalence: '/multiple/trailing/slash//'", "shortDescription": { "text": "A software system that accepts path input in the form of multiple trailing slash ('/multiple/trailing/slash//') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-163", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-289", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-53", "name": "Path Equivalence: '\\multiple\\\\internal\\backslash'", "shortDescription": { "text": "A software system that accepts path input in the form of multiple internal backslash ('\\multiple\\trailing\\\\slash') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-165", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-54", "name": "Path Equivalence: 'filedir\\' (Trailing Backslash)", "shortDescription": { "text": "A software system that accepts path input in the form of trailing backslash ('filedir\\') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-162", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-55", "name": "Path Equivalence: '/./' (Single Dot Directory)", "shortDescription": { "text": "A software system that accepts path input in the form of single dot directory exploit ('/./') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-56", "name": "Path Equivalence: 'filedir*' (Wildcard)", "shortDescription": { "text": "A software system that accepts path input in the form of asterisk wildcard ('filedir*') without appropriate validation can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-155", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-57", "name": "Path Equivalence: 'fakedir/../realdir/filename'", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-58", "name": "Path Equivalence: Windows 8.3 Filename", "shortDescription": { "text": "The software contains a protection mechanism that restricts access to a long filename on a Windows operating system, but the software does not properly restrict access to the equivalent short \"8.3\" filename." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-59", "name": "Improper Link Resolution Before File Access ('Link Following')", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-60", "name": "DEPRECATED: UNIX Path Link Problems", "fullDescription": { "text": "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." } }, { "id": "CWE-61", "name": "UNIX Symbolic Link (Symlink) Following", "shortDescription": { "text": "The software, 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 software to operate on unauthorized files." }, "fullDescription": { "text": "A software system 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." }, "relationships": [ { "target": { "id": "CWE-59", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-340", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-386", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-732", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] } ] }, { "id": "CWE-62", "name": "UNIX Hard Link", "shortDescription": { "text": "The software, 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 software to operate on unauthorized files." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-59", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-63", "name": "DEPRECATED: Windows Path Link Problems", "fullDescription": { "text": "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." } }, { "id": "CWE-64", "name": "Windows Shortcut Following (.LNK)", "shortDescription": { "text": "The software, 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 software to operate on unauthorized files." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-59", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-65", "name": "Windows Hard Link", "shortDescription": { "text": "The software, 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 software to operate on unauthorized files." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-59", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-66", "name": "Improper Handling of File Names that Identify Virtual Resources", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-67", "name": "Improper Handling of Windows Device Names", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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 software system 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." }, "relationships": [ { "target": { "id": "CWE-66", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-68", "name": "DEPRECATED: Windows Virtual File Problems", "fullDescription": { "text": "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." } }, { "id": "CWE-69", "name": "Improper Handling of Windows ::DATA Alternate Data Stream", "shortDescription": { "text": "The software does not properly prevent access to, or detect usage of, alternate data streams (ADS)." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-66", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-70", "name": "DEPRECATED: Mac Virtual File Problems", "fullDescription": { "text": "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." } }, { "id": "CWE-71", "name": "DEPRECATED: Apple '.DS_Store'", "shortDescription": { "text": "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." } }, { "id": "CWE-72", "name": "Improper Handling of Apple HFS+ Alternate Data Stream Path", "shortDescription": { "text": "The software does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system." }, "fullDescription": { "text": "If the software chooses actions to take based on the file name, then if an attacker provides the data or resource fork, the software may take unexpected actions. Further, if the software 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." }, "relationships": [ { "target": { "id": "CWE-66", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-73", "name": "External Control of File Name or Path", "shortDescription": { "text": "The software allows user input to control or influence paths or file names that are used in filesystem operations." }, "fullDescription": { "text": "This could allow an attacker to access or modify system files or other files that are critical to the application.Path manipulation errors occur when the following two conditions are met:1. An attacker can specify a path used in an operation on the filesystem.2. 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 or run with a configuration controlled by the attacker." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-22", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-59", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-98", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-434", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-642", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-74", "name": "Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Software 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 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." }, "relationships": [ { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-75", "name": "Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)", "shortDescription": { "text": "The software does not adequately filter user-controlled input for special elements with control implications." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-76", "name": "Improper Neutralization of Equivalent Special Elements", "shortDescription": { "text": "The software properly neutralizes certain special elements, but it improperly neutralizes equivalent special elements." }, "fullDescription": { "text": "The software 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 software 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 software 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." }, "relationships": [ { "target": { "id": "CWE-75", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-77", "name": "Improper Neutralization of Special Elements used in a Command ('Command Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Command injection vulnerabilities typically occur when:1. Data enters the application from an untrusted source.2. The data is part of a string that is executed as a command by the application.3. By executing the command, the application gives an attacker a privilege or capability that the attacker would not otherwise have.Command injection is a common problem with wrapper programs." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-78", "name": "Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.There are at least two subtypes of OS command injection: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.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.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." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-77", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-88", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] } ] }, { "id": "CWE-79", "name": "Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Cross-site scripting (XSS) vulnerabilities occur when:Untrusted data enters a web application, typically from a web request.The web application dynamically generates a web page that contains this untrusted data.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.A victim visits the generated web page through a web browser, which contains malicious script that was injected using the untrusted data.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.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.There are three main kinds of XSS:Type 1: Reflected XSS (or Non-Persistent) - \n \t\t\tThe 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.Type 2: Stored XSS (or Persistent) - \n 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.\n Type 0: DOM-Based XSS - \n 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.\n 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.\"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." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-352", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-494", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-80", "name": "Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)", "shortDescription": { "text": "The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters such as \"<\", \">\", and \"&\" that could be interpreted as web-scripting elements when they are sent to a downstream component that processes web pages." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-81", "name": "Improper Neutralization of Script in an Error Message Web Page", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Error pages may include customized 403 Forbidden or 404 Not Found pages.When an attacker can trigger an error that contains script syntax within the attacker's input, then cross-site scripting attacks may be possible." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-209", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-390", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] } ] }, { "id": "CWE-82", "name": "Improper Neutralization of Script in Attributes of IMG Tags in a Web Page", "shortDescription": { "text": "The web application does not neutralize or incorrectly neutralizes scripting elements within attributes of HTML IMG tags, such as the src attribute." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-83", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-83", "name": "Improper Neutralization of Script in Attributes in a Web Page", "shortDescription": { "text": "The software does not neutralize or incorrectly neutralizes \"javascript:\" or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-84", "name": "Improper Neutralization of Encoded URI Schemes in a Web Page", "shortDescription": { "text": "The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-85", "name": "Doubled Character XSS Manipulations", "shortDescription": { "text": "The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-675", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-86", "name": "Improper Neutralization of Invalid Characters in Identifiers in Web Pages", "shortDescription": { "text": "The software does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers." }, "fullDescription": { "text": "Some web browsers may remove these sequences, resulting in output that may have unintended control implications. For example, the software 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." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-184", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-87", "name": "Improper Neutralization of Alternate XSS Syntax", "shortDescription": { "text": "The software does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-88", "name": "Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')", "shortDescription": { "text": "The software constructs a string for a command to executed by a separate component\nin another control sphere, but it does not properly delimit the\nintended arguments, options, or switches within that command string." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-77", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-89", "name": "Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.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 software 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." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-943", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-90", "name": "Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-943", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-91", "name": "XML Injection (aka Blind XPath Injection)", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Within XML, special elements could include reserved words or characters such as \"<\", \">\", \"\"\", and \"&\", which could then be used to add new data or modify XML syntax." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-92", "name": "DEPRECATED: Improper Sanitization of Custom Special Characters", "shortDescription": { "text": "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." } }, { "id": "CWE-93", "name": "Improper Neutralization of CRLF Sequences ('CRLF Injection')", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-117", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-94", "name": "Improper Control of Generation of Code ('Code Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "When software 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 software. Such an alteration could lead to arbitrary code execution.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." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-913", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-95", "name": "Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')", "shortDescription": { "text": "The software 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\")." }, "fullDescription": { "text": "This may allow an attacker to execute arbitrary code, or at least modify what code can be executed." }, "relationships": [ { "target": { "id": "CWE-94", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-96", "name": "Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-94", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-97", "name": "Improper Neutralization of Server-Side Includes (SSI) Within a Web Page", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-96", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-98", "name": "Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')", "shortDescription": { "text": "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." }, "fullDescription": { "text": "In certain versions and configurations of PHP, this can allow an attacker to specify a URL to a remote location from which the software 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." }, "relationships": [ { "target": { "id": "CWE-94", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-426", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-829", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-99", "name": "Improper Control of Resource Identifiers ('Resource Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "A resource injection issue occurs when the following two conditions are met: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.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.This may enable an attacker to access or modify otherwise protected system resources." }, "relationships": [ { "target": { "id": "CWE-73", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-100", "name": "DEPRECATED: Technology-Specific Input Validation Problems", "fullDescription": { "text": "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." } }, { "id": "CWE-101", "name": "DEPRECATED: Struts Validation Problems", "fullDescription": { "text": "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." } }, { "id": "CWE-102", "name": "Struts: Duplicate Validation Forms", "shortDescription": { "text": "The application uses multiple validation forms with the same name, which might cause the Struts Validator to validate a form that the programmer does not expect." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-694", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1173", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-103", "name": "Struts: Incomplete validate() Method Definition", "shortDescription": { "text": "The application has a validator form that either does not define a validate() method, or defines a validate() method but does not call super.validate()." }, "fullDescription": { "text": "If you do 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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-104", "name": "Struts: Form Bean Does Not Extend Validation Class", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-105", "name": "Struts: Form Field Without Validator", "shortDescription": { "text": "The application has a form field that is not validated by a corresponding validation form, which can introduce other weaknesses related to insufficient input validation." }, "fullDescription": { "text": "Omitting validation for even a single input field may give attackers the leeway they need to compromise the application. 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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1173", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-106", "name": "Struts: Plug-in Framework not in Use", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1173", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-107", "name": "Struts: Unused Validation Form", "shortDescription": { "text": "An unused validation form indicates that validation logic is not up-to-date." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-108", "name": "Struts: Unvalidated Action Form", "shortDescription": { "text": "Every Action Form must have a corresponding validation form." }, "fullDescription": { "text": "If a Struts Action Form Mapping specifies a form, it must have a validation form defined under the Struts Validator." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1173", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-109", "name": "Struts: Validator Turned Off", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1173", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-110", "name": "Struts: Validator Without Form Field", "shortDescription": { "text": "Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-111", "name": "Direct Use of Unsafe JNI", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-695", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-112", "name": "Missing XML Validation", "shortDescription": { "text": "The software accepts XML from an untrusted source but does not validate the XML against the proper schema." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1286", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-113", "name": "Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting')", "shortDescription": { "text": "The software receives data from an upstream component, but does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers." }, "fullDescription": { "text": "Including unvalidated data in an HTTP header allows an attacker to specify the entirety of the HTTP response rendered by the browser. When an HTTP request contains unexpected CR (carriage return, also given by %0d or \\r) and LF (line feed, also given by %0a or \\n) characters the server may respond with an output stream that is interpreted as two different HTTP responses (instead of one). An attacker can control the second response and mount attacks such as cross-site scripting and cache poisoning attacks.HTTP response splitting weaknesses may be present when:Data enters a web application through an untrusted source, most frequently an HTTP request.The data is included in an HTTP response header sent to a web user without being validated for malicious characters." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-93", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-114", "name": "Process Control", "shortDescription": { "text": "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." }, "fullDescription": { "text": "Process control vulnerabilities take two forms: 1. An attacker can change the command that the program executes: the attacker explicitly controls what the command is. 2. An attacker can change the environment in which the command executes: the attacker implicitly controls what the command means. 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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-73", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-115", "name": "Misinterpretation of Input", "shortDescription": { "text": "The software misinterprets an input, whether from an attacker or another product, in a security-relevant fashion." }, "relationships": [ { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-116", "name": "Improper Encoding or Escaping of Output", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Improper encoding or escaping can allow attackers to change the commands that are sent to another component, inserting malicious commands instead.Most software follows 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\").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." }, "relationships": [ { "target": { "id": "CWE-74", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-117", "name": "Improper Output Neutralization for Logs", "shortDescription": { "text": "The software does not neutralize or incorrectly neutralizes output that is written to logs." }, "fullDescription": { "text": "This can allow an attacker to forge log entries or inject malicious content into logs.Log forging vulnerabilities occur when:Data enters an application from an untrusted source.The data is written to an application or system log file." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-116", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-118", "name": "Incorrect Access of Indexable Resource ('Range Error')", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-119", "name": "Improper Restriction of Operations within the Bounds of a Memory Buffer", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-118", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-120", "name": "Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')", "shortDescription": { "text": "The program 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." }, "fullDescription": { "text": "A buffer overflow condition exists when a program attempts to put more data in a buffer than it can hold, or when a program 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 program 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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-123", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-121", "name": "Stack-based Buffer Overflow", "shortDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-788", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-122", "name": "Heap-based Buffer Overflow", "shortDescription": { "text": "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()." }, "relationships": [ { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-788", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-123", "name": "Write-what-where Condition", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-124", "name": "Buffer Underwrite ('Buffer Underflow')", "shortDescription": { "text": "The software writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-786", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-125", "name": "Out-of-bounds Read", "shortDescription": { "text": "The software reads data past the end, or before the beginning, of the intended buffer." }, "fullDescription": { "text": "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 software 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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-126", "name": "Buffer Over-read", "shortDescription": { "text": "The software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-125", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-788", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-127", "name": "Buffer Under-read", "shortDescription": { "text": "The software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-125", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-786", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-128", "name": "Wrap-around Error", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-190", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-129", "name": "Improper Validation of Array Index", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-789", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-823", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-1285", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-130", "name": "Improper Handling of Length Parameter Inconsistency", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-240", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-805", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-131", "name": "Incorrect Calculation of Buffer Size", "shortDescription": { "text": "The software does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-132", "name": "DEPRECATED (Duplicate): Miscalculated Null Termination", "shortDescription": { "text": "This entry has been deprecated because it was a duplicate of CWE-170. All content has been transferred to CWE-170." } }, { "id": "CWE-133", "name": "String Errors", "fullDescription": { "text": "Weaknesses in this category are related to the creation and modification of strings." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-134" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-135" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-597" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-134", "name": "Use of Externally-Controlled Format String", "shortDescription": { "text": "The software uses a function that accepts a format string as an argument, but the format string originates from an external source." }, "fullDescription": { "text": "When an attacker can modify an externally-controlled format string, this can lead to buffer overflows, denial of service, or data representation problems.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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-123", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-135", "name": "Incorrect Calculation of Multi-Byte String Length", "shortDescription": { "text": "The software does not correctly calculate the length of strings that can contain wide or multi-byte characters." }, "relationships": [ { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-136", "name": "Type Errors", "fullDescription": { "text": "Weaknesses in this category are caused by improper data type transformation or improper handling of multiple data types." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-681" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-843" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-137", "name": "Data Neutralization Issues", "fullDescription": { "text": "Weaknesses in this category are related to the creation or neutralization of data using an incorrect format." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-76" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-88" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-90" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-91" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-93" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-94" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-96" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-117" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-140" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-170" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-188" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-462" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-463" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-464" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-641" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-643" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-652" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-791" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-795" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-838" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-917" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1236" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-138", "name": "Improper Neutralization of Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Most languages and protocols have their own special elements such as characters and reserved words. These special elements can carry control implications. If software 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 < (\"less than\") as meaning \"read input from a file\"." }, "relationships": [ { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-139", "name": "DEPRECATED: General Special Element Problems", "fullDescription": { "text": "This entry has been deprecated. It is a leftover from PLOVER, but CWE-138 is a more appropriate mapping." } }, { "id": "CWE-140", "name": "Improper Neutralization of Delimiters", "shortDescription": { "text": "The software does not neutralize or incorrectly neutralizes delimiters." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-141", "name": "Improper Neutralization of Parameter/Argument Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions." }, "relationships": [ { "target": { "id": "CWE-140", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-142", "name": "Improper Neutralization of Value Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions." }, "relationships": [ { "target": { "id": "CWE-140", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-143", "name": "Improper Neutralization of Record Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions." }, "relationships": [ { "target": { "id": "CWE-140", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-144", "name": "Improper Neutralization of Line Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions." }, "relationships": [ { "target": { "id": "CWE-93", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-140", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-145", "name": "Improper Neutralization of Section Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions.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." }, "relationships": [ { "target": { "id": "CWE-93", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-140", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-146", "name": "Improper Neutralization of Expression/Command Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions." }, "relationships": [ { "target": { "id": "CWE-140", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-147", "name": "Improper Neutralization of Input Terminators", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-148", "name": "Improper Neutralization of Input Leaders", "shortDescription": { "text": "The application 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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-149", "name": "Improper Neutralization of Quoting Syntax", "shortDescription": { "text": "Quotes injected into an application 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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-150", "name": "Improper Neutralization of Escape, Meta, or Control Sequences", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected/absent/malformed delimiter may cause the process to take unexpected actions." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-151", "name": "Improper Neutralization of Comment Delimiters", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-152", "name": "Improper Neutralization of Macro Symbols", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-153", "name": "Improper Neutralization of Substitution Characters", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-154", "name": "Improper Neutralization of Variable Name Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-155", "name": "Improper Neutralization of Wildcards or Matching Symbols", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected element may cause the process to take unexpected actions." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-156", "name": "Improper Neutralization of Whitespace", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This can include space, tab, etc." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-157", "name": "Failure to Sanitize Paired Delimiters", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Paired delimiters might include:< and > angle brackets( and ) parentheses{ and } braces[ and ] square brackets\" \" double quotes' ' single quotes" }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-158", "name": "Improper Neutralization of Null Byte or NUL Character", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, an injected NUL character or null byte may cause the software 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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-159", "name": "Improper Handling of Invalid Use of Special Elements", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-160", "name": "Improper Neutralization of Leading Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, improperly handled leading special elements may cause the process to take unexpected actions that result in an attack." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-161", "name": "Improper Neutralization of Multiple Leading Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, improperly handled multiple leading special elements may cause the process to take unexpected actions that result in an attack." }, "relationships": [ { "target": { "id": "CWE-160", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-162", "name": "Improper Neutralization of Trailing Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, improperly handled trailing special elements may cause the process to take unexpected actions that result in an attack." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-163", "name": "Improper Neutralization of Multiple Trailing Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, improperly handled multiple trailing special elements may cause the process to take unexpected actions that result in an attack." }, "relationships": [ { "target": { "id": "CWE-162", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-164", "name": "Improper Neutralization of Internal Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, improperly handled internal special elements may cause the process to take unexpected actions that result in an attack." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-165", "name": "Improper Neutralization of Multiple Internal Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "As data is parsed, improperly handled multiple internal special elements may cause the process to take unexpected actions that result in an attack." }, "relationships": [ { "target": { "id": "CWE-164", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-166", "name": "Improper Handling of Missing Special Element", "shortDescription": { "text": "The software receives input from an upstream component, but it does not handle or incorrectly handles when an expected special element is missing." }, "relationships": [ { "target": { "id": "CWE-159", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-167", "name": "Improper Handling of Additional Special Element", "shortDescription": { "text": "The software receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided." }, "relationships": [ { "target": { "id": "CWE-159", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-168", "name": "Improper Handling of Inconsistent Special Elements", "shortDescription": { "text": "The software does not properly handle input in which an inconsistency exists between two or more special characters or reserved words." }, "fullDescription": { "text": "An example of this problem would be if paired characters appear in the wrong order, or if the special characters are not properly nested." }, "relationships": [ { "target": { "id": "CWE-159", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-169", "name": "DEPRECATED: Technology-Specific Special Elements", "fullDescription": { "text": "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." } }, { "id": "CWE-170", "name": "Improper Null Termination", "shortDescription": { "text": "The software does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-120", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-126", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-147", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-463", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-464", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-171", "name": "DEPRECATED: Cleansing, Canonicalization, and Comparison Errors", "fullDescription": { "text": "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." } }, { "id": "CWE-172", "name": "Encoding Error", "shortDescription": { "text": "The software does not properly encode or decode the data, resulting in unexpected values." }, "relationships": [ { "target": { "id": "CWE-22", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-41", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-173", "name": "Improper Handling of Alternate Encoding", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-172", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-289", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-174", "name": "Double Decoding of the Same Data", "shortDescription": { "text": "The software decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations." }, "relationships": [ { "target": { "id": "CWE-172", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-675", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-175", "name": "Improper Handling of Mixed Encoding", "shortDescription": { "text": "The software does not properly handle when the same input uses several different (mixed) encodings." }, "relationships": [ { "target": { "id": "CWE-172", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-176", "name": "Improper Handling of Unicode Encoding", "shortDescription": { "text": "The software does not properly handle when an input contains Unicode encoding." }, "relationships": [ { "target": { "id": "CWE-172", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-177", "name": "Improper Handling of URL Encoding (Hex Encoding)", "shortDescription": { "text": "The software does not properly handle when all or part of an input has been URL encoded." }, "relationships": [ { "target": { "id": "CWE-172", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-178", "name": "Improper Handling of Case Sensitivity", "shortDescription": { "text": "The software does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results." }, "fullDescription": { "text": "Improperly handled case sensitive data can lead to several possible consequences, including:case-insensitive passwords reducing the size of the key space, making brute force attacks easierbypassing filters or access controls using alternate namesmultiple interpretation errors using alternate names." }, "relationships": [ { "target": { "id": "CWE-289", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-433", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-179", "name": "Incorrect Behavior Order: Early Validation", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Software 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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-696", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-180", "name": "Incorrect Behavior Order: Validate Before Canonicalize", "shortDescription": { "text": "The software validates input before it is canonicalized, which prevents the software from detecting data that becomes invalid after the canonicalization step." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-179", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-181", "name": "Incorrect Behavior Order: Validate Before Filter", "shortDescription": { "text": "The software validates data before it has been filtered, which prevents the software from detecting data that becomes invalid after the filtering step." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-179", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-182", "name": "Collapse of Data into Unsafe Value", "shortDescription": { "text": "The software filters data in a way that causes it to be reduced or \"collapsed\" into an unsafe value that violates an expected security property." }, "relationships": [ { "target": { "id": "CWE-33", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-34", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-35", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-183", "name": "Permissive List of Allowed Inputs", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-434", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-697", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-184", "name": "Incomplete List of Disallowed Inputs", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-78", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-98", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-434", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1023", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-185", "name": "Incorrect Regular Expression", "shortDescription": { "text": "The software specifies a regular expression in a way that causes data to be improperly matched or compared." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-182", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-187", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-697", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-186", "name": "Overly Restrictive Regular Expression", "shortDescription": { "text": "A regular expression is overly restrictive, which prevents dangerous values from being detected." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-183", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-184", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-185", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-187", "name": "Partial String Comparison", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "For example, an attacker might succeed in authentication by providing a small password that matches the associated portion of the larger, correct password." }, "relationships": [ { "target": { "id": "CWE-1023", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-188", "name": "Reliance on Data/Memory Layout", "shortDescription": { "text": "The software makes invalid assumptions about how protocol data or memory is organized at a lower level, resulting in unintended program behavior." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-435", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1105", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-189", "name": "Numeric Errors", "fullDescription": { "text": "Weaknesses in this category are related to improper calculation or conversion of numbers." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-128" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-190" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-191" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-192" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-193" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-197" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-198" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-369" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-681" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-839" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1077" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-190", "name": "Integer Overflow or Wraparound", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-191", "name": "Integer Underflow (Wrap or Wraparound)", "shortDescription": { "text": "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." }, "fullDescription": { "text": "This can happen in signed and unsigned cases." }, "relationships": [ { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-192", "name": "Integer Coercion Error", "shortDescription": { "text": "Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-681", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-193", "name": "Off-by-one Error", "shortDescription": { "text": "A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-170", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-617", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-194", "name": "Unexpected Sign Extension", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-681", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-195", "name": "Signed to Unsigned Conversion Error", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-681", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-196", "name": "Unsigned to Signed Conversion Error", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-120", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-124", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-681", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-197", "name": "Numeric Truncation Error", "shortDescription": { "text": "Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-192", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-194", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-195", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-196", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-681", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-198", "name": "Use of Incorrect Byte Ordering", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-188", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-199", "name": "Information Management Errors", "fullDescription": { "text": "Weaknesses in this category are related to improper handling of sensitive information." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-201" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-204" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-205" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-208" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-212" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-213" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-214" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-215" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-312" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-319" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-359" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-497" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-524" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-532" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-540" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-921" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1230" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-200", "name": "Exposure of Sensitive Information to an Unauthorized Actor", "shortDescription": { "text": "The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information." }, "fullDescription": { "text": "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:private, personal information, such as personal messages, financial data, health records, geographic location, or contact detailssystem status and environment, such as the operating system and installed packagesbusiness secrets and intellectual propertynetwork status and configurationthe product's own code or internal statemetadata, e.g. logging of connections or message headersindirect information, such as a discrepancy between two internal operations that can be observed by an outsiderInformation might be sensitive to different parties, each of which may have their own expectations for whether the information should be protected. These parties include:the product's own userspeople or organizations whose information is created or used by the product, even if they are not direct product usersthe product's administrators, including the admins of the system(s) and/or networks on which the product operatesthe developerInformation exposures can occur in different ways:the code explicitly inserts 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\"a different weakness or mistake indirectly inserts the sensitive information into resources, such as a web script error revealing the full system path of the program.the code manages resources that intentionally contain sensitive information, but the resources are unintentionally made accessible 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.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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-201", "name": "Insertion of Sensitive Information Into Sent Data", "shortDescription": { "text": "The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor." }, "fullDescription": { "text": "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).\n\t " }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-202", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-209", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] } ] }, { "id": "CWE-202", "name": "Exposure of Sensitive Information Through Data Queries", "shortDescription": { "text": "When trying to keep information confidential, an attacker can often infer some of the information by using statistics." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1230", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-203", "name": "Observable Discrepancy", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-204", "name": "Observable Response Discrepancy", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-203", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-205", "name": "Observable Behavioral Discrepancy", "shortDescription": { "text": "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." }, "fullDescription": { "text": "\n\t 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." }, "relationships": [ { "target": { "id": "CWE-203", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-514", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-206", "name": "Observable Internal Behavioral Discrepancy", "shortDescription": { "text": "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." }, "fullDescription": { "text": "\n\t 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.\n\t " }, "relationships": [ { "target": { "id": "CWE-205", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-207", "name": "Observable Behavioral Discrepancy With Equivalent Products", "shortDescription": { "text": "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." }, "fullDescription": { "text": "\n\t 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.\n\t " }, "relationships": [ { "target": { "id": "CWE-205", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-208", "name": "Observable Timing Discrepancy", "shortDescription": { "text": "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." }, "fullDescription": { "text": "\n\t 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.\n\t " }, "relationships": [ { "target": { "id": "CWE-203", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-327", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-385", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-209", "name": "Generation of Error Message Containing Sensitive Information", "shortDescription": { "text": "The software generates an error message that includes sensitive information about its environment, users, or associated data." }, "fullDescription": { "text": "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:self-generated: the source code explicitly constructs the error message and delivers itexternally-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 programmerAn 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." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-210", "name": "Self-generated Error Message Containing Sensitive Information", "shortDescription": { "text": "The software identifies an error condition and creates its own diagnostic or error messages that contain sensitive information." }, "relationships": [ { "target": { "id": "CWE-209", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-211", "name": "Externally-Generated Error Message Containing Sensitive Information", "shortDescription": { "text": "The application performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the application, such as an error generated by the programming language interpreter that the software uses. The error can contain sensitive system information." }, "relationships": [ { "target": { "id": "CWE-209", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-212", "name": "Improper Removal of Sensitive Information Before Storage or Transfer", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.For example, software that is used 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." }, "relationships": [ { "target": { "id": "CWE-201", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-213", "name": "Exposure of Sensitive Information Due to Incompatible Policies", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-214", "name": "Invocation of Process Using Visible Sensitive Information", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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 software or related resources." }, "relationships": [ { "target": { "id": "CWE-497", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-215", "name": "Insertion of Sensitive Information Into Debugging Code", "shortDescription": { "text": "The application inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production." }, "fullDescription": { "text": "When debugging, it may be necessary to report detailed information to the programmer. However, if the debugging code is not disabled when the application is operating in a production environment, then this sensitive information may be exposed to attackers.\n\t " }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-216", "name": "DEPRECATED: Containment Errors (Container Errors)", "shortDescription": { "text": "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." } }, { "id": "CWE-217", "name": "DEPRECATED: Failure to Protect Stored Data from Modification", "shortDescription": { "text": "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." } }, { "id": "CWE-218", "name": "DEPRECATED (Duplicate): Failure to provide confidentiality for stored data", "shortDescription": { "text": "This weakness has been deprecated because it was a duplicate of CWE-493. All content has been transferred to CWE-493." } }, { "id": "CWE-219", "name": "Storage of File with Sensitive Data Under Web Root", "shortDescription": { "text": "The application stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties." }, "fullDescription": { "text": "\n\t Besides public-facing web pages and code, applications 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.\n\t " }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-220", "name": "Storage of File With Sensitive Data Under FTP Root", "shortDescription": { "text": "The application stores sensitive data under the FTP server root with insufficient access control, which might make it accessible to untrusted parties." }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-221", "name": "Information Loss or Omission", "shortDescription": { "text": "The software does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis." }, "fullDescription": { "text": "This can be resultant, e.g. a buffer overflow might trigger a crash before the product can log the event." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-222", "name": "Truncation of Security-relevant Information", "shortDescription": { "text": "The application truncates the display, recording, or processing of security-relevant information in a way that can obscure the source or nature of an attack." }, "relationships": [ { "target": { "id": "CWE-221", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-223", "name": "Omission of Security-relevant Information", "shortDescription": { "text": "The application 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." }, "relationships": [ { "target": { "id": "CWE-221", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-224", "name": "Obscured Security-relevant Information by Alternate Name", "shortDescription": { "text": "The software records security-relevant information according to an alternate name of the affected entity, instead of the canonical name." }, "relationships": [ { "target": { "id": "CWE-221", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-225", "name": "DEPRECATED (Duplicate): General Information Management Problems", "shortDescription": { "text": "This weakness can be found at CWE-199." } }, { "id": "CWE-226", "name": "Sensitive Information in Resource Not Removed Before Reuse", "shortDescription": { "text": "When a device releases a resource such as memory or a file for reuse by other entities, information contained in the resource is not fully cleared prior to reuse of the resource." }, "fullDescription": { "text": "When resources are released, they can be made available for reuse. For example, after memory is used and released, 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.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." }, "relationships": [ { "target": { "id": "CWE-201", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-212", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-459", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-227", "name": "7PK - API Abuse", "fullDescription": { "text": "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.\"" }, "relationships": [ { "target": { "id": "CWE-700" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-242" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-243" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-244" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-245" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-246" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-248" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-250" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-251" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-252" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-558" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-228", "name": "Improper Handling of Syntactically Invalid Structure", "shortDescription": { "text": "The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification." }, "relationships": [ { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-229", "name": "Improper Handling of Values", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-228", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-230", "name": "Improper Handling of Missing Values", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-229", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-231", "name": "Improper Handling of Extra Values", "shortDescription": { "text": "The software does not handle or incorrectly handles when more values are provided than expected." }, "relationships": [ { "target": { "id": "CWE-120", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-229", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-232", "name": "Improper Handling of Undefined Values", "shortDescription": { "text": "The software does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name." }, "relationships": [ { "target": { "id": "CWE-229", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-233", "name": "Improper Handling of Parameters", "shortDescription": { "text": "The software does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined." }, "relationships": [ { "target": { "id": "CWE-228", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-234", "name": "Failure to Handle Missing Parameter", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-233", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-235", "name": "Improper Handling of Extra Parameters", "shortDescription": { "text": "The software does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount." }, "relationships": [ { "target": { "id": "CWE-233", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-236", "name": "Improper Handling of Undefined Parameters", "shortDescription": { "text": "The software does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product." }, "relationships": [ { "target": { "id": "CWE-233", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-237", "name": "Improper Handling of Structural Elements", "shortDescription": { "text": "The software does not handle or incorrectly handles inputs that are related to complex structures." }, "relationships": [ { "target": { "id": "CWE-228", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-238", "name": "Improper Handling of Incomplete Structural Elements", "shortDescription": { "text": "The software does not handle or incorrectly handles when a particular structural element is not completely specified." }, "relationships": [ { "target": { "id": "CWE-237", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-239", "name": "Failure to Handle Incomplete Element", "shortDescription": { "text": "The software does not properly handle when a particular element is not completely specified." }, "relationships": [ { "target": { "id": "CWE-237", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-240", "name": "Improper Handling of Inconsistent Structural Elements", "shortDescription": { "text": "The software does not handle or incorrectly handles when two or more structural elements should be consistent, but are not." }, "relationships": [ { "target": { "id": "CWE-237", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-241", "name": "Improper Handling of Unexpected Data Type", "shortDescription": { "text": "The software 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)." }, "relationships": [ { "target": { "id": "CWE-228", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-242", "name": "Use of Inherently Dangerous Function", "shortDescription": { "text": "The program calls a function that can never be guaranteed to work safely." }, "fullDescription": { "text": "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 >> 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 >> operator and overflow the destination buffer." }, "relationships": [ { "target": { "id": "CWE-1177", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-243", "name": "Creation of chroot Jail Without Changing Working Directory", "shortDescription": { "text": "The program 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-244", "name": "Improper Clearing of Heap Memory Before Release ('Heap Inspection')", "shortDescription": { "text": "Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-226", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-245", "name": "J2EE Bad Practices: Direct Management of Connections", "shortDescription": { "text": "The J2EE application directly manages connections, instead of using the container's connection management facilities." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-695", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-246", "name": "J2EE Bad Practices: Direct Use of Sockets", "shortDescription": { "text": "The J2EE application directly uses sockets instead of using framework method calls." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-695", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-247", "name": "DEPRECATED (Duplicate): Reliance on DNS Lookups in a Security Decision", "shortDescription": { "text": "This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350." } }, { "id": "CWE-248", "name": "Uncaught Exception", "shortDescription": { "text": "An exception is thrown from a function, but it is not caught." }, "fullDescription": { "text": "When an exception is not caught, it may cause the program to crash or expose sensitive information." }, "relationships": [ { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-249", "name": "DEPRECATED: Often Misused: Path Manipulation", "shortDescription": { "text": "This entry has been deprecated because of name\n\tconfusion and an accidental combination of multiple\n\tweaknesses. Most of its content has been transferred to\n\tCWE-785.\n\n This entry was deprecated for several reasons. The primary\n reason is over-loading of the \"path manipulation\" term and the\n description. The original description for this entry was the\n same as that for the \"Often Misused: File System\" item in the\n original Seven Pernicious Kingdoms paper. However, Seven\n Pernicious Kingdoms also has a \"Path Manipulation\" phrase that\n is for external control of pathnames (CWE-73), which is a\n factor in symbolic link following and path traversal, neither\n of which is explicitly mentioned in 7PK. Fortify uses the\n phrase \"Often Misused: Path Manipulation\" for a broader range\n of problems, generally for issues related to buffer\n management. Given the multiple conflicting uses of this term,\n there is a chance that CWE users may have incorrectly mapped\n to this entry.\n\n\tThe second reason for deprecation is an implied combination of\n\tmultiple weaknesses within buffer-handling functions. The\n\tfocus of this entry was generally on the path-conversion\n\tfunctions and their association with buffer\n\toverflows. However, some of Fortify's Vulncat entries have the\n\tterm \"path manipulation\" but describe a non-overflow weakness\n\tin which the buffer is not guaranteed to contain the entire\n\tpathname, i.e., there is information truncation (see CWE-222\n\tfor a similar concept). A new entry for this non-overflow\n\tweakness may be created in a future version of CWE.\n\t \n\t " } }, { "id": "CWE-250", "name": "Execution with Unnecessary Privileges", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-251", "name": "Often Misused: String Management", "fullDescription": { "text": "Functions that manipulate strings encourage buffer overflows." } }, { "id": "CWE-252", "name": "Unchecked Return Value", "shortDescription": { "text": "The software does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions." }, "fullDescription": { "text": "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 software 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." }, "relationships": [ { "target": { "id": "CWE-476", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-754", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-253", "name": "Incorrect Check of Function Return Value", "shortDescription": { "text": "The software incorrectly checks a return value from a function, which prevents the software from detecting errors or exceptional conditions." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-754", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-254", "name": "7PK - Security Features", "fullDescription": { "text": "Software security is not security software. Here we're concerned with topics like authentication, access control, confidentiality, cryptography, and privilege management." }, "relationships": [ { "target": { "id": "CWE-700" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-256" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-258" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-259" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-260" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-261" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-272" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-284" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-285" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-330" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-359" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-798" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-255", "name": "Credentials Management Errors", "fullDescription": { "text": "Weaknesses in this category are related to the management of credentials." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-256" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-257" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-260" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-261" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-262" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-263" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-324" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-521" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-523" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-549" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-620" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-640" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-798" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-916" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-256", "name": "Unprotected Storage of Credentials", "shortDescription": { "text": "Storing a password in plaintext may result in a system compromise." }, "fullDescription": { "text": "Password management issues occur when a password is stored in plaintext in an application's properties or configuration file. Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource." }, "relationships": [ { "target": { "id": "CWE-319", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-522", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-257", "name": "Storing Passwords in a Recoverable Format", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-259", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-522", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-258", "name": "Empty Password in Configuration File", "shortDescription": { "text": "Using an empty string as a password is insecure." }, "relationships": [ { "target": { "id": "CWE-260", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-521", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-259", "name": "Use of Hard-coded Password", "shortDescription": { "text": "The software contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components." }, "fullDescription": { "text": "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:Inbound: the software contains an authentication mechanism that checks for a hard-coded password.Outbound: the software connects to another system or component, and it contains hard-coded password for connecting to that component.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 software. 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 software will have the same password, even across different organizations, this enables massive attacks such as worms to take place.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 software. 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." }, "relationships": [ { "target": { "id": "CWE-257", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-321", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-798", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-260", "name": "Password in Configuration File", "shortDescription": { "text": "The software stores a password in a configuration file that might be accessible to actors who do not know the password." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-522", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-261", "name": "Weak Encoding for Password", "shortDescription": { "text": "Obscuring a password with a trivial encoding does not protect the password." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-326", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-262", "name": "Not Using Password Aging", "shortDescription": { "text": "If no mechanism is in place for managing password aging, users will have no incentive to update passwords in a timely manner." }, "fullDescription": { "text": "Security experts have often recommended that users change their passwords regularly and avoid reusing passwords. Although this can be an effective mitigation, if the expiration window is too short, it can cause users to generate poor or predictable passwords. As such, it is important to discourage creating similar passwords. It is also useful to have a password aging mechanism that notifies users when passwords are considered old and requests that they replace them with new, strong passwords. Companion documentation which stresses how important this practice is can help users understand and better support this approach." }, "relationships": [ { "target": { "id": "CWE-263", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-309", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-324", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-263", "name": "Password Aging with Long Expiration", "shortDescription": { "text": "Allowing password aging to occur unchecked can result in the possibility of diminished password integrity." }, "fullDescription": { "text": "Just as neglecting to include functionality for the management of password aging is dangerous, so is allowing password aging to continue unchecked. Passwords must be given a maximum life span, after which a user is required to update with a new and different password." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-264", "name": "Permissions, Privileges, and Access Controls", "fullDescription": { "text": "Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control." } }, { "id": "CWE-265", "name": "Privilege Issues", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-243" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-250" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-266" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-267" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-268" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-270" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-272" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-273" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-274" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-280" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-501" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-580" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-648" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-266", "name": "Incorrect Privilege Assignment", "shortDescription": { "text": "A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-286", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] } ] }, { "id": "CWE-267", "name": "Privilege Defined With Unsafe Actions", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-268", "name": "Privilege Chaining", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-269", "name": "Improper Privilege Management", "shortDescription": { "text": "The software does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-270", "name": "Privilege Context Switching Error", "shortDescription": { "text": "The software does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-271", "name": "Privilege Dropping / Lowering Errors", "shortDescription": { "text": "The software does not drop privileges before passing control of a resource to an actor that does not have those privileges." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-272", "name": "Least Privilege Violation", "shortDescription": { "text": "The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed." }, "relationships": [ { "target": { "id": "CWE-271", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-273", "name": "Improper Check for Dropped Privileges", "shortDescription": { "text": "The software attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded." }, "fullDescription": { "text": "If the drop fails, the software will continue to run with the raised privileges, which might provide additional access to unprivileged users." }, "relationships": [ { "target": { "id": "CWE-252", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-271", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-754", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-274", "name": "Improper Handling of Insufficient Privileges", "shortDescription": { "text": "The software does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-271", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-280", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-275", "name": "Permission Issues", "fullDescription": { "text": "Weaknesses in this category are related to improper assignment or handling of permissions." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-276" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-277" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-278" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-279" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-280" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-281" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-618" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-766" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-767" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-276", "name": "Incorrect Default Permissions", "shortDescription": { "text": "During installation, installed file permissions are set to allow anyone to modify those files." }, "relationships": [ { "target": { "id": "CWE-732", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-277", "name": "Insecure Inherited Permissions", "shortDescription": { "text": "A product defines a set of insecure permissions that are inherited by objects that are created by the program." }, "relationships": [ { "target": { "id": "CWE-732", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-278", "name": "Insecure Preserved Inherited Permissions", "shortDescription": { "text": "A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement." }, "relationships": [ { "target": { "id": "CWE-732", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-279", "name": "Incorrect Execution-Assigned Permissions", "shortDescription": { "text": "While it is executing, the software sets the permissions of an object in a way that violates the intended permissions that have been specified by the user." }, "relationships": [ { "target": { "id": "CWE-732", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-280", "name": "Improper Handling of Insufficient Permissions or Privileges ", "shortDescription": { "text": "The application 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 application in an invalid state." }, "relationships": [ { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-281", "name": "Improper Preservation of Permissions", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-732", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-282", "name": "Improper Ownership Management", "shortDescription": { "text": "The software assigns the wrong ownership, or does not properly verify the ownership, of an object or resource." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-283", "name": "Unverified Ownership", "shortDescription": { "text": "The software does not properly verify that a critical resource is owned by the proper entity." }, "relationships": [ { "target": { "id": "CWE-282", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-284", "name": "Improper Access Control", "shortDescription": { "text": "The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor." }, "fullDescription": { "text": "Access control involves the use of several protection mechanisms such as:Authentication (proving the identity of an actor)Authorization (ensuring that a given actor can access a resource), andAccountability (tracking of activities that were performed)When any mechanism is not applied or otherwise fails, attackers can compromise the security of the software by gaining privileges, reading sensitive information, executing commands, evading detection, etc.There are two distinct behaviors that can introduce access control weaknesses: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.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." } }, { "id": "CWE-285", "name": "Improper Authorization", "shortDescription": { "text": "The software does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-286", "name": "Incorrect User Management", "shortDescription": { "text": "The software does not properly manage a user within its environment." }, "fullDescription": { "text": "Users can be assigned to the wrong group (class) of permissions resulting in unintended access rights to sensitive objects." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-287", "name": "Improper Authentication", "shortDescription": { "text": "When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-288", "name": "Authentication Bypass Using an Alternate Path or Channel", "shortDescription": { "text": "A product requires authentication, but the product has an alternate path or channel that does not require authentication." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-420", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-425", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-289", "name": "Authentication Bypass by Alternate Name", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-290", "name": "Authentication Bypass by Spoofing", "shortDescription": { "text": "This attack-focused weakness is caused by improperly implemented authentication schemes that are subject to spoofing attacks." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-291", "name": "Reliance on IP Address for Authentication", "shortDescription": { "text": "The software uses an IP address for authentication." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-290", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-471", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-292", "name": "DEPRECATED (Duplicate): Trusting Self-reported DNS Name", "shortDescription": { "text": "This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350." } }, { "id": "CWE-293", "name": "Using Referer Field for Authentication", "shortDescription": { "text": "The referer field in HTTP requests can be easily modified and, as such, is not a valid means of message integrity checking." }, "relationships": [ { "target": { "id": "CWE-290", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-294", "name": "Authentication Bypass by Capture-replay", "shortDescription": { "text": "A capture-replay flaw exists when the design of the software 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)." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-295", "name": "Improper Certificate Validation", "shortDescription": { "text": "The software does not validate, or incorrectly validates, a certificate." }, "fullDescription": { "text": "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 software might connect to a malicious host while believing it is a trusted host, or the software might be deceived into accepting spoofed data that appears to originate from a trusted host." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-322", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-296", "name": "Improper Following of a Certificate's Chain of Trust", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.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.There are several ways in which the chain of trust might be broken, including but not limited to:Any certificate in the chain is self-signed, unless it the root.Not every intermediate certificate is checked, starting from the original certificate all the way up to the root certificate.An intermediate, CA-signed certificate does not have the expected Basic Constraints or other important extensions.The root certificate has been compromised or authorized to the wrong party." }, "relationships": [ { "target": { "id": "CWE-295", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-297", "name": "Improper Validation of Certificate with Host Mismatch", "shortDescription": { "text": "The software communicates with a host that provides a certificate, but the software does not properly ensure that the certificate is actually associated with that host." }, "fullDescription": { "text": "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 software 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.Even if the software 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.This weakness can occur even when the software uses Certificate Pinning, if the software does not verify the hostname at the time a certificate is pinned." }, "relationships": [ { "target": { "id": "CWE-295", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-298", "name": "Improper Validation of Certificate Expiration", "shortDescription": { "text": "A certificate expiration is not validated or is incorrectly validated, so trust may be assigned to certificates that have been abandoned due to age." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-295", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-299", "name": "Improper Check for Certificate Revocation", "shortDescription": { "text": "The software does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-295", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-300", "name": "Channel Accessible by Non-Endpoint", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-301", "name": "Reflection Attack in an Authentication Protocol", "shortDescription": { "text": "Simple authentication protocols are subject to reflection attacks if a malicious user can use the target machine to impersonate a trusted user." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-327", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-302", "name": "Authentication Bypass by Assumed-Immutable Data", "shortDescription": { "text": "The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-807", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-303", "name": "Incorrect Implementation of Authentication Algorithm", "shortDescription": { "text": "The requirements for the software dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect." }, "fullDescription": { "text": "This incorrect implementation may allow authentication to be bypassed." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-304", "name": "Missing Critical Step in Authentication", "shortDescription": { "text": "The software implements an authentication technique, but it skips a step that weakens the technique." }, "fullDescription": { "text": "Authentication techniques should follow the algorithms that define them exactly, otherwise authentication can be bypassed or more easily subjected to brute force attacks." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-305", "name": "Authentication Bypass by Primary Weakness", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-306", "name": "Missing Authentication for Critical Function", "shortDescription": { "text": "The software does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-307", "name": "Improper Restriction of Excessive Authentication Attempts", "shortDescription": { "text": "The software does not implement sufficient measures to prevent multiple failed authentication attempts within in a short time frame, making it more susceptible to brute force attacks." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-799", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-308", "name": "Use of Single-factor Authentication", "shortDescription": { "text": "The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-309", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-654", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-309", "name": "Use of Password System for Primary Authentication", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-308", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-654", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-310", "name": "Cryptographic Issues", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-261" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-324" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-325" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-328" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-331" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-334" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-335" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-338" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-347" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-916" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1240" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-311", "name": "Missing Encryption of Sensitive Data", "shortDescription": { "text": "The software does not encrypt sensitive or critical information before storage or transmission." }, "fullDescription": { "text": "The lack of proper data encryption passes up the guarantees of confidentiality, integrity, and accountability that properly implemented encryption conveys." }, "relationships": [ { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-312", "name": "Cleartext Storage of Sensitive Information", "shortDescription": { "text": "The application stores sensitive information in cleartext within a resource that might be accessible to another control sphere." }, "fullDescription": { "text": "Because the information is stored in cleartext, 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." }, "relationships": [ { "target": { "id": "CWE-311", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-922", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-313", "name": "Cleartext Storage in a File or on Disk", "shortDescription": { "text": "The application stores sensitive information in cleartext in a file, or on disk." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-312", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-314", "name": "Cleartext Storage in the Registry", "shortDescription": { "text": "The application stores sensitive information in cleartext in the registry." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-312", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-315", "name": "Cleartext Storage of Sensitive Information in a Cookie", "shortDescription": { "text": "The application stores sensitive information in cleartext in a cookie." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-312", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-316", "name": "Cleartext Storage of Sensitive Information in Memory", "shortDescription": { "text": "The application stores sensitive information in cleartext in memory." }, "fullDescription": { "text": "The sensitive memory might be saved to disk, stored in a core dump, or remain uncleared if the application crashes, or if the programmer does not properly clear the memory before freeing it.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." }, "relationships": [ { "target": { "id": "CWE-312", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-317", "name": "Cleartext Storage of Sensitive Information in GUI", "shortDescription": { "text": "The application stores sensitive information in cleartext within the GUI." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-312", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-318", "name": "Cleartext Storage of Sensitive Information in Executable", "shortDescription": { "text": "The application stores sensitive information in cleartext in an executable." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-312", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-319", "name": "Cleartext Transmission of Sensitive Information", "shortDescription": { "text": "The software transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors." }, "fullDescription": { "text": "Many communication channels can be \"sniffed\" by attackers during data transmission. For example, network traffic can often be sniffed by any attacker who has access to a network interface. This significantly lowers the difficulty of exploitation by attackers." }, "relationships": [ { "target": { "id": "CWE-311", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-320", "name": "Key Management Errors", "fullDescription": { "text": "Weaknesses in this category are related to errors in the management of cryptographic keys." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-321" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-322" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-323" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-324" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-321", "name": "Use of Hard-coded Cryptographic Key", "shortDescription": { "text": "The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered." }, "relationships": [ { "target": { "id": "CWE-798", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-322", "name": "Key Exchange without Entity Authentication", "shortDescription": { "text": "The software performs a key exchange with an actor without verifying the identity of that actor." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-295", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-323", "name": "Reusing a Nonce, Key Pair in Encryption", "shortDescription": { "text": "Nonces should be used for the present occasion and only once." }, "relationships": [ { "target": { "id": "CWE-344", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-324", "name": "Use of a Key Past its Expiration Date", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-298", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-325", "name": "Missing Cryptographic Step", "shortDescription": { "text": "The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm." }, "relationships": [ { "target": { "id": "CWE-358", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-326", "name": "Inadequate Encryption Strength", "shortDescription": { "text": "The software stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required." }, "fullDescription": { "text": "A weak encryption scheme can be subjected to brute force attacks that have a reasonable chance of succeeding using current attack methods and resources." }, "relationships": [ { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-327", "name": "Use of a Broken or Risky Cryptographic Algorithm", "shortDescription": { "text": "The use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the exposure of sensitive information." }, "fullDescription": { "text": "The use of a non-standard algorithm is dangerous because a determined attacker may be able to break the algorithm and compromise whatever data has been protected. Well-known techniques may exist to break the algorithm." }, "relationships": [ { "target": { "id": "CWE-311", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-328", "name": "Reversible One-Way Hash", "shortDescription": { "text": "The product uses a hashing algorithm that produces a hash value that can be used to determine the original input, or to find an input that can produce the same hash, more efficiently than brute force techniques." }, "fullDescription": { "text": "This weakness is especially dangerous when the hash is used in security algorithms that require the one-way property to hold. For example, if an authentication system takes an incoming password and generates a hash, then compares the hash to another hash that it has stored in its authentication database, then the ability to create a collision could allow an attacker to provide an alternate password that produces the same target hash, bypassing authentication." }, "relationships": [ { "target": { "id": "CWE-326", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-327", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-329", "name": "Not Using an Unpredictable IV with CBC Mode", "shortDescription": { "text": "Not using an unpredictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key." }, "fullDescription": { "text": "CBC mode eliminates a weakness of Electronic Code\n\t Book (ECB) mode by allowing identical plaintext blocks to\n\t be encrypted to different ciphertext blocks. This is\n\t possible by the XOR-ing of an IV with the initial plaintext\n\t block so that every plaintext block in the chain is XOR'd\n\t with a different value before encryption. If IVs are\n\t reused, then identical plaintexts would be encrypted to\n\t identical ciphertexts. However, even if IVs are not\n\t identical but are predictable, then they still break the\n\t security of CBC mode against Chosen Plaintext Attacks\n\t (CPA)." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1204", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-330", "name": "Use of Insufficiently Random Values", "shortDescription": { "text": "The software uses insufficiently random numbers or values in a security context that depends on unpredictable numbers." }, "fullDescription": { "text": "When software 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." }, "relationships": [ { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-331", "name": "Insufficient Entropy", "shortDescription": { "text": "The software uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others." }, "relationships": [ { "target": { "id": "CWE-330", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-332", "name": "Insufficient Entropy in PRNG", "shortDescription": { "text": "The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat." }, "relationships": [ { "target": { "id": "CWE-331", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-333", "name": "Improper Handling of Insufficient Entropy in TRNG", "shortDescription": { "text": "True random number generators (TRNG) generally have a limited source of entropy and therefore can fail or block." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-331", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-334", "name": "Small Space of Random Values", "shortDescription": { "text": "The number of possible random values is smaller than needed by the product, making it more susceptible to brute force attacks." }, "relationships": [ { "target": { "id": "CWE-330", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-335", "name": "Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)", "shortDescription": { "text": "The software uses a Pseudo-Random Number Generator (PRNG) that does not correctly manage seeds." }, "relationships": [ { "target": { "id": "CWE-330", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-336", "name": "Same Seed in Pseudo-Random Number Generator (PRNG)", "shortDescription": { "text": "A Pseudo-Random Number Generator (PRNG) uses the same seed each time the product is initialized." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-335", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-337", "name": "Predictable Seed in Pseudo-Random Number Generator (PRNG)", "shortDescription": { "text": "A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-335", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-338", "name": "Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)", "shortDescription": { "text": "The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong." }, "fullDescription": { "text": "When a non-cryptographic PRNG is used in a cryptographic context, it can expose the cryptography to certain types of attacks.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." }, "relationships": [ { "target": { "id": "CWE-330", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-339", "name": "Small Seed Space in PRNG", "shortDescription": { "text": "A PRNG uses a relatively small space of seeds." }, "relationships": [ { "target": { "id": "CWE-335", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-341", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-340", "name": "Generation of Predictable Numbers or Identifiers", "shortDescription": { "text": "The product uses a scheme that generates numbers or identifiers that are more predictable than required." }, "relationships": [ { "target": { "id": "CWE-330", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-341", "name": "Predictable from Observable State", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-340", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-342", "name": "Predictable Exact Value from Previous Values", "shortDescription": { "text": "An exact value or random number can be precisely predicted by observing previous values." }, "relationships": [ { "target": { "id": "CWE-340", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-343", "name": "Predictable Value Range from Previous Values", "shortDescription": { "text": "The software'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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-340", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-344", "name": "Use of Invariant Value in Dynamically Changing Context", "shortDescription": { "text": "The product uses a constant value, name, or reference, but this value can (or should) vary across different environments." }, "relationships": [ { "target": { "id": "CWE-330", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-345", "name": "Insufficient Verification of Data Authenticity", "shortDescription": { "text": "The software does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data." }, "relationships": [ { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-346", "name": "Origin Validation Error", "shortDescription": { "text": "The software does not properly verify that the source of data or communication is valid." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-347", "name": "Improper Verification of Cryptographic Signature", "shortDescription": { "text": "The software does not verify, or incorrectly verifies, the cryptographic signature for data." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-348", "name": "Use of Less Trusted Source", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-349", "name": "Acceptance of Extraneous Untrusted Data With Trusted Data", "shortDescription": { "text": "The software, 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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-350", "name": "Reliance on Reverse DNS Resolution for a Security-Critical Action", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Since DNS names can be easily spoofed or misreported, and it may be difficult for the software to detect if a trusted DNS server has been compromised, DNS names do not constitute a valid authentication mechanism.When the software performs a reverse DNS resolution for an IP address, if an attacker controls the 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.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." }, "relationships": [ { "target": { "id": "CWE-290", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-807", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-351", "name": "Insufficient Type Distinction", "shortDescription": { "text": "The software does not properly distinguish between different types of elements in a way that leads to insecure behavior." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-352", "name": "Cross-Site Request Forgery (CSRF)", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-346", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-441", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-613", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-642", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] } ] }, { "id": "CWE-353", "name": "Missing Support for Integrity Check", "shortDescription": { "text": "The software uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-354", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-354", "name": "Improper Validation of Integrity Check Value", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-353", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-754", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-355", "name": "User Interface Security Issues", "fullDescription": { "text": "Weaknesses in this category are related to or introduced in the User Interface (UI)." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-317" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-356" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-357" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-447" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-448" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-449" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-450" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-549" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1007" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1021" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-356", "name": "Product UI does not Warn User of Unsafe Actions", "shortDescription": { "text": "The software'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." }, "fullDescription": { "text": "Software 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." }, "relationships": [ { "target": { "id": "CWE-221", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-357", "name": "Insufficient UI Warning of Dangerous Operations", "shortDescription": { "text": "The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention." }, "relationships": [ { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-358", "name": "Improperly Implemented Security Check for Standard", "shortDescription": { "text": "The software does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique." }, "relationships": [ { "target": { "id": "CWE-290", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-359", "name": "Exposure of Private Personal Information to an Unauthorized Actor", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.Some types of private information include:Government identifiers, such as Social Security NumbersContact information, such as home addresses and telephone numbersGeographic location - where the user is (or was)Employment historyFinancial data - such as credit card numbers, salary, bank accounts, and debtsPictures, video, or audioBehavioral patterns - such as web surfing history, when certain activities are performed, etc.Relationships (and types of relationships) with others - family, friends, contacts, etc.Communications - e-mail addresses, private messages, text messages, chat logs, etc.Health - medical conditions, insurance status, prescription recordsAccount passwords and other credentialsSome 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.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." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-360", "name": "Trust of System Event Data", "shortDescription": { "text": "Security based on event locations are insecure and can be spoofed." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-361", "name": "7PK - Time and State", "fullDescription": { "text": "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.\"" }, "relationships": [ { "target": { "id": "CWE-700" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-364" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-367" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-377" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-382" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-383" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-384" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-412" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-362", "name": "Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')", "shortDescription": { "text": "The program 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." }, "fullDescription": { "text": "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.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.A race condition violates these properties, which are closely related: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.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.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).The interfering code sequence could be \"trusted\" or \"untrusted.\" A trusted interfering code sequence occurs within the program; 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 program." }, "relationships": [ { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-363", "name": "Race Condition Enabling Link Following", "shortDescription": { "text": "The software 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 software to access the wrong file." }, "fullDescription": { "text": "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 software 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." }, "relationships": [ { "target": { "id": "CWE-59", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-367", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-364", "name": "Signal Handler Race Condition", "shortDescription": { "text": "The software uses a signal handler that introduces a race condition." }, "fullDescription": { "text": "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 software state to be corrupted, possibly leading to a denial of service or even code execution.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.There are several known behaviors related to signal handlers that have received the label of \"signal handler race condition\":Shared state (e.g. global data or static variables) that are accessible to both a signal handler and \"regular\" codeShared state between a signal handler and other signal handlersUse 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.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.Use of setjmp and longjmp, or other mechanisms that prevent a signal handler from returning control back to the original functionalityWhile 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.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:Avoiding shared stateUsing synchronization in the signal handlerUsing synchronization in the regular codeDisabling or masking other signals, which provides atomicity (which effectively ensures exclusivity)" }, "relationships": [ { "target": { "id": "CWE-123", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-415", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-416", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-365", "name": "Race Condition in Switch", "shortDescription": { "text": "The code contains a switch statement in which the switched variable can be modified while the switch is still executing, resulting in unexpected behavior." }, "fullDescription": { "text": "This issue is particularly important in the case of switch statements that involve fall-through style case statements - i.e., those which do not end with break. If the variable being tested by the switch changes in the course of execution, this could change the intended logic of the switch so much that it places the process in a contradictory state and in some cases could even result in memory corruption." }, "relationships": [ { "target": { "id": "CWE-364", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-366", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-367", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-366", "name": "Race Condition within a Thread", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-367", "name": "Time-of-check Time-of-use (TOCTOU) Race Condition", "shortDescription": { "text": "The software 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 software to perform invalid actions when the resource is in an unexpected state." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-368", "name": "Context Switching Race Condition", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-364", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] } ] }, { "id": "CWE-369", "name": "Divide By Zero", "shortDescription": { "text": "The product divides a value by zero." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-370", "name": "Missing Check for Certificate Revocation after Initial Check", "shortDescription": { "text": "The software does not check the revocation status of a certificate after its initial revocation check, which can cause the software to perform privileged actions even after the certificate is revoked at a later time." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-296", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-297", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-298", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-299", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-371", "name": "State Issues", "fullDescription": { "text": "Weaknesses in this category are related to improper management of system state." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-15" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-372" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-374" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-375" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1265" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-372", "name": "Incomplete Internal State Distinction", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-373", "name": "DEPRECATED: State Synchronization Error", "shortDescription": { "text": "This entry was deprecated because it overlapped the same concepts as race condition (CWE-362) and Improper Synchronization (CWE-662)." } }, { "id": "CWE-374", "name": "Passing Mutable Objects to an Untrusted Method", "shortDescription": { "text": "The program sends non-cloned mutable data as an argument to a method or function." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-375", "name": "Returning a Mutable Object to an Untrusted Caller", "shortDescription": { "text": "Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-376", "name": "DEPRECATED: Temporary File Issues", "fullDescription": { "text": "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)." } }, { "id": "CWE-377", "name": "Insecure Temporary File", "shortDescription": { "text": "Creating and using insecure temporary files can leave application and system data vulnerable to attack." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-378", "name": "Creation of Temporary File With Insecure Permissions", "shortDescription": { "text": "Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack." }, "relationships": [ { "target": { "id": "CWE-377", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-379", "name": "Creation of Temporary File in Directory with Insecure Permissions", "shortDescription": { "text": "The software creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-377", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-380", "name": "DEPRECATED: Technology-Specific Time and State Issues", "fullDescription": { "text": "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." } }, { "id": "CWE-381", "name": "DEPRECATED: J2EE Time and State Issues", "fullDescription": { "text": "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." } }, { "id": "CWE-382", "name": "J2EE Bad Practices: Use of System.exit()", "shortDescription": { "text": "A J2EE application uses System.exit(), which also shuts down its container." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-383", "name": "J2EE Bad Practices: Direct Use of Threads", "shortDescription": { "text": "Thread management in a Web application is forbidden in some circumstances and is always highly error prone." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-695", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-384", "name": "Session Fixation", "shortDescription": { "text": "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." }, "fullDescription": { "text": "Such a scenario is commonly observed when:A web application authenticates a user without first invalidating the existing session, thereby continuing to use the session already associated with the user.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.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." }, "relationships": [ { "target": { "id": "CWE-346", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-441", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-472", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-385", "name": "Covert Timing Channel", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-514", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-386", "name": "Symbolic Name not Mapping to Correct Object", "shortDescription": { "text": "A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time." }, "relationships": [ { "target": { "id": "CWE-367", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-486", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-387", "name": "Signal Errors", "fullDescription": { "text": "Weaknesses in this category are related to the improper handling of signals." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-364" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-432" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-828" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-831" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-388", "name": "7PK - Errors", "fullDescription": { "text": "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.\"" }, "relationships": [ { "target": { "id": "CWE-700" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-391" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-395" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-396" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-397" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-389", "name": "Error Conditions, Return Values, Status Codes", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-248" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-252" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-253" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-390" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-391" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-392" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-393" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-394" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-395" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-396" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-397" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-544" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-584" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-600" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-617" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-756" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1069" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-390", "name": "Detection of Error Condition Without Action", "shortDescription": { "text": "The software detects a specific error, but takes no actions to handle the error." }, "relationships": [ { "target": { "id": "CWE-401", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-391", "name": "Unchecked Error Condition", "shortDescription": { "text": "[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." }, "relationships": [ { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-392", "name": "Missing Report of Error Condition", "shortDescription": { "text": "The software encounters an error but does not provide a status code or return value to indicate that an error has occurred." }, "relationships": [ { "target": { "id": "CWE-684", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-393", "name": "Return of Wrong Status Code", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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 software to assume that an action is safe, even when it is not." }, "relationships": [ { "target": { "id": "CWE-684", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-394", "name": "Unexpected Status Code or Return Value", "shortDescription": { "text": "The software does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the software." }, "relationships": [ { "target": { "id": "CWE-754", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-395", "name": "Use of NullPointerException Catch to Detect NULL Pointer Dereference", "shortDescription": { "text": "Catching NullPointerException should not be used as an alternative to programmatic checks to prevent dereferencing a null pointer." }, "fullDescription": { "text": "Programmers typically catch NullPointerException under three circumstances:The program contains a null pointer dereference. Catching the resulting exception was easier than fixing the underlying problem.The program explicitly throws a NullPointerException to signal an error condition.The code is part of a test harness that supplies unexpected input to the classes under test.Of these three circumstances, only the last is acceptable." }, "relationships": [ { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-396", "name": "Declaration of Catch for Generic Exception", "shortDescription": { "text": "Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities." }, "fullDescription": { "text": "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 Java'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." }, "relationships": [ { "target": { "id": "CWE-221", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-397", "name": "Declaration of Throws for Generic Exception", "shortDescription": { "text": "Throwing overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-221", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-398", "name": "7PK - Code Quality", "fullDescription": { "text": "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.\"" }, "relationships": [ { "target": { "id": "CWE-700" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-401" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-404" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-415" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-416" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-457" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-474" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-475" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-476" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-477" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-399", "name": "Resource Management Errors", "fullDescription": { "text": "Weaknesses in this category are related to improper management of system resources." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-73" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-403" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-410" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-470" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-502" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-619" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-641" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-694" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-763" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-770" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-771" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-772" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-826" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-908" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-909" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-910" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-911" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-914" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-915" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-920" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1188" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-400", "name": "Uncontrolled Resource Consumption", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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 software, 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.There are at least three distinct scenarios which can commonly lead to resource exhaustion:Lack of throttling for the number of allocated resourcesLosing all references to a resource before reaching the shutdown stageNot closing/returning a resource after processingResource exhaustion problems are often result due to an incorrect implementation of the following situations:Error conditions and other exceptional circumstances.Confusion over which part of the program is responsible for releasing the resource." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-401", "name": "Missing Release of Memory after Effective Lifetime", "shortDescription": { "text": "The software does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-772", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-402", "name": "Transmission of Private Resources into a New Sphere ('Resource Leak')", "shortDescription": { "text": "The software makes resources available to untrusted parties when those resources are only intended to be accessed by the software." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-403", "name": "Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak')", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-402", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-404", "name": "Improper Resource Shutdown or Release", "shortDescription": { "text": "The program does not release or incorrectly releases a resource before it is made available for re-use." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-405", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-619", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-405", "name": "Asymmetric Resource Consumption (Amplification)", "shortDescription": { "text": "Software that does not appropriately monitor or control resource consumption can lead to adverse system performance." }, "fullDescription": { "text": "This situation is amplified if the software allows malicious users or attackers to consume more resources than their access level permits. Exploiting such a weakness can lead to asymmetric resource consumption, aiding in amplification attacks against the system or the network." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-406", "name": "Insufficient Control of Network Message Volume (Network Amplification)", "shortDescription": { "text": "The software does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the software to transmit more traffic than should be allowed for that actor." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-405", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-407", "name": "Inefficient Algorithmic Complexity", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-405", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-408", "name": "Incorrect Behavior Order: Early Amplification", "shortDescription": { "text": "The software allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place." }, "relationships": [ { "target": { "id": "CWE-405", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-696", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-409", "name": "Improper Handling of Highly Compressed Data (Data Amplification)", "shortDescription": { "text": "The software does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-405", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-410", "name": "Insufficient Resource Pool", "shortDescription": { "text": "The software'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." }, "fullDescription": { "text": "Frequently the consequence is a \"flood\" of connection or sessions." }, "relationships": [ { "target": { "id": "CWE-400", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-411", "name": "Resource Locking Problems", "fullDescription": { "text": "Weaknesses in this category are related to improper handling of locks that are used to control access to resources." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-412" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-413" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-414" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-609" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-764" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-765" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-832" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-833" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-412", "name": "Unrestricted Externally Accessible Lock", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This prevents the software 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." }, "relationships": [ { "target": { "id": "CWE-410", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-667", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-413", "name": "Improper Resource Locking", "shortDescription": { "text": "The software does not lock or does not correctly lock a resource when the software must have exclusive access to the resource." }, "fullDescription": { "text": "When a resource is not properly locked, an attacker could modify the resource while it is being operated on by the software. This might violate the software's assumption that the resource will not change, potentially leading to unexpected behaviors." }, "relationships": [ { "target": { "id": "CWE-667", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-414", "name": "Missing Lock Check", "shortDescription": { "text": "A product does not check to see if a lock is present before performing sensitive operations on a resource." }, "relationships": [ { "target": { "id": "CWE-667", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-415", "name": "Double Free", "shortDescription": { "text": "The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-123", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-416", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-666", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-675", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-825", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-416", "name": "Use After Free", "shortDescription": { "text": "Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code." }, "fullDescription": { "text": "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:Error conditions and other exceptional circumstances.Confusion over which part of the program is responsible for freeing the memory.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.If the newly allocated data chances 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." }, "relationships": [ { "target": { "id": "CWE-120", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-123", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-825", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-417", "name": "Communication Channel Errors", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-322" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-346" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-385" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-419" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-420" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-425" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-515" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-924" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-940" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-941" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-418", "name": "DEPRECATED: Channel Errors", "fullDescription": { "text": "This category has been deprecated because it redundant with the grouping provided by CWE-417." } }, { "id": "CWE-419", "name": "Unprotected Primary Channel", "shortDescription": { "text": "The software uses a primary channel for administration or restricted functionality, but it does not properly protect the channel." }, "relationships": [ { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-420", "name": "Unprotected Alternate Channel", "shortDescription": { "text": "The software protects a primary channel, but it does not use the same level of protection for an alternate channel." }, "relationships": [ { "target": { "id": "CWE-923", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-421", "name": "Race Condition During Access to Alternate Channel", "shortDescription": { "text": "The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors." }, "fullDescription": { "text": "This creates a race condition that allows an attacker to access the channel before the authorized user does." }, "relationships": [ { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-420", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-422", "name": "Unprotected Windows Messaging Channel ('Shatter')", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-360", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-420", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-423", "name": "DEPRECATED (Duplicate): Proxied Trusted Channel", "shortDescription": { "text": "This entry has been deprecated because it was a duplicate of CWE-441. All content has been transferred to CWE-441." } }, { "id": "CWE-424", "name": "Improper Protection of Alternate Path", "shortDescription": { "text": "The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources." }, "relationships": [ { "target": { "id": "CWE-638", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-425", "name": "Direct Request ('Forced Browsing')", "shortDescription": { "text": "The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-98", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-288", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-424", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-471", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-862", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-426", "name": "Untrusted Search Path", "shortDescription": { "text": "The application searches for critical resources using an externally-supplied search path that can point to resources that are not under the application's direct control." }, "fullDescription": { "text": "This might allow attackers to execute their own programs, access unauthorized data files, or modify configuration in unexpected ways. If the application 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 application would then execute. The problem extends to any type of critical resource that the application trusts.Some of the most common variants of untrusted search path are: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.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." }, "relationships": [ { "target": { "id": "CWE-427", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-428", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-642", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-673", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-427", "name": "Uncontrolled Search Path Element", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.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:the directory from which the program has been loadedthe current working directory.In some cases, the attack can be conducted remotely, such as when SMB or WebDAV network shares are used.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.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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-428", "name": "Unquoted Search Path or Element", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-429", "name": "Handler Errors", "fullDescription": { "text": "Weaknesses in this category are related to improper management of handlers." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-430" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-431" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-432" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-433" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-434" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-479" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-430", "name": "Deployment of Wrong Handler", "shortDescription": { "text": "The wrong \"handler\" is assigned to process an object." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-433", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-434", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-431", "name": "Missing Handler", "shortDescription": { "text": "A handler is not available or implemented." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-433", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-432", "name": "Dangerous Signal Handler not Disabled During Sensitive Operations", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-364", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-433", "name": "Unparsed Raw Web Content Delivery", "shortDescription": { "text": "The software stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-219", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-434", "name": "Unrestricted Upload of File with Dangerous Type", "shortDescription": { "text": "The software allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment." }, "relationships": [ { "target": { "id": "CWE-351", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-430", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-435", "name": "Improper Interaction Between Multiple Correctly-Behaving Entities", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." } }, { "id": "CWE-436", "name": "Interpretation Conflict", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-435", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-437", "name": "Incomplete Model of Endpoint Features", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-438", "name": "Behavioral Problems", "fullDescription": { "text": "Weaknesses in this category are related to unexpected behaviors from code that an application uses." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-115" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-179" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-408" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-437" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-439" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-440" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-444" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-480" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-483" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-484" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-551" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-698" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-733" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-783" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-835" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-837" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-841" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1025" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1037" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-439", "name": "Behavioral Change in New Version or Environment", "shortDescription": { "text": "A's behavior or functionality changes with a new version of A, or a new environment, which is not known (or manageable) by B." }, "relationships": [ { "target": { "id": "CWE-435", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-440", "name": "Expected Behavior Violation", "shortDescription": { "text": "A feature, API, or function does not perform according to its specification." }, "relationships": [ { "target": { "id": "CWE-684", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-441", "name": "Unintended Proxy or Intermediary ('Confused Deputy')", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.Since proxy functionality and message-forwarding often serve a legitimate purpose, this issue only becomes a vulnerability when:The product runs with different privileges or on a different system, or otherwise has different levels of access than the upstream component;The attacker is prevented from making the request directly to the target; andThe 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." }, "relationships": [ { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-442", "name": "DEPRECATED: Web Problems", "fullDescription": { "text": "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." } }, { "id": "CWE-443", "name": "DEPRECATED (Duplicate): HTTP response splitting", "shortDescription": { "text": "This weakness can be found at CWE-113." } }, { "id": "CWE-444", "name": "Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling')", "shortDescription": { "text": "When malformed or abnormal HTTP requests are interpreted by one or more entities in the data flow between the user and the web server, such as a proxy or firewall, they can be interpreted inconsistently, allowing the attacker to \"smuggle\" a request to one device without the other device being aware of it." }, "relationships": [ { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-445", "name": "DEPRECATED: User Interface Errors", "fullDescription": { "text": "This weakness has been deprecated because it was a duplicate of CWE-355. All content has been transferred to CWE-355." } }, { "id": "CWE-446", "name": "UI Discrepancy for Security Feature", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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 software does not actually enable the encryption. Alternately, the user might provide a \"restrict ALL'\" access control rule, but the software only implements \"restrict SOME\"." }, "relationships": [ { "target": { "id": "CWE-684", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-447", "name": "Unimplemented or Unsupported Feature in UI", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-446", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-671", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-448", "name": "Obsolete Feature in UI", "shortDescription": { "text": "A UI function is obsolete and the product does not warn the user." }, "relationships": [ { "target": { "id": "CWE-446", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-449", "name": "The UI Performs the Wrong Action", "shortDescription": { "text": "The UI performs the wrong action with respect to the user's request." }, "relationships": [ { "target": { "id": "CWE-446", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-450", "name": "Multiple Interpretations of UI Input", "shortDescription": { "text": "The UI has multiple interpretations of user input but does not prompt the user when it selects the less secure interpretation." }, "relationships": [ { "target": { "id": "CWE-357", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-451", "name": "User Interface (UI) Misrepresentation of Critical Information", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.UI misrepresentation can take many forms:Incorrect indicator: incorrect information is displayed, which prevents the user from understanding the true state of the software or the environment the software is monitoring, especially of potentially-dangerous conditions or operations. This can be broken down into several different subtypes.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.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)Timing: the software 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.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.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.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." }, "relationships": [ { "target": { "id": "CWE-221", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-346", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-684", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-452", "name": "Initialization and Cleanup Errors", "fullDescription": { "text": "Weaknesses in this category occur in behaviors that are used for initialization and breakdown." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-226" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-454" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-455" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-459" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-460" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1051" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1052" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1188" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-453", "name": "Insecure Default Variable Initialization", "shortDescription": { "text": "The software, by default, initializes an internal variable with an insecure or less secure value than is possible." }, "relationships": [ { "target": { "id": "CWE-1188", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-454", "name": "External Initialization of Trusted Variables or Data Stores", "shortDescription": { "text": "The software initializes critical internal variables or data stores using inputs that can be modified by untrusted actors." }, "fullDescription": { "text": "A software 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." }, "relationships": [ { "target": { "id": "CWE-456", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-665", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-455", "name": "Non-exit on Failed Initialization", "shortDescription": { "text": "The software 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, which can cause the software to execute in a less secure fashion than intended by the administrator." }, "relationships": [ { "target": { "id": "CWE-636", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-665", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-456", "name": "Missing Initialization of a Variable", "shortDescription": { "text": "The software does not initialize critical variables, which causes the execution environment to use unexpected values." }, "relationships": [ { "target": { "id": "CWE-89", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-98", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-120", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-457", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-665", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-909", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-457", "name": "Use of Uninitialized Variable", "shortDescription": { "text": "The code uses a variable that has not been initialized, leading to unpredictable or unintended results." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-665", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-908", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-458", "name": "DEPRECATED: Incorrect Initialization", "shortDescription": { "text": "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." } }, { "id": "CWE-459", "name": "Incomplete Cleanup", "shortDescription": { "text": "The software does not properly \"clean up\" and remove temporary or supporting resources after they have been used." }, "relationships": [ { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-460", "name": "Improper Cleanup on Thrown Exception", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-459", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-461", "name": "DEPRECATED: Data Structure Issues", "fullDescription": { "text": "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." } }, { "id": "CWE-462", "name": "Duplicate Key in Associative List (Alist)", "shortDescription": { "text": "Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-694", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-463", "name": "Deletion of Data Structure Sentinel", "shortDescription": { "text": "The accidental deletion of a data-structure sentinel can cause serious programming logic problems." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-464", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-707", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-464", "name": "Addition of Data Structure Sentinel", "shortDescription": { "text": "The accidental addition of a data-structure sentinel can cause serious programming logic problems." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-465", "name": "Pointer Issues", "fullDescription": { "text": "Weaknesses in this category are related to improper handling of pointers." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-466" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-467" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-468" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-469" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-476" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-587" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-588" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-763" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-822" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-823" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-824" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-825" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-466", "name": "Return of Pointer Value Outside of Expected Range", "shortDescription": { "text": "A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-467", "name": "Use of sizeof() on a Pointer Type", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-131", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-468", "name": "Incorrect Pointer Scaling", "shortDescription": { "text": "In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled." }, "relationships": [ { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-469", "name": "Use of Pointer Subtraction to Determine Size", "shortDescription": { "text": "The application 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." }, "relationships": [ { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-470", "name": "Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "If the application 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 application 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 application's classpath (CWE-427) or add new entries to the application's classpath (CWE-426). Under either of these conditions, the attacker can use reflection to introduce new, malicious behavior into the application." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-913", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-471", "name": "Modification of Assumed-Immutable Data (MAID)", "shortDescription": { "text": "The software does not properly protect an assumed-immutable element from being modified by an attacker." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-472", "name": "External Control of Assumed-Immutable Web Parameter", "shortDescription": { "text": "The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-471", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-642", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-473", "name": "PHP External Variable Modification", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-98", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-471", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-474", "name": "Use of Function with Inconsistent Implementations", "shortDescription": { "text": "The code uses a function that has inconsistent implementations across operating systems and versions." }, "fullDescription": { "text": "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.The implementation of many functions varies by platform, and at times, even by different versions of the same platform. Implementation differences can include:Slight differences in the way parameters are interpreted leading to inconsistent results.Some implementations of the function carry significant security risks.The function might not be defined on all platforms.The function might change which return codes it can provide, or change the meaning of its return codes." }, "relationships": [ { "target": { "id": "CWE-758", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-475", "name": "Undefined Behavior for Input to API", "shortDescription": { "text": "The behavior of this function is undefined unless its control parameter is set to a specific value." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-476", "name": "NULL Pointer Dereference", "shortDescription": { "text": "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." }, "fullDescription": { "text": "NULL pointer dereference issues can occur through a number of flaws, including race conditions, and simple programming omissions." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-754", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-477", "name": "Use of Obsolete Function", "shortDescription": { "text": "The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained." }, "fullDescription": { "text": "As programming languages evolve, functions occasionally become obsolete due to:Advances in the languageImproved understanding of how operations should be performed effectively and securelyChanges in the conventions that govern certain operationsFunctions that are removed are usually replaced by newer counterparts that perform the same task in some different and hopefully improved way." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-478", "name": "Missing Default Case in Switch Statement", "shortDescription": { "text": "The code does not have a default case in a switch statement, which might lead to complex logical errors and resultant weaknesses." }, "fullDescription": { "text": "This flaw represents a common problem in software development, in which not all possible values for a variable are considered or handled by a given process. 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." }, "relationships": [ { "target": { "id": "CWE-1023", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-479", "name": "Signal Handler Use of a Non-reentrant Function", "shortDescription": { "text": "The program defines a signal handler that calls a non-reentrant function." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-123", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-663", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-828", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-480", "name": "Use of Incorrect Operator", "shortDescription": { "text": "The programmer accidentally uses the wrong operator, which changes the application logic in security-relevant ways." }, "fullDescription": { "text": "These types of errors are generally the result of a typo." }, "relationships": [ { "target": { "id": "CWE-670", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-481", "name": "Assigning instead of Comparing", "shortDescription": { "text": "The code uses an operator for assignment when the intention was to perform a comparison." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-480", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-697", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-482", "name": "Comparing instead of Assigning", "shortDescription": { "text": "The code uses an operator for comparison when the intention was to perform an assignment." }, "fullDescription": { "text": "In many languages, the compare statement is very close in appearance to the assignment statement; they are often confused." }, "relationships": [ { "target": { "id": "CWE-480", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-483", "name": "Incorrect Block Delimitation", "shortDescription": { "text": "The code does not explicitly delimit a block that is intended to contain 2 or more statements, creating a logic error." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-670", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-484", "name": "Omitted Break Statement in Switch", "shortDescription": { "text": "The program 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." }, "fullDescription": { "text": "This can lead to critical code executing in situations where it should not." }, "relationships": [ { "target": { "id": "CWE-670", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-485", "name": "7PK - Encapsulation", "fullDescription": { "text": "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.\"" }, "relationships": [ { "target": { "id": "CWE-700" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-486" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-488" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-489" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-491" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-492" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-493" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-495" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-496" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-497" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-501" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-486", "name": "Comparison of Classes by Name", "shortDescription": { "text": "The program compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1025", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-487", "name": "Reliance on Package-level Scope", "shortDescription": { "text": "Java packages are not inherently closed; therefore, relying on them for code security is not a good practice." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-488", "name": "Exposure of Data Element to Wrong Session", "shortDescription": { "text": "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." }, "fullDescription": { "text": "Data can \"bleed\" from one session to another through member variables of singleton objects, such as Servlets, and objects from a shared pool.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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-489", "name": "Active Debug Code", "shortDescription": { "text": "The application is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information." }, "fullDescription": { "text": "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 application. 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 application." }, "relationships": [ { "target": { "id": "CWE-215", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-490", "name": "DEPRECATED: Mobile Code Issues", "fullDescription": { "text": "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." } }, { "id": "CWE-491", "name": "Public cloneable() Method Without Final ('Object Hijack')", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-492", "name": "Use of Inner Class Containing Sensitive Data", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-493", "name": "Critical Public Variable Without Final Modifier", "shortDescription": { "text": "The product has a critical public variable that is not final, which allows the variable to be modified to contain unexpected values." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-494", "name": "Download of Code Without Integrity Check", "shortDescription": { "text": "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." }, "fullDescription": { "text": "An attacker can execute malicious code by compromising the host server, performing DNS spoofing, or modifying the code in transit." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-495", "name": "Private Data Structure Returned From A Public Method", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-496", "name": "Public Data Assigned to Private Array-Typed Field", "shortDescription": { "text": "Assigning public data to a private array is equivalent to giving public access to the array." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-497", "name": "Exposure of Sensitive System Information to an Unauthorized Control Sphere", "shortDescription": { "text": "The application 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 application does." }, "fullDescription": { "text": "Network-based software, such as web applications, often runs on top of an operating system or similar environment. When the application 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 application itself, or buried within diagnostic or debugging messages. Debugging information helps an adversary learn about the system and form an attack plan.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. An application may use diagnostic methods that provide significant implementation details such as stack traces as part of its error handling mechanism." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-498", "name": "Cloneable Class Containing Sensitive Information", "shortDescription": { "text": "The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-499", "name": "Serializable Class Containing Sensitive Data", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-500", "name": "Public Static Field Not Marked Final", "shortDescription": { "text": "An object contains a public static field that is not marked final, which might allow it to be modified in unexpected ways." }, "fullDescription": { "text": "Public static variables can be read without an accessor and changed without a mutator by any classes in the application." }, "relationships": [ { "target": { "id": "CWE-493", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-501", "name": "Trust Boundary Violation", "shortDescription": { "text": "The product mixes trusted and untrusted data in the same data structure or structured message." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-502", "name": "Deserialization of Untrusted Data", "shortDescription": { "text": "The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid." }, "fullDescription": { "text": "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.Data that is untrusted can not be trusted to be well-formed.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." }, "relationships": [ { "target": { "id": "CWE-913", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-915", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-503", "name": "DEPRECATED: Byte/Object Code", "fullDescription": { "text": "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." } }, { "id": "CWE-504", "name": "DEPRECATED: Motivation/Intent", "fullDescription": { "text": "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." } }, { "id": "CWE-505", "name": "DEPRECATED: Intentionally Introduced Weakness", "fullDescription": { "text": "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." } }, { "id": "CWE-506", "name": "Embedded Malicious Code", "shortDescription": { "text": "The application contains code that appears to be malicious in nature." }, "fullDescription": { "text": "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 an application 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." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-507", "name": "Trojan Horse", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-506", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-508", "name": "Non-Replicating Malicious Code", "shortDescription": { "text": "Non-replicating malicious code only resides on the target system or software that is attacked; it does not attempt to spread to other systems." }, "relationships": [ { "target": { "id": "CWE-507", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-509", "name": "Replicating Malicious Code (Virus or Worm)", "shortDescription": { "text": "Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or software." }, "relationships": [ { "target": { "id": "CWE-507", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-510", "name": "Trapdoor", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-506", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-511", "name": "Logic/Time Bomb", "shortDescription": { "text": "The software contains code that is designed to disrupt the legitimate operation of the software (or its environment) when a certain time passes, or when a certain logical condition is met." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-506", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-512", "name": "Spyware", "shortDescription": { "text": "The software collects personally identifiable information about a human user or the user's activities, but the software accesses this information using other resources besides itself, and it does not require that user's explicit approval or direct input into the software." }, "fullDescription": { "text": "\"Spyware\" is a commonly used term with many definitions and interpretations. In general, it is meant to software that collects information or installs 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." }, "relationships": [ { "target": { "id": "CWE-506", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-513", "name": "DEPRECATED: Intentionally Introduced Nonmalicious Weakness", "fullDescription": { "text": "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." } }, { "id": "CWE-514", "name": "Covert Channel", "shortDescription": { "text": "A covert channel is a path that can be used to transfer information in a way not intended by the system's designers." }, "fullDescription": { "text": "Typically the system has not given authorization for the transmission and has no knowledge of its occurrence." }, "relationships": [ { "target": { "id": "CWE-1229", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-515", "name": "Covert Storage Channel", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-514", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-516", "name": "DEPRECATED (Duplicate): Covert Timing Channel", "shortDescription": { "text": "This weakness can be found at CWE-385." } }, { "id": "CWE-517", "name": "DEPRECATED: Other Intentional, Nonmalicious Weakness", "fullDescription": { "text": "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." } }, { "id": "CWE-518", "name": "DEPRECATED: Inadvertently Introduced Weakness", "fullDescription": { "text": "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." } }, { "id": "CWE-519", "name": "DEPRECATED: .NET Environment Issues", "fullDescription": { "text": "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." } }, { "id": "CWE-520", "name": ".NET Misconfiguration: Use of Impersonation", "shortDescription": { "text": "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." }, "fullDescription": { "text": ".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." }, "relationships": [ { "target": { "id": "CWE-266", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-521", "name": "Weak Password Requirements", "shortDescription": { "text": "The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-522", "name": "Insufficiently Protected Credentials", "shortDescription": { "text": "The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-523", "name": "Unprotected Transport of Credentials", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-312", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] }, { "target": { "id": "CWE-522", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-524", "name": "Use of Cache Containing Sensitive Information", "shortDescription": { "text": "The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere." }, "fullDescription": { "text": "\n\t 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.\n\t " }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-525", "name": "Use of Web Browser Cache Containing Sensitive Information", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-524", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-526", "name": "Exposure of Sensitive Information Through Environmental Variables", "shortDescription": { "text": "Environmental variables may contain sensitive information about a remote server." }, "relationships": [ { "target": { "id": "CWE-497", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-527", "name": "Exposure of Version-Control Repository to an Unauthorized Control Sphere", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-528", "name": "Exposure of Core Dump File to an Unauthorized Control Sphere", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-529", "name": "Exposure of Access Control List Files to an Unauthorized Control Sphere", "shortDescription": { "text": "The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-530", "name": "Exposure of Backup File to an Unauthorized Control Sphere", "shortDescription": { "text": "A backup file is stored in a directory or archive that is made accessible to unauthorized actors." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-531", "name": "Inclusion of Sensitive Information in Test Code", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-540", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-532", "name": "Insertion of Sensitive Information into Log File", "shortDescription": { "text": "Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information." }, "fullDescription": { "text": "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.Different log files may be produced and stored for: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.log files that are used for debugging" }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-538", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-533", "name": "DEPRECATED: Information Exposure Through Server Log Files", "shortDescription": { "text": "This entry has been deprecated because its abstraction was too low-level. See CWE-532." } }, { "id": "CWE-534", "name": "DEPRECATED: Information Exposure Through Debug Log Files", "shortDescription": { "text": "This entry has been deprecated because its abstraction was too low-level. See CWE-532." } }, { "id": "CWE-535", "name": "Exposure of Information Through Shell Error Message", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-211", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-536", "name": "Servlet Runtime Error Message Containing Sensitive Information", "shortDescription": { "text": "A servlet error message indicates that there exists an unhandled exception in your web application code and may provide useful information to an attacker." }, "relationships": [ { "target": { "id": "CWE-211", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-537", "name": "Java Runtime Error Message Containing Sensitive Information", "shortDescription": { "text": "In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system." }, "relationships": [ { "target": { "id": "CWE-211", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-538", "name": "Insertion of Sensitive Information into Externally-Accessible File or Directory", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-200", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-539", "name": "Use of Persistent Cookies Containing Sensitive Information", "shortDescription": { "text": "The web application uses persistent cookies, but the cookies contain sensitive information." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-540", "name": "Inclusion of Sensitive Information in Source Code", "shortDescription": { "text": "Source code on a web server or repository often contains sensitive information and should generally not be accessible to users." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-538", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-541", "name": "Inclusion of Sensitive Information in an Include File", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-540", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-542", "name": "DEPRECATED: Information Exposure Through Cleanup Log Files", "shortDescription": { "text": "This entry has been deprecated because its abstraction was too low-level. See CWE-532." } }, { "id": "CWE-543", "name": "Use of Singleton Pattern Without Synchronization in a Multithreaded Context", "shortDescription": { "text": "The software uses the singleton pattern when creating a resource within a multithreaded environment." }, "fullDescription": { "text": "The use of a singleton pattern may not be thread-safe." }, "relationships": [ { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-820", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-544", "name": "Missing Standardized Error Handling Mechanism", "shortDescription": { "text": "The software does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses." }, "fullDescription": { "text": "If the application 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." }, "relationships": [ { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-545", "name": "DEPRECATED: Use of Dynamic Class Loading", "shortDescription": { "text": "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." } }, { "id": "CWE-546", "name": "Suspicious Comment", "shortDescription": { "text": "The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1078", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-547", "name": "Use of Hard-coded, Security-relevant Constants", "shortDescription": { "text": "The program 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1078", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-548", "name": "Exposure of Information Through Directory Listing", "shortDescription": { "text": "A directory listing is inappropriately exposed, yielding potentially sensitive information to attackers." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-497", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-549", "name": "Missing Password Field Masking", "shortDescription": { "text": "The software does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords." }, "relationships": [ { "target": { "id": "CWE-522", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-550", "name": "Server-generated Error Message Containing Sensitive Information", "shortDescription": { "text": "Certain conditions, such as network failure, will cause a server error message to be displayed." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-209", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-551", "name": "Incorrect Behavior Order: Authorization Before Parsing and Canonicalization", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-696", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-863", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-552", "name": "Files or Directories Accessible to External Parties", "shortDescription": { "text": "The product makes files or directories accessible to unauthorized actors, even though they should not be." }, "fullDescription": { "text": "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.\n\t " }, "relationships": [ { "target": { "id": "CWE-285", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-553", "name": "Command Shell in Externally Accessible Directory", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-552", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-554", "name": "ASP.NET Misconfiguration: Not Using Input Validation Framework", "shortDescription": { "text": "The ASP.NET application does not use an input validation framework." }, "relationships": [ { "target": { "id": "CWE-1173", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-555", "name": "J2EE Misconfiguration: Plaintext Password in Configuration File", "shortDescription": { "text": "The J2EE application stores a plaintext password in a configuration file." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-260", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-556", "name": "ASP.NET Misconfiguration: Use of Identity Impersonation", "shortDescription": { "text": "Configuring an ASP.NET application to run with impersonated credentials may give the application unnecessary privileges." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-266", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-557", "name": "Concurrency Issues", "fullDescription": { "text": "Weaknesses in this category are related to concurrent use of shared resources." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-363" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-364" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-365" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-366" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-367" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-368" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-386" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-421" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-567" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-585" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-663" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-820" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-821" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1058" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1088" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-558", "name": "Use of getlogin() in Multithreaded Application", "shortDescription": { "text": "The application uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-663", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-559", "name": "DEPRECATED: Often Misused: Arguments and Parameters", "fullDescription": { "text": "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." } }, { "id": "CWE-560", "name": "Use of umask() with chmod-style Argument", "shortDescription": { "text": "The product calls umask() with an incorrect argument that is specified as if it is an argument to chmod()." }, "relationships": [ { "target": { "id": "CWE-687", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-561", "name": "Dead Code", "shortDescription": { "text": "The software contains dead code, which can never be executed." }, "fullDescription": { "text": "Dead code is source 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." }, "relationships": [ { "target": { "id": "CWE-1164", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-562", "name": "Return of Stack Variable Address", "shortDescription": { "text": "A function returns the address of a stack variable, which will cause unintended program behavior, typically in the form of a crash." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-758", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-825", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-563", "name": "Assignment to Variable without Use", "shortDescription": { "text": "The variable's value is assigned but never used, making it a dead store." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1164", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-564", "name": "SQL Injection: Hibernate", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-89", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-565", "name": "Reliance on Cookies without Validation and Integrity Checking", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-602", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-642", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-566", "name": "Authorization Bypass Through User-Controlled SQL Primary Key", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "When a user can set a primary key to any value, then the user can modify the key to point to unauthorized records.Database access control errors occur when:Data enters a program from an untrusted source.The data is used to specify the value of a primary key in a SQL query.The untrusted source does not have the permissions to be able to access all rows in the associated table." }, "relationships": [ { "target": { "id": "CWE-639", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-567", "name": "Unsynchronized Access to Shared Data in a Multithreaded Context", "shortDescription": { "text": "The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes." }, "fullDescription": { "text": "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.Note that this weakness is not unique to servlets." }, "relationships": [ { "target": { "id": "CWE-488", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-820", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-568", "name": "finalize() Method Without super.finalize()", "shortDescription": { "text": "The software contains a finalize() method that does not call super.finalize()." }, "fullDescription": { "text": "The Java Language Specification states that it is a good practice for a finalize() method to call super.finalize()." }, "relationships": [ { "target": { "id": "CWE-459", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-569", "name": "Expression Issues", "fullDescription": { "text": "Weaknesses in this category are related to incorrectly written expressions within code." }, "relationships": [ { "target": { "id": "CWE-699" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-480" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-570" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-571" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-588" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-595" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-783" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-570", "name": "Expression is Always False", "shortDescription": { "text": "The software contains an expression that will always evaluate to false." }, "relationships": [ { "target": { "id": "CWE-561", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-571", "name": "Expression is Always True", "shortDescription": { "text": "The software contains an expression that will always evaluate to true." }, "relationships": [ { "target": { "id": "CWE-561", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-572", "name": "Call to Thread run() instead of start()", "shortDescription": { "text": "The program 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-821", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-573", "name": "Improper Following of Specification by Caller", "shortDescription": { "text": "The software does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-574", "name": "EJB Bad Practices: Use of Synchronization Primitives", "shortDescription": { "text": "The program violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives." }, "fullDescription": { "text": "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 program 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.\"" }, "relationships": [ { "target": { "id": "CWE-695", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-821", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-575", "name": "EJB Bad Practices: Use of AWT Swing", "shortDescription": { "text": "The program violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing." }, "fullDescription": { "text": "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 program 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.\"" }, "relationships": [ { "target": { "id": "CWE-695", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-576", "name": "EJB Bad Practices: Use of Java I/O", "shortDescription": { "text": "The program violates the Enterprise JavaBeans (EJB) specification by using the java.io package." }, "fullDescription": { "text": "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 program 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.\"" }, "relationships": [ { "target": { "id": "CWE-695", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-577", "name": "EJB Bad Practices: Use of Sockets", "shortDescription": { "text": "The program violates the Enterprise JavaBeans (EJB) specification by using sockets." }, "fullDescription": { "text": "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 program 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.\"" }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-578", "name": "EJB Bad Practices: Use of Class Loader", "shortDescription": { "text": "The program violates the Enterprise JavaBeans (EJB) specification by using the class loader." }, "fullDescription": { "text": "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 program 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.\"" }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-579", "name": "J2EE Bad Practices: Non-serializable Object Stored in Session", "shortDescription": { "text": "The application stores a non-serializable object as an HttpSession attribute, which can hurt reliability." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-580", "name": "clone() Method Without super.clone()", "shortDescription": { "text": "The software contains a clone() method that does not call super.clone() to obtain the new object." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-581", "name": "Object Model Violation: Just One of Equals and Hashcode Defined", "shortDescription": { "text": "The software does not maintain equal hashcodes for equal objects." }, "fullDescription": { "text": "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()." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-697", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-582", "name": "Array Declared Public, Final, and Static", "shortDescription": { "text": "The program declares an array public, final, and static, which is not sufficient to prevent the array's contents from being modified." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-583", "name": "finalize() Method Declared Public", "shortDescription": { "text": "The program violates secure coding principles for mobile code by declaring a finalize() method public." }, "fullDescription": { "text": "A program 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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-584", "name": "Return Inside Finally Block", "shortDescription": { "text": "The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded." }, "relationships": [ { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-585", "name": "Empty Synchronized Block", "shortDescription": { "text": "The software contains an empty synchronized block." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1071", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-586", "name": "Explicit Call to Finalize()", "shortDescription": { "text": "The software makes an explicit call to the finalize() method from outside the finalizer." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1076", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-587", "name": "Assignment of a Fixed Address to a Pointer", "shortDescription": { "text": "The software sets a pointer to a specific address other than NULL or 0." }, "fullDescription": { "text": "Using a fixed address is not portable, because that address will probably not be valid in all environments or platforms." }, "relationships": [ { "target": { "id": "CWE-344", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-758", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-588", "name": "Attempt to Access Child of a Non-structure Pointer", "shortDescription": { "text": "Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption." }, "relationships": [ { "target": { "id": "CWE-704", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-758", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-589", "name": "Call to Non-ubiquitous API", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-474", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-590", "name": "Free of Memory not on the Heap", "shortDescription": { "text": "The application calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc()." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-123", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-762", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-591", "name": "Sensitive Data Storage in Improperly Locked Memory", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-413", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-592", "name": "DEPRECATED: Authentication Bypass Issues", "shortDescription": { "text": "This weakness has been deprecated because it covered redundant concepts already described in CWE-287." } }, { "id": "CWE-593", "name": "Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created", "shortDescription": { "text": "The software modifies the SSL context after connection creation has begun." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-666", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-594", "name": "J2EE Framework: Saving Unserializable Objects to Disk", "shortDescription": { "text": "When the J2EE container attempts to write unserializable objects to disk there is no guarantee that the process will complete successfully." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-595", "name": "Comparison of Object References Instead of Object Contents", "shortDescription": { "text": "The program compares object references instead of the contents of the objects themselves, preventing it from detecting equivalent objects." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1025", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-596", "name": "DEPRECATED: Incorrect Semantic Object Comparison", "shortDescription": { "text": "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." } }, { "id": "CWE-597", "name": "Use of Wrong Operator in String Comparison", "shortDescription": { "text": "The product uses the wrong operator when comparing a string, such as using \"==\" when the .equals() method should be used instead." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-480", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-595", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-598", "name": "Use of GET Request Method With Sensitive Query Strings", "shortDescription": { "text": "The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that requests." }, "fullDescription": { "text": "The query string can 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.\n\t " }, "relationships": [ { "target": { "id": "CWE-201", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-599", "name": "Missing Validation of OpenSSL Certificate", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-295", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-600", "name": "Uncaught Exception in Servlet ", "shortDescription": { "text": "The Servlet does not catch all exceptions, which may reveal sensitive debugging information." }, "fullDescription": { "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. 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." }, "relationships": [ { "target": { "id": "CWE-209", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-248", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-390", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-601", "name": "URL Redirection to Untrusted Site ('Open Redirect')", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-602", "name": "Client-Side Enforcement of Server-Side Security", "shortDescription": { "text": "The software is composed of a server that relies on the client to implement a mechanism that is intended to protect the server." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-290", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-300", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-471", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-603", "name": "Use of Client-Side Authentication", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-300", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-602", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-656", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-604", "name": "Deprecated Entries", "fullDescription": { "text": "CWE nodes in this view (slice) have been deprecated. There should be a reference pointing to the replacement in each deprecated weakness." } }, { "id": "CWE-605", "name": "Multiple Binds to the Same Port", "shortDescription": { "text": "When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-666", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-675", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-606", "name": "Unchecked Input for Loop Condition", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-834", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-1284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-607", "name": "Public Static Final Field References Mutable Object", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-471", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-608", "name": "Struts: Non-private Field in ActionForm Class", "shortDescription": { "text": "An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-609", "name": "Double-Checked Locking", "shortDescription": { "text": "The program uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient." }, "fullDescription": { "text": "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 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." }, "relationships": [ { "target": { "id": "CWE-367", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-667", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-610", "name": "Externally Controlled Reference to a Resource in Another Sphere", "shortDescription": { "text": "The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-611", "name": "Improper Restriction of XML External Entity Reference", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.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.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." }, "relationships": [ { "target": { "id": "CWE-441", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-610", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-612", "name": "Improper Authorization of Index Containing Sensitive Information", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1230", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-613", "name": "Insufficient Session Expiration", "shortDescription": { "text": "According to WASC, \"Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.\"" }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-614", "name": "Sensitive Cookie in HTTPS Session Without 'Secure' Attribute", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-311", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-615", "name": "Inclusion of Sensitive Information in Source Code Comments", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-540", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-546", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-616", "name": "Incomplete Identification of Uploaded File Variables (PHP)", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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\"." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-473", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-617", "name": "Reachable Assertion", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-670", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-618", "name": "Exposed Unsafe ActiveX Method", "shortDescription": { "text": "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)." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-749", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-619", "name": "Dangling Database Cursor ('Cursor Injection')", "shortDescription": { "text": "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.\"" }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-402", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-620", "name": "Unverified Password Change", "shortDescription": { "text": "When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication." }, "fullDescription": { "text": "This could be used by an attacker to change passwords for another user, thus gaining the privileges associated with that user." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-621", "name": "Variable Extraction Error", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.Similar functionality is possible in other interpreted languages, including custom languages." }, "relationships": [ { "target": { "id": "CWE-471", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-914", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-622", "name": "Improper Validation of Function Hook Arguments", "shortDescription": { "text": "The product adds hooks to user-accessible API functions, but it does not properly validate the arguments. This could lead to resultant vulnerabilities." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-623", "name": "Unsafe ActiveX Control Marked Safe For Scripting", "shortDescription": { "text": "An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-267", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-618", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-624", "name": "Executable Regular Expression Error", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-77", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-625", "name": "Permissive Regular Expression", "shortDescription": { "text": "The product uses a regular expression that does not sufficiently restrict the set of allowed values." }, "fullDescription": { "text": "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:not identifying the beginning and end of the target stringusing wildcards instead of acceptable character rangesothers" }, "relationships": [ { "target": { "id": "CWE-183", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-184", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-185", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-187", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-626", "name": "Null Byte Interaction Error (Poison Null Byte)", "shortDescription": { "text": "The product does not properly handle null bytes or NUL characters when passing data between different representations or components." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-147", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-627", "name": "Dynamic Variable Evaluation", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-183", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-914", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-628", "name": "Function Call with Incorrectly Specified Arguments", "shortDescription": { "text": "The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses." }, "fullDescription": { "text": "There are multiple ways in which this weakness can be introduced, including:the wrong variable or reference;an incorrect number of arguments;incorrect order of arguments;wrong type of arguments; orwrong value." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-629", "name": "Weaknesses in OWASP Top Ten (2007)", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-712" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-713" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-714" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-715" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-716" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-717" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-718" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-719" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-720" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-721" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-630", "name": "DEPRECATED: Weaknesses Examined by SAMATE", "fullDescription": { "text": "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." } }, { "id": "CWE-631", "name": "DEPRECATED: Resource-specific Weaknesses", "fullDescription": { "text": "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." } }, { "id": "CWE-632", "name": "DEPRECATED: Weaknesses that Affect Files or Directories", "fullDescription": { "text": "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." } }, { "id": "CWE-633", "name": "DEPRECATED: Weaknesses that Affect Memory", "fullDescription": { "text": "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." } }, { "id": "CWE-634", "name": "DEPRECATED: Weaknesses that Affect System Processes", "fullDescription": { "text": "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." } }, { "id": "CWE-635", "name": "Weaknesses Originally Used by NVD from 2008 to 2016", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-16" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-20" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-22" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-59" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-94" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-134" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-189" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-200" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-255" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-264" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-287" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-310" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-352" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-362" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-399" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-636", "name": "Not Failing Securely ('Failing Open')", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.\"" }, "relationships": [ { "target": { "id": "CWE-280", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-637", "name": "Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-638", "name": "Not Using Complete Mediation", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-862", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-639", "name": "Authorization Bypass Through User-Controlled Key", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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.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.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." }, "relationships": [ { "target": { "id": "CWE-284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-863", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-640", "name": "Weak Password Recovery Mechanism for Forgotten Password", "shortDescription": { "text": "The software contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-641", "name": "Improper Restriction of Names for Files and Other Resources", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-99", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-642", "name": "External Control of Critical State Data", "shortDescription": { "text": "The software stores security-critical state information about its users, or the software itself, in a location that is accessible to unauthorized actors." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-643", "name": "Improper Neutralization of Data within XPath Expressions ('XPath Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-91", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-943", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-644", "name": "Improper Neutralization of HTTP Headers for Scripting Syntax", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "An attacker may be able to conduct cross-site scripting and other attacks against users who have these components enabled.If an application 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." }, "relationships": [ { "target": { "id": "CWE-116", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-645", "name": "Overly Restrictive Account Lockout Mechanism", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-646", "name": "Reliance on File Name or Extension of Externally-Supplied File", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-647", "name": "Use of Non-Canonical URL Paths for Authorization Decisions", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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:http://WWW.EXAMPLE.COM/mypagehttp://www.example.com/%6Dypage (alternate encoding)http://192.168.1.1/mypage (IP address)http://www.example.com/mypage/ (trailing /)http://www.example.com:80/mypageTherefore 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)." }, "relationships": [ { "target": { "id": "CWE-863", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-648", "name": "Incorrect Use of Privileged APIs", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "When an application contains certain functions that perform operations requiring an elevated level of privilege, the caller of a privileged API must be careful to:ensure that assumptions made by the APIs are valid, such as validity of argumentsaccount for known weaknesses in the design/implementation of the APIcall the API from a safe contextIf 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.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." }, "relationships": [ { "target": { "id": "CWE-269", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-649", "name": "Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking", "shortDescription": { "text": "The software uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the software does not use integrity checks to detect if those inputs have been modified." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-650", "name": "Trusting HTTP Permission Methods on the Server Side", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-436", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-651", "name": "Exposure of WSDL File Containing Sensitive Information", "shortDescription": { "text": "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)." }, "fullDescription": { "text": "An information exposure may occur if any of the following apply:The WSDL file is accessible to a wider audience than intended.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.Information in the WSDL file helps guess names/locations of methods/resources that should not be publicly accessible." }, "relationships": [ { "target": { "id": "CWE-538", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-652", "name": "Improper Neutralization of Data within XQuery Expressions ('XQuery Injection')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-91", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-943", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-653", "name": "Insufficient Compartmentalization", "shortDescription": { "text": "The product does not sufficiently compartmentalize functionality or processes that require different privilege levels, rights, or permissions." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-654", "name": "Reliance on a Single Factor in a Security Decision", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-655", "name": "Insufficient Psychological Acceptability", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-656", "name": "Reliance on Security Through Obscurity", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-259", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-321", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-472", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-657", "name": "Violation of Secure Design Principles", "shortDescription": { "text": "The product violates well-established principles for secure design." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-658", "name": "Weaknesses in Software Written in C", "fullDescription": { "text": "This view (slice) covers issues that are found in C programs that are not common to all languages." } }, { "id": "CWE-659", "name": "Weaknesses in Software Written in C++", "fullDescription": { "text": "This view (slice) covers issues that are found in C++ programs that are not common to all languages." } }, { "id": "CWE-660", "name": "Weaknesses in Software Written in Java", "fullDescription": { "text": "This view (slice) covers issues that are found in Java programs that are not common to all languages." } }, { "id": "CWE-661", "name": "Weaknesses in Software Written in PHP", "fullDescription": { "text": "This view (slice) covers issues that are found in PHP programs that are not common to all languages." } }, { "id": "CWE-662", "name": "Improper Synchronization", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-663", "name": "Use of a Non-reentrant Function in a Concurrent Context", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-664", "name": "Improper Control of a Resource Through its Lifetime", "shortDescription": { "text": "The software does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release." }, "fullDescription": { "text": "Resources often have explicit instructions on how to be created, used and destroyed. When software does not follow these instructions, it can lead to unexpected behaviors and potentially exploitable states.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.\"" } }, { "id": "CWE-665", "name": "Improper Initialization", "shortDescription": { "text": "The software does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-666", "name": "Operation on Resource in Wrong Phase of Lifetime", "shortDescription": { "text": "The software performs an operation on a resource at the wrong phase of the resource's lifecycle, which can lead to unexpected behaviors." }, "fullDescription": { "text": "When a developer wants to initialize, use or release a resource, it is important to follow the specifications outlined for how to operate on that resource and to ensure that the resource is in the expected state. In this case, the software wants to perform a normally valid operation, initialization, use or release, on a resource when it is in the incorrect phase of its lifetime." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-667", "name": "Improper Locking", "shortDescription": { "text": "The software does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-668", "name": "Exposure of Resource to Wrong Sphere", "shortDescription": { "text": "The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource." }, "fullDescription": { "text": "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.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.In either case, the end result is that a resource has been exposed to the wrong party." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-669", "name": "Incorrect Resource Transfer Between Spheres", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-670", "name": "Always-Incorrect Control Flow Implementation", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-671", "name": "Lack of Administrator Control over Security", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-657", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-672", "name": "Operation on a Resource after Expiration or Release", "shortDescription": { "text": "The software uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked." }, "relationships": [ { "target": { "id": "CWE-666", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-673", "name": "External Influence of Sphere Definition", "shortDescription": { "text": "The product does not prevent the definition of control spheres from external actors." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-674", "name": "Uncontrolled Recursion", "shortDescription": { "text": "The product does not properly control the amount of recursion which takes place, consuming excessive resources, such as allocated memory or the program stack." }, "relationships": [ { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-675", "name": "Duplicate Operations on Resource", "shortDescription": { "text": "The product performs the same operation on a resource two or more times, when the operation should only be applied once." }, "relationships": [ { "target": { "id": "CWE-102", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-586", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] } ] }, { "id": "CWE-676", "name": "Use of Potentially Dangerous Function", "shortDescription": { "text": "The program invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely." }, "relationships": [ { "target": { "id": "CWE-1177", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-677", "name": "Weakness Base Elements", "fullDescription": { "text": "This view (slice) displays only weakness base elements." } }, { "id": "CWE-678", "name": "Composites", "fullDescription": { "text": "This view displays only composite weaknesses." } }, { "id": "CWE-679", "name": "DEPRECATED: Chain Elements", "fullDescription": { "text": "This view has been deprecated. It has limited utility for stakeholders, since all weaknesses can be links in a chain." } }, { "id": "CWE-680", "name": "Integer Overflow to Buffer Overflow", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-190", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] } ] }, { "id": "CWE-681", "name": "Incorrect Conversion between Numeric Types", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-682", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-704", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-682", "name": "Incorrect Calculation", "shortDescription": { "text": "The software performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management." }, "fullDescription": { "text": "When software 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." }, "relationships": [ { "target": { "id": "CWE-170", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-683", "name": "Function Call With Incorrect Order of Arguments", "shortDescription": { "text": "The software calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-628", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-684", "name": "Incorrect Provision of Specified Functionality", "shortDescription": { "text": "The code does not function according to its published specifications, potentially leading to incorrect usage." }, "fullDescription": { "text": "When providing functionality to an external party, it is important that the software 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." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-685", "name": "Function Call With Incorrect Number of Arguments", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-628", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-686", "name": "Function Call With Incorrect Argument Type", "shortDescription": { "text": "The software calls a function, procedure, or routine, but the caller specifies an argument that is the wrong data type, which may lead to resultant weaknesses." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-628", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-687", "name": "Function Call With Incorrectly Specified Argument Value", "shortDescription": { "text": "The software calls a function, procedure, or routine, but the caller specifies an argument that contains the wrong value, which may lead to resultant weaknesses." }, "relationships": [ { "target": { "id": "CWE-628", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-688", "name": "Function Call With Incorrect Variable or Reference as Argument", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-628", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-689", "name": "Permission Race Condition During Resource Copy", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-362", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-732", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] } ] }, { "id": "CWE-690", "name": "Unchecked Return Value to NULL Pointer Dereference", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-252", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] }, { "target": { "id": "CWE-476", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-691", "name": "Insufficient Control Flow Management", "shortDescription": { "text": "The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways." } }, { "id": "CWE-692", "name": "Incomplete Denylist to Cross-Site Scripting", "shortDescription": { "text": "The product uses a denylist-based protection mechanism to defend against XSS attacks, but the denylist is incomplete, allowing XSS variants to succeed." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-79", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-184", "toolComponent": { "name": "CWE" } }, "kinds": [ "willPrecede" ] } ] }, { "id": "CWE-693", "name": "Protection Mechanism Failure", "shortDescription": { "text": "The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product." }, "fullDescription": { "text": "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." } }, { "id": "CWE-694", "name": "Use of Multiple Resources with Duplicate Identifier", "shortDescription": { "text": "The software uses multiple resources that can have the same identifier, in a context in which unique identifiers are required." }, "fullDescription": { "text": "If the software assumes that each resource has a unique identifier, the software could operate on the wrong resource if attackers can cause multiple resources to be associated with the same identifier." }, "relationships": [ { "target": { "id": "CWE-99", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-695", "name": "Use of Low-Level Functionality", "shortDescription": { "text": "The software uses low-level functionality that is explicitly prohibited by the framework or specification under which the software is supposed to operate." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-573", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-696", "name": "Incorrect Behavior Order", "shortDescription": { "text": "The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses." }, "relationships": [ { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-697", "name": "Incorrect Comparison", "shortDescription": { "text": "The software compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses." }, "fullDescription": { "text": "This weakness class covers several possibilities:the comparison checks one factor incorrectly;the comparison should consider multiple factors, but it does not check some of those factors at all;the comparison checks the wrong factor." } }, { "id": "CWE-698", "name": "Execution After Redirect (EAR)", "shortDescription": { "text": "The web application sends a redirect to another location, but instead of exiting, it executes additional code." }, "relationships": [ { "target": { "id": "CWE-670", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-705", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-699", "name": "Software Development", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-19" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-133" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-136" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-137" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-189" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-199" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-255" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-265" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-275" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-310" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-320" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-355" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-371" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-387" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-389" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-399" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-411" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-417" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-429" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-438" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-452" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-465" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-557" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-569" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-840" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1006" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1210" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1211" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1212" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1213" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1214" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1215" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1216" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1217" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1218" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1219" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1225" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1226" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1227" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1228" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-700", "name": "Seven Pernicious Kingdoms", "fullDescription": { "text": "This view (graph) organizes weaknesses using a hierarchical structure that is similar to that used by Seven Pernicious Kingdoms." }, "relationships": [ { "target": { "id": "CWE-2" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-227" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-254" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-361" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-388" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-398" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-485" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-1005" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-701", "name": "Weaknesses Introduced During Design", "fullDescription": { "text": "This view (slice) lists weaknesses that can be introduced during design." } }, { "id": "CWE-702", "name": "Weaknesses Introduced During Implementation", "fullDescription": { "text": "This view (slice) lists weaknesses that can be introduced during implementation." } }, { "id": "CWE-703", "name": "Improper Check or Handling of Exceptional Conditions", "shortDescription": { "text": "The software does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the software." } }, { "id": "CWE-704", "name": "Incorrect Type Conversion or Cast", "shortDescription": { "text": "The software does not correctly convert an object, resource, or structure from one type to a different type." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-705", "name": "Incorrect Control Flow Scoping", "shortDescription": { "text": "The software does not properly return control flow to the proper location after it has completed a task or detected an unusual condition." }, "relationships": [ { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-706", "name": "Use of Incorrectly-Resolved Name or Reference", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-99", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-707", "name": "Improper Neutralization", "shortDescription": { "text": "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." }, "fullDescription": { "text": "If a message is malformed, it may cause the message to be incorrectly interpreted.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:checking that the input/output is already \"safe\" (e.g. validation)transformation of the input/output to be \"safe\" using techniques such as filtering, encoding/decoding, escaping/unescaping, quoting/unquoting, or canonicalizationpreventing the input/output from being directly provided by an attacker (e.g. \"indirect selection\" that maps externally-provided values to internally-controlled values)preventing the input/output from being processed at allThis 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." } }, { "id": "CWE-708", "name": "Incorrect Ownership Assignment", "shortDescription": { "text": "The software assigns an owner to a resource, but the owner is outside of the intended control sphere." }, "fullDescription": { "text": "This may allow the resource to be manipulated by actors outside of the intended control sphere." }, "relationships": [ { "target": { "id": "CWE-282", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-345", "toolComponent": { "name": "CWE" } }, "kinds": [ "equal" ] } ] }, { "id": "CWE-709", "name": "Named Chains", "fullDescription": { "text": "This view displays Named Chains and their components." } }, { "id": "CWE-710", "name": "Improper Adherence to Coding Standards", "shortDescription": { "text": "The software does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities." } }, { "id": "CWE-711", "name": "Weaknesses in OWASP Top Ten (2004)", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-722" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-723" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-724" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-725" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-726" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-727" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-728" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-729" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-730" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-731" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-712", "name": "OWASP Top Ten 2007 Category A1 - Cross Site Scripting (XSS)", "fullDescription": { "text": "Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-713", "name": "OWASP Top Ten 2007 Category A2 - Injection Flaws", "fullDescription": { "text": "Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-77" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-90" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-91" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-93" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-714", "name": "OWASP Top Ten 2007 Category A3 - Malicious File Execution", "fullDescription": { "text": "Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-95" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-98" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-434" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-715", "name": "OWASP Top Ten 2007 Category A4 - Insecure Direct Object Reference", "fullDescription": { "text": "Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-22" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-472" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-639" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-716", "name": "OWASP Top Ten 2007 Category A5 - Cross Site Request Forgery (CSRF)", "fullDescription": { "text": "Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-352" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-717", "name": "OWASP Top Ten 2007 Category A6 - Information Leakage and Improper Error Handling", "fullDescription": { "text": "Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-200" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-203" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-215" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-718", "name": "OWASP Top Ten 2007 Category A7 - Broken Authentication and Session Management", "fullDescription": { "text": "Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-287" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-301" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-522" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-719", "name": "OWASP Top Ten 2007 Category A8 - Insecure Cryptographic Storage", "fullDescription": { "text": "Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-311" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-321" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-325" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-326" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-720", "name": "OWASP Top Ten 2007 Category A9 - Insecure Communications", "fullDescription": { "text": "Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-311" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-321" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-325" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-326" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-721", "name": "OWASP Top Ten 2007 Category A10 - Failure to Restrict URL Access", "fullDescription": { "text": "Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2007." }, "relationships": [ { "target": { "id": "CWE-629" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-285" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-288" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-425" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-722", "name": "OWASP Top Ten 2004 Category A1 - Unvalidated Input", "fullDescription": { "text": "Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-20" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-77" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-102" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-103" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-104" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-106" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-109" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-120" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-166" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-167" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-179" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-180" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-181" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-182" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-183" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-425" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-472" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-601" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-602" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-723", "name": "OWASP Top Ten 2004 Category A2 - Broken Access Control", "fullDescription": { "text": "Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-9" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-22" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-41" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-73" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-266" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-268" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-275" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-283" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-284" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-285" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-330" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-425" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-525" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-551" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-556" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-639" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-708" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-724", "name": "OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management", "fullDescription": { "text": "Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-255" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-259" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-287" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-296" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-298" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-302" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-304" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-307" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-309" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-345" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-384" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-521" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-522" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-525" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-613" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-620" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-640" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-798" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-725", "name": "OWASP Top Ten 2004 Category A4 - Cross-Site Scripting (XSS) Flaws", "fullDescription": { "text": "Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-644" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-726", "name": "OWASP Top Ten 2004 Category A5 - Buffer Overflows", "fullDescription": { "text": "Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-120" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-134" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-727", "name": "OWASP Top Ten 2004 Category A6 - Injection Flaws", "fullDescription": { "text": "Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-74" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-77" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-91" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-95" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-98" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-117" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-728", "name": "OWASP Top Ten 2004 Category A7 - Improper Error Handling", "fullDescription": { "text": "Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-7" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-203" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-228" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-252" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-389" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-390" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-391" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-394" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-636" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-729", "name": "OWASP Top Ten 2004 Category A8 - Insecure Storage", "fullDescription": { "text": "Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-14" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-226" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-261" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-311" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-321" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-326" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-327" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-539" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-591" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-598" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-730", "name": "OWASP Top Ten 2004 Category A9 - Denial of Service", "fullDescription": { "text": "Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-170" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-248" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-369" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-382" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-400" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-401" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-404" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-405" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-410" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-412" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-476" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-674" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-731", "name": "OWASP Top Ten 2004 Category A10 - Insecure Configuration Management", "fullDescription": { "text": "Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2004." }, "relationships": [ { "target": { "id": "CWE-711" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-5" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-6" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-7" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-8" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-9" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-11" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-12" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-13" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-215" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-219" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-275" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-295" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-459" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-489" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-520" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-526" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-527" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-528" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-529" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-530" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-531" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-532" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-540" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-541" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-548" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-552" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-554" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-555" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-556" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-732", "name": "Incorrect Permission Assignment for Critical Resource", "shortDescription": { "text": "The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors." }, "fullDescription": { "text": "When a resource is given a permissions 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." }, "relationships": [ { "target": { "id": "CWE-285", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-733", "name": "Compiler Optimization Removal or Modification of Security-critical Code", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-1038", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-734", "name": "Weaknesses Addressed by the CERT C Secure Coding Standard (2008)", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-735" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-736" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-737" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-738" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-739" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-740" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-741" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-742" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-743" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-744" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-745" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-746" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-747" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-748" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-735", "name": "CERT C Secure Coding Standard (2008) Chapter 2 - Preprocessor (PRE)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the Preprocessor (PRE) chapter of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-684" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-736", "name": "CERT C Secure Coding Standard (2008) Chapter 3 - Declarations and Initialization (DCL)", "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-547" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-628" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-686" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-737", "name": "CERT C Secure Coding Standard (2008) Chapter 4 - Expressions (EXP)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) chapter of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-467" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-468" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-476" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-628" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-704" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-783" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-738", "name": "CERT C Secure Coding Standard (2008) Chapter 5 - Integers (INT)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the Integers (INT) chapter of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-20" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-129" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-190" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-192" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-197" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-369" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-466" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-587" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-606" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-676" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-681" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-682" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-739", "name": "CERT C Secure Coding Standard (2008) Chapter 6 - Floating Point (FLP)", "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-369" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-681" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-682" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-686" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-740", "name": "CERT C Secure Coding Standard (2008) Chapter 7 - Arrays (ARR)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the Arrays (ARR) chapter of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-129" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-467" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-469" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-665" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-805" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-741", "name": "CERT C Secure Coding Standard (2008) Chapter 8 - Characters and Strings (STR)", "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-88" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-120" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-135" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-170" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-193" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-464" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-686" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-704" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-742", "name": "CERT C Secure Coding Standard (2008) Chapter 9 - Memory Management (MEM)", "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-20" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-128" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-131" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-190" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-226" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-244" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-252" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-415" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-416" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-476" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-528" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-590" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-591" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-628" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-665" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-687" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-754" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-743", "name": "CERT C Secure Coding Standard (2008) Chapter 10 - Input Output (FIO)", "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-22" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-37" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-38" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-39" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-41" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-59" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-62" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-64" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-65" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-67" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-134" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-241" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-276" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-279" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-362" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-367" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-379" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-391" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-403" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-404" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-552" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-675" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-676" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-686" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-732" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-744", "name": "CERT C Secure Coding Standard (2008) Chapter 11 - Environment (ENV)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the Environment (ENV) chapter of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-88" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-426" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-462" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-705" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-745", "name": "CERT C Secure Coding Standard (2008) Chapter 12 - Signals (SIG)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the Signals (SIG) chapter of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-479" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-662" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-746", "name": "CERT C Secure Coding Standard (2008) Chapter 13 - Error Handling (ERR)", "fullDescription": { "text": "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)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-20" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-391" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-544" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-676" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-705" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-747", "name": "CERT C Secure Coding Standard (2008) Chapter 14 - Miscellaneous (MSC)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) chapter of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-14" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-20" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-176" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-330" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-480" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-482" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-561" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-563" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-570" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-571" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-697" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-704" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-748", "name": "CERT C Secure Coding Standard (2008) Appendix - POSIX (POS)", "fullDescription": { "text": "Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) appendix of the CERT C Secure Coding Standard (2008)." }, "relationships": [ { "target": { "id": "CWE-734" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-59" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-170" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-242" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-272" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-273" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-363" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-366" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-562" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-667" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-686" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-696" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-749", "name": "Exposed Dangerous Method or Function", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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.The exposure can occur in a few different ways:1) The function/method was never intended to be exposed to outside actors.2) 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." }, "relationships": [ { "target": { "id": "CWE-664", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-750", "name": "Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-751" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-752" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-753" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-751", "name": "2009 Top 25 - Insecure Interaction Between Components", "fullDescription": { "text": "Weaknesses in this category are listed in the \"Insecure Interaction Between Components\" section of the 2009 CWE/SANS Top 25 Programming Errors." }, "relationships": [ { "target": { "id": "CWE-750" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-20" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-116" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-319" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-352" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-362" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-752", "name": "2009 Top 25 - Risky Resource Management", "fullDescription": { "text": "Weaknesses in this category are listed in the \"Risky Resource Management\" section of the 2009 CWE/SANS Top 25 Programming Errors." }, "relationships": [ { "target": { "id": "CWE-750" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-73" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-94" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-119" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-404" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-426" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-494" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-642" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-665" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-682" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-753", "name": "2009 Top 25 - Porous Defenses", "fullDescription": { "text": "Weaknesses in this category are listed in the \"Porous Defenses\" section of the 2009 CWE/SANS Top 25 Programming Errors." }, "relationships": [ { "target": { "id": "CWE-750" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-250" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-259" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-285" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-327" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-330" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-602" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-732" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-798" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-754", "name": "Improper Check for Unusual or Exceptional Conditions", "shortDescription": { "text": "The software 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 software." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-755", "name": "Improper Handling of Exceptional Conditions", "shortDescription": { "text": "The software does not handle or incorrectly handles an exceptional condition." }, "relationships": [ { "target": { "id": "CWE-703", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-756", "name": "Missing Custom Error Page", "shortDescription": { "text": "The software does not return custom error pages to the user, possibly exposing sensitive information." }, "relationships": [ { "target": { "id": "CWE-209", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-755", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-757", "name": "Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')", "shortDescription": { "text": "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." }, "fullDescription": { "text": "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 software 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." }, "relationships": [ { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-758", "name": "Reliance on Undefined, Unspecified, or Implementation-Defined Behavior", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This can lead to resultant weaknesses when the required properties change, such as when the software is ported to a different platform or if an interaction error (CWE-435) occurs." }, "relationships": [ { "target": { "id": "CWE-710", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-759", "name": "Use of a One-Way Hash without a Salt", "shortDescription": { "text": "The software uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the software does not also use a salt as part of the input." }, "fullDescription": { "text": "This makes it easier for attackers to pre-compute the hash value using dictionary attack techniques such as rainbow tables.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." }, "relationships": [ { "target": { "id": "CWE-916", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-760", "name": "Use of a One-Way Hash with a Predictable Salt", "shortDescription": { "text": "The software uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the software uses a predictable salt as part of the input." }, "fullDescription": { "text": "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.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." }, "relationships": [ { "target": { "id": "CWE-916", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-761", "name": "Free of Pointer not at Start of Buffer", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "This can cause the application to crash, or in some cases, modify critical program variables or execute code.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." }, "relationships": [ { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-763", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-762", "name": "Mismatched Memory Management Routines", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "This weakness can be generally described as mismatching memory management routines, such as: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.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.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." }, "relationships": [ { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-763", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-763", "name": "Release of Invalid Pointer or Reference", "shortDescription": { "text": "The application attempts to return a memory resource to the system, but calls the wrong release function or calls the appropriate release function incorrectly." }, "fullDescription": { "text": "This weakness can take several forms, such as:The memory was allocated, explicitly or implicitly, via one memory management method and deallocated using a different, non-compatible function (CWE-762).The function calls or memory management routines chosen are appropriate, however they are used incorrectly, such as in CWE-761." }, "relationships": [ { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-764", "name": "Multiple Locks of a Critical Resource", "shortDescription": { "text": "The software locks a critical resource more times than intended, leading to an unexpected state in the system." }, "fullDescription": { "text": "When software 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." }, "relationships": [ { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-667", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-675", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-765", "name": "Multiple Unlocks of a Critical Resource", "shortDescription": { "text": "The software unlocks a critical resource more times than intended, leading to an unexpected state in the system." }, "fullDescription": { "text": "When software 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." }, "relationships": [ { "target": { "id": "CWE-667", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-675", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-766", "name": "Critical Data Element Declared Public", "shortDescription": { "text": "The software declares a critical variable, field, or member to be public when intended security policy requires it to be private." }, "fullDescription": { "text": "This issue makes it more difficult to 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." }, "relationships": [ { "target": { "id": "CWE-1061", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-767", "name": "Access to Critical Private Variable via Public Method", "shortDescription": { "text": "The software defines a public method that reads or modifies a private variable." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-668", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-768", "name": "Incorrect Short Circuit Evaluation", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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 software's execution. If an attacker can discover such an inconsistency, it may be exploitable to gain arbitrary control over a system.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.Finally, the usage of short circuit evaluation may decrease the maintainability of the code." }, "relationships": [ { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-769", "name": "DEPRECATED: Uncontrolled File Descriptor Consumption", "shortDescription": { "text": "This entry has been deprecated because it was a duplicate of CWE-774. All content has been transferred to CWE-774." } }, { "id": "CWE-770", "name": "Allocation of Resources Without Limits or Throttling", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-400", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-665", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-771", "name": "Missing Reference to Active Allocated Resource", "shortDescription": { "text": "The software does not properly maintain a reference to a resource that has been allocated, which prevents the resource from being reclaimed." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-400", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-772", "name": "Missing Release of Resource after Effective Lifetime", "shortDescription": { "text": "The software does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-773", "name": "Missing Reference to Active File Descriptor or Handle", "shortDescription": { "text": "The software does not properly maintain references to a file descriptor or handle, which prevents that file descriptor/handle from being reclaimed." }, "fullDescription": { "text": "This can cause the software to consume all available file descriptors or handles, which can prevent other processes from performing critical file processing operations." }, "relationships": [ { "target": { "id": "CWE-771", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-774", "name": "Allocation of File Descriptors or Handles Without Limits or Throttling", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This can cause the software to consume all available file descriptors or handles, which can prevent other processes from performing critical file processing operations." }, "relationships": [ { "target": { "id": "CWE-770", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-775", "name": "Missing Release of File Descriptor or Handle after Effective Lifetime", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-404", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-772", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-776", "name": "Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-409", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-674", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-777", "name": "Regular Expression without Anchors", "shortDescription": { "text": "The software uses a regular expression to perform neutralization, but the regular expression is not anchored and may allow malicious or malformed data to slip through." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-625", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-778", "name": "Insufficient Logging", "shortDescription": { "text": "When a security-critical event occurs, the software either does not record the event or omits important details about the event when logging it." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-223", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-779", "name": "Logging of Excessive Data", "shortDescription": { "text": "The software logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-400", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-780", "name": "Use of RSA Algorithm without OAEP", "shortDescription": { "text": "The software uses the RSA algorithm but does not incorporate Optimal Asymmetric Encryption Padding (OAEP), which might weaken the encryption." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-327", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-781", "name": "Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code", "shortDescription": { "text": "The software defines an IOCTL that uses METHOD_NEITHER for I/O, but it does not validate or incorrectly validates the addresses that are provided." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-822", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-1285", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-782", "name": "Exposed IOCTL with Insufficient Access Control", "shortDescription": { "text": "The software implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL." }, "fullDescription": { "text": "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.The implementations of IOCTLs will differ between operating system types and versions, so the methods of attack and prevention may vary widely." }, "relationships": [ { "target": { "id": "CWE-749", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-781", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-783", "name": "Operator Precedence Logic Error", "shortDescription": { "text": "The program uses an expression in which operator precedence causes incorrect logic to be used." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-670", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-784", "name": "Reliance on Cookies without Validation and Integrity Checking in a Security Decision", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-565", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-807", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-785", "name": "Use of Path Manipulation Function without Maximum-sized Buffer", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-20", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-120", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-676", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-786", "name": "Access of Memory Location Before Start of Buffer", "shortDescription": { "text": "The software reads or writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-787", "name": "Out-of-bounds Write", "shortDescription": { "text": "The software writes data past the end, or before the beginning, of the intended buffer." }, "fullDescription": { "text": "Typically, this can result in corruption of data, a crash, or code execution. The software 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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-788", "name": "Access of Memory Location After End of Buffer", "shortDescription": { "text": "The software reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer." }, "fullDescription": { "text": "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 buffer; or when a negative index is used, which generates a position before the buffer." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-789", "name": "Memory Allocation with Excessive Size Value", "shortDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-476", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-770", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-1284", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-790", "name": "Improper Filtering of Special Elements", "shortDescription": { "text": "The software receives data from an upstream component, but does not filter or incorrectly filters special elements before sending it to a downstream component." }, "relationships": [ { "target": { "id": "CWE-138", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-791", "name": "Incomplete Filtering of Special Elements", "shortDescription": { "text": "The software receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component." }, "relationships": [ { "target": { "id": "CWE-790", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-792", "name": "Incomplete Filtering of One or More Instances of Special Elements", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Incomplete filtering of this nature involves either:only filtering a single instance of a special element when more exist, ornot filtering all instances or all elements where multiple special elements exist." }, "relationships": [ { "target": { "id": "CWE-791", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-793", "name": "Only Filtering One Instance of a Special Element", "shortDescription": { "text": "The software receives data from an upstream component, but only filters a single instance of a special element before sending it to a downstream component." }, "fullDescription": { "text": "Incomplete filtering of this nature may be location-dependent, as in only the first or last element is filtered." }, "relationships": [ { "target": { "id": "CWE-792", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-794", "name": "Incomplete Filtering of Multiple Instances of Special Elements", "shortDescription": { "text": "The software receives data from an upstream component, but does not filter all instances of a special element before sending it to a downstream component." }, "fullDescription": { "text": "Incomplete filtering of this nature may be applied to:sequential elements (special elements that appear next to each other) ornon-sequential elements (special elements that appear multiple times in different locations)." }, "relationships": [ { "target": { "id": "CWE-792", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-795", "name": "Only Filtering Special Elements at a Specified Location", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "A filter might only account for instances of special elements when they occur:relative to a marker (e.g. \"at the beginning/end of string; the second argument\"), orat an absolute position (e.g. \"byte number 10\").This may leave special elements in the data that did not match the filter position, but still may be dangerous." }, "relationships": [ { "target": { "id": "CWE-791", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-796", "name": "Only Filtering Special Elements Relative to a Marker", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-795", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-797", "name": "Only Filtering Special Elements at an Absolute Position", "shortDescription": { "text": "The software 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." }, "relationships": [ { "target": { "id": "CWE-795", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-798", "name": "Use of Hard-coded Credentials", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "Hard-coded credentials typically create a significant hole that allows an attacker to bypass the authentication that has been configured by the software 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:Inbound: the software contains an authentication mechanism that checks the input credentials against a hard-coded set of credentials.Outbound: the software connects to another system or component, and it contains hard-coded credentials for connecting to that component.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 software. 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 software will have the same password, even across different organizations, this enables massive attacks such as worms to take place.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 software. 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." }, "relationships": [ { "target": { "id": "CWE-257", "toolComponent": { "name": "CWE" } }, "kinds": [ "relevant" ] }, { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-344", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-671", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-799", "name": "Improper Control of Interaction Frequency", "shortDescription": { "text": "The software does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests." }, "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-691", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-800", "name": "Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-801" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-802" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-803" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-808" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-801", "name": "2010 Top 25 - Insecure Interaction Between Components", "fullDescription": { "text": "Weaknesses in this category are listed in the \"Insecure Interaction Between Components\" section of the 2010 CWE/SANS Top 25 Programming Errors." }, "relationships": [ { "target": { "id": "CWE-800" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-352" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-362" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-434" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-601" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-802", "name": "2010 Top 25 - Risky Resource Management", "fullDescription": { "text": "Weaknesses in this category are listed in the \"Risky Resource Management\" section of the 2010 CWE/SANS Top 25 Programming Errors." }, "relationships": [ { "target": { "id": "CWE-800" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-22" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-98" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-120" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-129" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-131" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-190" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-494" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-754" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-770" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-805" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-803", "name": "2010 Top 25 - Porous Defenses", "fullDescription": { "text": "Weaknesses in this category are listed in the \"Porous Defenses\" section of the 2010 CWE/SANS Top 25 Programming Errors." }, "relationships": [ { "target": { "id": "CWE-800" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-285" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-306" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-311" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-327" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-732" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-798" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-807" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-804", "name": "Guessable CAPTCHA", "shortDescription": { "text": "The software uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor." }, "fullDescription": { "text": "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.There can be several different causes of a guessable CAPTCHA:An audio or visual image that does not have sufficient distortion from the unobfuscated source image.A question is generated that with a format that can be automatically recognized, such as a math question.A question for which the number of possible answers is limited, such as birth years or favorite sports teams.A general-knowledge or trivia question for which the answer can be accessed using a data base, such as country capitals or popular actors.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." }, "relationships": [ { "target": { "id": "CWE-287", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-330", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-863", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-805", "name": "Buffer Access with Incorrect Length Value", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "When the length value exceeds the size of the destination, a buffer overflow could occur." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-806", "name": "Buffer Access Using Size of Source Buffer", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "When the size of the destination is smaller than the size of the source, a buffer overflow could occur." }, "relationships": [ { "target": { "id": "CWE-805", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-807", "name": "Reliance on Untrusted Inputs in a Security Decision", "shortDescription": { "text": "The application 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." }, "fullDescription": { "text": "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.Without sufficient encryption, integrity checking, or other mechanism, any input that originates from an outsider cannot be trusted." }, "relationships": [ { "target": { "id": "CWE-693", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-808", "name": "2010 Top 25 - Weaknesses On the Cusp", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-800" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-59" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-134" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-212" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-307" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-330" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-416" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-426" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-454" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-456" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-476" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-672" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-681" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-749" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-772" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-799" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-804" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-809", "name": "Weaknesses in OWASP Top Ten (2010)", "fullDescription": { "text": "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." }, "relationships": [ { "target": { "id": "CWE-810" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-811" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-812" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-813" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-814" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-815" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-816" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-817" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-818" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-819" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-810", "name": "OWASP Top Ten 2010 Category A1 - Injection", "fullDescription": { "text": "Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-78" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-88" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-89" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-90" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-91" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-811", "name": "OWASP Top Ten 2010 Category A2 - Cross-Site Scripting (XSS)", "fullDescription": { "text": "Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-79" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-812", "name": "OWASP Top Ten 2010 Category A3 - Broken Authentication and Session Management", "fullDescription": { "text": "Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-287" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-306" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-307" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-798" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-813", "name": "OWASP Top Ten 2010 Category A4 - Insecure Direct Object References", "fullDescription": { "text": "Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-22" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-99" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-434" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-639" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-829" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-862" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-863" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-814", "name": "OWASP Top Ten 2010 Category A5 - Cross-Site Request Forgery(CSRF)", "fullDescription": { "text": "Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-352" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-815", "name": "OWASP Top Ten 2010 Category A6 - Security Misconfiguration", "fullDescription": { "text": "Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-209" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-219" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-250" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-538" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-552" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-732" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-816", "name": "OWASP Top Ten 2010 Category A7 - Insecure Cryptographic Storage", "fullDescription": { "text": "Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-311" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-312" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-326" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-327" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-759" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-817", "name": "OWASP Top Ten 2010 Category A8 - Failure to Restrict URL Access", "fullDescription": { "text": "Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-285" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-862" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-863" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-818", "name": "OWASP Top Ten 2010 Category A9 - Insufficient Transport Layer Protection", "fullDescription": { "text": "Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-311" }, "kinds": [ "subset" ] }, { "target": { "id": "CWE-319" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-819", "name": "OWASP Top Ten 2010 Category A10 - Unvalidated Redirects and Forwards", "fullDescription": { "text": "Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2010." }, "relationships": [ { "target": { "id": "CWE-809" }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-601" }, "kinds": [ "subset" ] } ] }, { "id": "CWE-820", "name": "Missing Synchronization", "shortDescription": { "text": "The software utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource." }, "fullDescription": { "text": "If access to a shared resource is not synchronized, then the resource may not be in a state that is expected by the software. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource." }, "relationships": [ { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-821", "name": "Incorrect Synchronization", "shortDescription": { "text": "The software utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource." }, "fullDescription": { "text": "If access to a shared resource is not correctly synchronized, then the resource may not be in a state that is expected by the software. This might lead to unexpected or insecure behaviors, especially if an attacker can influence the shared resource." }, "relationships": [ { "target": { "id": "CWE-662", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-822", "name": "Untrusted Pointer Dereference", "shortDescription": { "text": "The program obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer." }, "fullDescription": { "text": "An attacker can supply a pointer for memory locations that the program is not expecting. If the pointer is dereferenced for a write operation, the attack might allow modification of critical program 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 program variable to an unexpected value (since the value will be read from an unexpected memory location).There are several variants of this weakness, including but not necessarily limited to:The untrusted value is directly invoked as a function call.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).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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-125", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-823", "name": "Use of Out-of-range Pointer Offset", "shortDescription": { "text": "The program 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." }, "fullDescription": { "text": "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.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.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 program. As a result, the attack might change the state of the software as accessed through program variables, cause a crash or instable behavior, and possibly lead to code execution." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-125", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-824", "name": "Access of Uninitialized Pointer", "shortDescription": { "text": "The program accesses or uses a pointer that has not been initialized." }, "fullDescription": { "text": "If the pointer contains an uninitialized value, then the value might not point to a valid memory location. This could cause the program 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.Depending on memory layout, associated memory management behaviors, and program 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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-125", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-825", "name": "Expired Pointer Dereference", "shortDescription": { "text": "The program dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid." }, "fullDescription": { "text": "When a program 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 program 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." }, "relationships": [ { "target": { "id": "CWE-119", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-125", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-787", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-826", "name": "Premature Release of Resource During Expected Lifetime", "shortDescription": { "text": "The program releases a resource that is still intended to be used by the program itself or another actor." }, "fullDescription": { "text": "This weakness focuses on errors in which the program should not release a resource, but performs the release anyway. This is different than a weakness in which the program 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.When a program 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." }, "relationships": [ { "target": { "id": "CWE-666", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-672", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] } ] }, { "id": "CWE-827", "name": "Improper Control of Document Type Definition", "shortDescription": { "text": "The software 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 software to expose files, consume excessive system resources, or execute arbitrary http requests on behalf of the attacker." }, "fullDescription": { "text": "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.For example, the SOAP specification prohibits SOAP messages from containing DTDs." }, "relationships": [ { "target": { "id": "CWE-706", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] }, { "target": { "id": "CWE-776", "toolComponent": { "name": "CWE" } }, "kinds": [ "canFollow" ] }, { "target": { "id": "CWE-829", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-828", "name": "Signal Handler with Functionality that is not Asynchronous-Safe", "shortDescription": { "text": "The software 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." }, "fullDescription": { "text": "This can lead to an unexpected system state with a variety of potential consequences depending on context, including denial of service and code execution.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.There are several different scenarios that introduce this issue: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.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.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).Note that in some environments or contexts, it might be possible for the signal handler to be interrupted itself.If both a signal handler and the normal behavior of the software 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." }, "relationships": [ { "target": { "id": "CWE-364", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-829", "name": "Inclusion of Functionality from Untrusted Control Sphere", "shortDescription": { "text": "The software imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere." }, "fullDescription": { "text": "When including third-party functionality, such as a web widget, library, or other source of functionality, the software 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.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)." }, "relationships": [ { "target": { "id": "CWE-669", "toolComponent": { "name": "CWE" } }, "kinds": [ "superset" ] } ] }, { "id": "CWE-830", "name": "Inclusion of Web Functionality from an Untrusted Source", "shortDescription": { "text": "The software includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the software, potentially granting total access and control of the software to the untrusted source." }, "fullDescription": { "text": "Including third party functionality in a web-based environment is risky, especially if the source of the functionality is untrusted.Even if the third party is a trusted source, the software 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 software.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 '