CWE

Common Weakness Enumeration

A Community-Developed List of Software Weakness Types

CWE/SANS Top 25 Most Dangerous Software Errors
Home > CWE List > CWE- Individual Dictionary Definition (3.0)  
ID

CWE VIEW: Weaknesses for Simplified Mapping of Published Vulnerabilities

View ID: 1003
Type: Graph
Status: Incomplete
+ Objective
CWE entries in this view (graph) may be used to categorize potential weaknesses within sources that handle public, third-party vulnerability information, such as NVD. By design, this view is incomplete; it is limited to a small number of the most commonly-seen weaknesses, so that it is easier to use for humans. This view is most similar to CWE-699 (Development Concepts), although it also has some relationships that are similar to those for CWE-1000 (Research Concepts). Note: this view is likely to change significantly in the next version.
+ Relationships
Show Details:
1003 - Weaknesses for Simplified Mapping of Published Vulnerabilities
*CategoryCategoryConfiguration - (16)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 16 (Configuration)
Weaknesses in this category are typically introduced during the configuration of the software.
+CategoryCategoryCode - (17)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code)
Weaknesses in this category are typically introduced during code development, including specification, design, and implementation.
+CategoryCategorySource Code - (18)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code)
Weaknesses in this category are typically found within source code.
+CategoryCategoryData Processing Errors - (19)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors)
Weaknesses in this category are typically found in functionality that processes data.
+ClassClassIncorrect Access of Indexable Resource ('Range Error') - (118)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 118 (Incorrect Access of Indexable Resource ('Range Error'))
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.
+ClassClassImproper Restriction of Operations within the Bounds of a Memory Buffer - (119)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)
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.Memory Corruption
*BaseBaseWrite-what-where Condition - (123)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 123 (Write-what-where Condition)
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.
*BaseBaseOut-of-bounds Read - (125)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 125 (Out-of-bounds Read)
The software reads data past the end, or before the beginning, of the intended buffer.
*BaseBaseOut-of-bounds Write - (787)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 787 (Out-of-bounds Write)
The software writes data past the end, or before the beginning, of the intended buffer.
*BaseBaseAccess of Uninitialized Pointer - (824)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 824 (Access of Uninitialized Pointer)
The program accesses or uses a pointer that has not been initialized.
+CategoryCategoryRepresentation Errors - (137)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 137 (Representation Errors)
Weaknesses in this category are introduced when inserting or converting data from one representation into another.
+CategoryCategoryCleansing, Canonicalization, and Comparison Errors - (171)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 137 (Representation Errors) > 171 (Cleansing, Canonicalization, and Comparison Errors)
Weaknesses in this category are related to improper handling of data within protection mechanisms that attempt to perform neutralization for untrusted data.
+ClassClassImproper Enforcement of Message or Data Structure - (707)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 137 (Representation Errors) > 171 (Cleansing, Canonicalization, and Comparison Errors) > 707 (Improper Enforcement of Message or Data Structure)
The software does not enforce or incorrectly enforces that structured messages or data are well-formed before being read from an upstream component or sent to a downstream component.
*ClassClassImproper Encoding or Escaping of Output - (116)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 137 (Representation Errors) > 171 (Cleansing, Canonicalization, and Comparison Errors) > 707 (Improper Enforcement of Message or Data Structure) > 116 (Improper Encoding or Escaping of Output)
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.Output SanitizationOutput ValidationOutput Encoding
*ClassClassEncoding Error - (172)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 137 (Representation Errors) > 171 (Cleansing, Canonicalization, and Comparison Errors) > 707 (Improper Enforcement of Message or Data Structure) > 172 (Encoding Error)
The software does not properly encode or decode the data, resulting in unexpected values.
*ClassClassIncorrect Regular Expression - (185)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 19 (Data Processing Errors) > 185 (Incorrect Regular Expression)
The software specifies a regular expression in a way that causes data to be improperly matched or compared.
+CategoryCategoryPathname Traversal and Equivalence Errors - (21)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 21 (Pathname Traversal and Equivalence Errors)
Weaknesses in this category can be used to access files outside of a restricted directory (path traversal) or to perform operations on files that would otherwise be restricted (path equivalence). Files, directories, and folders are so central to information technology that many different weaknesses and variants have been discovered. The manipulations generally involve special characters or sequences in pathnames, or the use of alternate references or channels.
*ClassClassImproper Limitation of a Pathname to a Restricted Directory ('Path Traversal') - (22)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 21 (Pathname Traversal and Equivalence Errors) > 22 (Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'))
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.Directory traversalPath traversal
*BaseBaseImproper Link Resolution Before File Access ('Link Following') - (59)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 21 (Pathname Traversal and Equivalence Errors) > 59 (Improper Link Resolution Before File Access ('Link Following'))
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.insecure temporary file
+CategoryCategory7PK - Security Features - (254)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features)
Software security is not security software. Here we're concerned with topics like authentication, access control, confidentiality, cryptography, and privilege management.
+CategoryCategoryCredentials Management - (255)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 255 (Credentials Management)
Weaknesses in this category are related to the management of credentials.
*BaseBaseWeak Password Recovery Mechanism for Forgotten Password - (640)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 255 (Credentials Management) > 640 (Weak Password Recovery Mechanism for Forgotten Password)
The software contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
*BaseBaseUse of Hard-coded Credentials - (798)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 255 (Credentials Management) > 798 (Use of Hard-coded Credentials)
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.
+CategoryCategoryPermissions, Privileges, and Access Controls - (264)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 264 (Permissions, Privileges, and Access Controls)
Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
+ClassClassImproper Access Control - (284)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 264 (Permissions, Privileges, and Access Controls) > 284 (Improper Access Control)
The software does not restrict or incorrectly restricts access to a resource from an unauthorized actor.Authorization
*ClassClassImproper Authorization - (285)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 264 (Permissions, Privileges, and Access Controls) > 284 (Improper Access Control) > 285 (Improper Authorization)
The software does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.AuthZ
+ClassClassImproper Authentication - (287)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 264 (Permissions, Privileges, and Access Controls) > 284 (Improper Access Control) > 287 (Improper Authentication)
When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.authentificationAuthC
*VariantVariantMissing Authentication for Critical Function - (306)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 264 (Permissions, Privileges, and Access Controls) > 284 (Improper Access Control) > 287 (Improper Authentication) > 306 (Missing Authentication for Critical Function)
The software does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
*CompositeCompositeSession Fixation - (384)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 264 (Permissions, Privileges, and Access Controls) > 284 (Improper Access Control) > 287 (Improper Authentication) > 384 (Session Fixation)
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.
+BaseBaseImproper Certificate Validation - (295)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 295 (Improper Certificate Validation)
The software does not validate, or incorrectly validates, a certificate.
*VariantVariantImproper Validation of Certificate with Host Mismatch - (297)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 295 (Improper Certificate Validation) > 297 (Improper Validation of Certificate with Host Mismatch)
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.
+CategoryCategoryCryptographic Issues - (310)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 310 (Cryptographic Issues)
Weaknesses in this category are related to the use of cryptography.
*CategoryCategoryKey Management Errors - (320)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 310 (Cryptographic Issues) > 320 (Key Management Errors)
Weaknesses in this category are related to errors in the management of cryptographic keys.
*ClassClassInadequate Encryption Strength - (326)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 310 (Cryptographic Issues) > 326 (Inadequate Encryption Strength)
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.
*BaseBaseUse of a Broken or Risky Cryptographic Algorithm - (327)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 310 (Cryptographic Issues) > 327 (Use of a Broken or Risky Cryptographic Algorithm)
The use of a broken or risky cryptographic algorithm is an unnecessary risk that may result in the exposure of sensitive information.
+ClassClassUse of Insufficiently Random Values - (330)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 330 (Use of Insufficiently Random Values)
The software may use insufficiently random numbers or values in a security context that depends on unpredictable numbers.
+BaseBaseInsufficient Entropy - (331)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 330 (Use of Insufficiently Random Values) > 331 (Insufficient Entropy)
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.
*VariantVariantInsufficient Entropy in PRNG - (332)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 330 (Use of Insufficiently Random Values) > 331 (Insufficient Entropy) > 332 (Insufficient Entropy in PRNG)
The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat.
*BaseBaseUse of Cryptographically Weak Pseudo-Random Number Generator (PRNG) - (338)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 330 (Use of Insufficiently Random Values) > 338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
+ClassClassInsufficient Verification of Data Authenticity - (345)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 345 (Insufficient Verification of Data Authenticity)
The software does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
*BaseBaseImproper Verification of Cryptographic Signature - (347)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 345 (Insufficient Verification of Data Authenticity) > 347 (Improper Verification of Cryptographic Signature)
The software does not verify, or incorrectly verifies, the cryptographic signature for data.
*CompositeCompositeCross-Site Request Forgery (CSRF) - (352)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 345 (Insufficient Verification of Data Authenticity) > 352 (Cross-Site Request Forgery (CSRF))
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.Session RidingCross Site Reference ForgeryXSRF
*BaseBaseImproperly Implemented Security Check for Standard - (358)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 358 (Improperly Implemented Security Check for Standard)
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.
+ClassClassProtection Mechanism Failure - (693)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure)
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
*BaseBaseIncomplete Blacklist - (184)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 184 (Incomplete Blacklist)
An application uses a "blacklist" of prohibited values, but the blacklist is incomplete.
+ClassClassImproper Input Validation - (20)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation)
The product does not validate or incorrectly validates input that can affect the control flow or data flow of a program.
*BaseBaseImproper Validation of Array Index - (129)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 129 (Improper Validation of Array Index)
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.out-of-bounds array indexindex-out-of-rangearray index underflow
*VariantVariantURL Redirection to Untrusted Site ('Open Redirect') - (601)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 601 (URL Redirection to Untrusted Site ('Open Redirect'))
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.Open RedirectCross-site RedirectCross-domain Redirect
+ClassClassImproper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') - (74)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'))
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.
*BaseBaseUse of Externally-Controlled Format String - (134)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 134 (Use of Externally-Controlled Format String)
The software uses a function that accepts a format string as an argument, but the format string originates from an external source.
+ClassClassImproper Neutralization of Special Elements used in a Command ('Command Injection') - (77)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 77 (Improper Neutralization of Special Elements used in a Command ('Command Injection'))
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.
*BaseBaseImproper Neutralization of Special Elements used in an OS Command ('OS Command Injection') - (78)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 77 (Improper Neutralization of Special Elements used in a Command ('Command Injection')) > 78 (Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'))
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.Shell injectionShell metacharacters
*BaseBaseArgument Injection or Modification - (88)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 77 (Improper Neutralization of Special Elements used in a Command ('Command Injection')) > 88 (Argument Injection or Modification)
The software does not sufficiently delimit the arguments being passed to a component in another control sphere, allowing alternate arguments to be provided, leading to potentially security-relevant changes.
*BaseBaseImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') - (79)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting'))
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.XSSCSS
*BaseBaseXML Injection (aka Blind XPath Injection) - (91)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 91 (XML Injection (aka Blind XPath Injection))
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.
+BaseBaseImproper Neutralization of CRLF Sequences ('CRLF Injection') - (93)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 93 (Improper Neutralization of CRLF Sequences ('CRLF Injection'))
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.
*BaseBaseImproper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting') - (113)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 93 (Improper Neutralization of CRLF Sequences ('CRLF Injection')) > 113 (Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Response Splitting'))
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.
*ClassClassImproper Control of Generation of Code ('Code Injection') - (94)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 94 (Improper Control of Generation of Code ('Code Injection'))
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.
+ClassClassImproper Neutralization of Special Elements in Data Query Logic - (943)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic)
The application generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
*BaseBaseImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') - (89)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic) > 89 (Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'))
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.
*BaseBaseImproper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') - (90)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic) > 90 (Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection'))
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.
+BaseBaseImproper Control of Resource Identifiers ('Resource Injection') - (99)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection'))
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.Insecure Direct Object Reference
*BaseBaseUse of Multiple Resources with Duplicate Identifier - (694)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 254 (7PK - Security Features) > 693 (Protection Mechanism Failure) > 20 (Improper Input Validation) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 694 (Use of Multiple Resources with Duplicate Identifier)
The software uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.
+CategoryCategory7PK - Time and State - (361)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State)
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."
*ClassClassConcurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') - (362)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))
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.
+CategoryCategoryState Issues - (371)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 371 (State Issues)
Weaknesses in this category are related to improper management of system state.
*BaseBaseExternal Control of Assumed-Immutable Web Parameter - (472)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 371 (State Issues) > 472 (External Control of Assumed-Immutable Web Parameter)
The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.Assumed-Immutable Parameter Tampering
+ClassClassImproper Control of a Resource Through its Lifetime - (664)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime)
The software does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.
+ClassClassExternally Controlled Reference to a Resource in Another Sphere - (610)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere)
The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.
+ClassClassUnintended Proxy or Intermediary ('Confused Deputy') - (441)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 441 (Unintended Proxy or Intermediary ('Confused Deputy'))
The software receives a request, message, or directive from an upstream component, but the software does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the software's control sphere. This causes the software 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.Confused Deputy
*BaseBaseServer-Side Request Forgery (SSRF) - (918)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 441 (Unintended Proxy or Intermediary ('Confused Deputy')) > 918 (Server-Side Request Forgery (SSRF))
The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.XSPA
*VariantVariantImproper Restriction of XML External Entity Reference ('XXE') - (611)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 611 (Improper Restriction of XML External Entity Reference ('XXE'))
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.XXE
*ClassClassImproper Initialization - (665)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization)
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.
*ClassClassIncorrect Type Conversion or Cast - (704)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 704 (Incorrect Type Conversion or Cast)
The software does not correctly convert an object, resource or structure from one type to a different type.
+ClassClassImproper Control of Dynamically-Managed Code Resources - (913)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources)
The software does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.
*VariantVariantDeserialization of Untrusted Data - (502)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 502 (Deserialization of Untrusted Data)
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.Marshaling, UnmarshalingPickling, Unpickling
+ClassClassExposure of Resource to Wrong Sphere - (668)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 668 (Exposure of Resource to Wrong Sphere)
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
+ClassClassInformation Exposure - (200)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Information Exposure)
An information exposure is the intentional or unintentional disclosure of information to an actor that is not explicitly authorized to have access to that information.Information LeakInformation Disclosure
+BaseBaseFile and Directory Information Exposure - (538)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Information Exposure) > 538 (File and Directory Information Exposure)
The product stores sensitive information in files or directories that are accessible to actors outside of the intended control sphere.
+VariantVariantInformation Exposure Through Log Files - (532)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Information Exposure) > 538 (File and Directory Information Exposure) > 532 (Information Exposure Through Log Files)
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
*VariantVariantInformation Exposure Through Debug Log Files - (534)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Information Exposure) > 538 (File and Directory Information Exposure) > 532 (Information Exposure Through Log Files) > 534 (Information Exposure Through Debug Log Files)
The application does not sufficiently restrict access to a log file that is used for debugging.
*VariantVariantSensitive Data Under FTP Root - (220)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 668 (Exposure of Resource to Wrong Sphere) > 220 (Sensitive Data Under FTP Root)
The application stores sensitive data under the FTP document root with insufficient access control, which might make it accessible to untrusted parties.
*BaseBaseFiles or Directories Accessible to External Parties - (552)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties)
Files or directories are accessible in the environment that should not be.
+ClassClassIncorrect Resource Transfer Between Spheres - (669)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 669 (Incorrect Resource Transfer Between Spheres)
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.
*BaseBaseUnrestricted Upload of File with Dangerous Type - (434)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 361 (7PK - Time and State) > 669 (Incorrect Resource Transfer Between Spheres) > 434 (Unrestricted Upload of File with Dangerous Type)
The software allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.Unrestricted File Upload
+CategoryCategoryError Conditions, Return Values, Status Codes - (389)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 389 (Error Conditions, Return Values, Status Codes)
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.
*ClassClassImproper Check for Unusual or Exceptional Conditions - (754)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 389 (Error Conditions, Return Values, Status Codes) > 754 (Improper Check for Unusual or Exceptional Conditions)
The software does not check or improperly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the software.
+CategoryCategory7PK - Code Quality - (398)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 398 (7PK - Code Quality)
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."
*BaseBaseNULL Pointer Dereference - (476)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 398 (7PK - Code Quality) > 476 (NULL Pointer Dereference)
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.
+CategoryCategoryResource Management Errors - (399)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors)
Weaknesses in this category are related to improper management of system resources.
+BaseBaseUncontrolled Resource Consumption ('Resource Exhaustion') - (400)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 400 (Uncontrolled Resource Consumption ('Resource Exhaustion'))
The software does not properly restrict the size or amount of resources that are requested or influenced by an actor, which can be used to consume more resources than intended.
+BaseBaseUncontrolled File Descriptor Consumption - (769)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 400 (Uncontrolled Resource Consumption ('Resource Exhaustion')) > 769 (Uncontrolled File Descriptor Consumption)
The software does not properly limit the number of open file descriptors that it uses.File descriptor exhaustion
*VariantVariantAllocation of File Descriptors or Handles Without Limits or Throttling - (774)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 400 (Uncontrolled Resource Consumption ('Resource Exhaustion')) > 769 (Uncontrolled File Descriptor Consumption) > 774 (Allocation of File Descriptors or Handles Without Limits or Throttling)
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.
*VariantVariantMissing Release of File Descriptor or Handle after Effective Lifetime - (775)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 400 (Uncontrolled Resource Consumption ('Resource Exhaustion')) > 769 (Uncontrolled File Descriptor Consumption) > 775 (Missing Release of File Descriptor or Handle after Effective Lifetime)
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.
*BaseBaseImproper Resource Shutdown or Release - (404)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 404 (Improper Resource Shutdown or Release)
The program does not release or incorrectly releases a resource before it is made available for re-use.
+ClassClassAsymmetric Resource Consumption (Amplification) - (405)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 405 (Asymmetric Resource Consumption (Amplification))
Software that does not appropriately monitor or control resource consumption can lead to adverse system performance.
*BaseBaseAlgorithmic Complexity - (407)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 405 (Asymmetric Resource Consumption (Amplification)) > 407 (Algorithmic Complexity)
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.
*VariantVariantDouble Free - (415)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 415 (Double Free)
The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.Double-free
*BaseBaseUse After Free - (416)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 399 (Resource Management Errors) > 416 (Use After Free)
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.Dangling pointerUse-After-Free
+CategoryCategoryChannel and Path Errors - (417)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 417 (Channel and Path Errors)
Weaknesses in this category are related to improper handling of communication channels and access paths.
*CompositeCompositeUntrusted Search Path - (426)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 417 (Channel and Path Errors) > 426 (Untrusted Search Path)
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.Untrusted Path
*BaseBaseUncontrolled Search Path Element - (427)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 417 (Channel and Path Errors) > 427 (Uncontrolled Search Path Element)
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.DLL preloadingBinary plantingInsecure library loading
*BaseBaseUnquoted Search Path or Element - (428)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 17 (Code) > 18 (Source Code) > 417 (Channel and Path Errors) > 428 (Unquoted Search Path or Element)
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.
+CategoryCategory7PK - Environment - (2)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 2 (7PK - Environment)
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."
+ClassClassImproper Interaction Between Multiple Entities - (435)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 2 (7PK - Environment) > 435 (Improper Interaction Between Multiple Entities)
An interaction error occurs when two entities work correctly when running independently, but they interact in unexpected ways when they are run together.
+BaseBaseInterpretation Conflict - (436)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 2 (7PK - Environment) > 435 (Improper Interaction Between Multiple Entities) > 436 (Interpretation Conflict)
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.
*BaseBaseInconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling') - (444)
1003 (Weaknesses for Simplified Mapping of Published Vulnerabilities) > 2 (7PK - Environment) > 435 (Improper Interaction Between Multiple Entities) > 436 (Interpretation Conflict) > 444 (Inconsistent Interpretation of HTTP Requests ('HTTP Request Smuggling'))
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.
+ Notes

Maintenance

This view contains many entries that are being considered for use in NVD in 2015. This list is expected to change with contributions from additional sources.
+ References
[REF-1] NIST. "CWE - Common Weakness Enumeration". <http://nvd.nist.gov/cwe.cfm>.
+ Content History
Submissions
Submission DateSubmitterOrganizationSource
2015-12-07CWE Content TeamMITRE
Contributions
Contribution DateContributorOrganizationSource
2015-12-07NIST
Provided many relationships.
+ View Metrics
CWEs in this viewTotal CWEs
Total114out of982
Weaknesses93out of 714
Categories21out of 237
Views0out of 31

More information is available — Please select a different filter.
Page Last Updated: November 15, 2017