Software weaknesses, explained simply
CWE names recurring weakness types found in software and devices; it is not a list of individual vulnerabilities. Scantide keeps the MITRE terminology visible, then explains what each weakness means and shows familiar, non-operational examples of what it can look like in a real product.
CWE-5 · J2EE Misconfiguration: Data Transmission Without Encryption
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-5 · J2EE Misconfiguration: Data Transmission Without Encryption
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
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.
CWE-6 · J2EE Misconfiguration: Insufficient Session-ID Length
J2EE Misconfiguration: Insufficient Session-ID Length
Technical detail
CWE-6 · J2EE Misconfiguration: Insufficient Session-ID Length
J2EE Misconfiguration: Insufficient Session-ID Length
In plain English
J2EE Misconfiguration: Insufficient Session-ID Length
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The J2EE application is configured to use an insufficient session ID length.
CWE-7 · J2EE Misconfiguration: Missing Custom Error Page
The product can expose information beyond the audience that should receive it.
Important
CWE-7 · J2EE Misconfiguration: Missing Custom Error Page
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The default error page of a web application should not display sensitive information about the product.
CWE-8 · J2EE Misconfiguration: Entity Bean Declared Remote
The product can expose information beyond the audience that should receive it.
Important
CWE-8 · J2EE Misconfiguration: Entity Bean Declared Remote
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
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.
CWE-9 · J2EE Misconfiguration: Weak Access Permissions for EJB Methods
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-9 · J2EE Misconfiguration: Weak Access Permissions for EJB Methods
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the product.
CWE-11 · ASP.NET Misconfiguration: Creating Debug Binary
ASP.NET Misconfiguration: Creating Debug Binary
Technical detail
CWE-11 · ASP.NET Misconfiguration: Creating Debug Binary
ASP.NET Misconfiguration: Creating Debug Binary
In plain English
ASP.NET Misconfiguration: Creating Debug Binary
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Debugging messages help attackers learn about the system and plan a form of attack.
CWE-12 · ASP.NET Misconfiguration: Missing Custom Error Page
ASP.NET Misconfiguration: Missing Custom Error Page
Technical detail
CWE-12 · ASP.NET Misconfiguration: Missing Custom Error Page
ASP.NET Misconfiguration: Missing Custom Error Page
In plain English
ASP.NET Misconfiguration: Missing Custom Error Page
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses.
CWE-13 · ASP.NET Misconfiguration: Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-13 · ASP.NET Misconfiguration: Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-14 · Compiler Removal of Code to Clear Buffers
The product handles memory in an unsafe way.
Important
CWE-14 · Compiler Removal of Code to Clear Buffers
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
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."
CWE-15 · External Control of System or Configuration Setting
External Control of System or Configuration Setting
Technical detail
CWE-15 · External Control of System or Configuration Setting
External Control of System or Configuration Setting
In plain English
External Control of System or Configuration Setting
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
One or more system settings or configuration elements can be externally controlled by a user.
CWE-20 · Improper Input Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-20 · Improper Input Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
User-controlled path components can escape the intended directory.
Important
CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
User-controlled path components can escape the intended directory.
In plain English
User-controlled path components can escape the intended directory.
What this can look like
A download endpoint expects a filename, but crafted path segments make it read a configuration or credential file outside the download folder.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CWE-23 · Relative Path Traversal
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-23 · Relative Path Traversal
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize sequences such as ".." that can resolve to a location that is outside of that directory.
CWE-24 · Path Traversal: '../filedir'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-24 · Path Traversal: '../filedir'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
CWE-25 · Path Traversal: '/../filedir'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-25 · Path Traversal: '/../filedir'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/../" sequences that can resolve to a location that is outside of that directory.
CWE-26 · Path Traversal: '/dir/../filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-26 · Path Traversal: '/dir/../filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/dir/../filename" sequences that can resolve to a location that is outside of that directory.
CWE-27 · Path Traversal: 'dir/../../filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-27 · Path Traversal: 'dir/../../filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize multiple internal "../" sequences that can resolve to a location that is outside of that directory.
CWE-28 · Path Traversal: '..\filedir'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-28 · Path Traversal: '..\filedir'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "..\" sequences that can resolve to a location that is outside of that directory.
CWE-29 · Path Traversal: '\..\filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-29 · Path Traversal: '\..\filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
CWE-30 · Path Traversal: '\dir\..\filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-30 · Path Traversal: '\dir\..\filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\dir\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
CWE-31 · Path Traversal: 'dir\..\..\filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-31 · Path Traversal: 'dir\..\..\filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize 'dir\..\..\filename' (multiple internal backslash dot dot) sequences that can resolve to a location that is outside of that directory.
CWE-32 · Path Traversal: '...' (Triple Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-32 · Path Traversal: '...' (Triple Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '...' (triple dot) sequences that can resolve to a location that is outside of that directory.
CWE-33 · Path Traversal: '....' (Multiple Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-33 · Path Traversal: '....' (Multiple Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....' (multiple dot) sequences that can resolve to a location that is outside of that directory.
CWE-34 · Path Traversal: '....//'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-34 · Path Traversal: '....//'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....//' (doubled dot dot slash) sequences that can resolve to a location that is outside of that directory.
CWE-35 · Path Traversal: '.../...//'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-35 · Path Traversal: '.../...//'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory.
CWE-36 · Absolute Path Traversal
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-36 · Absolute Path Traversal
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory.
CWE-37 · Path Traversal: '/absolute/pathname/here'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-37 · Path Traversal: '/absolute/pathname/here'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts input in the form of a slash absolute path ('/absolute/pathname/here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-38 · Path Traversal: '\absolute\pathname\here'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-38 · Path Traversal: '\absolute\pathname\here'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts input in the form of a backslash absolute path ('\absolute\pathname\here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-39 · Path Traversal: 'C:dirname'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-39 · Path Traversal: 'C:dirname'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts input that contains a drive letter or Windows volume letter ('C:dirname') that potentially redirects access to an unintended location or arbitrary file.
CWE-40 · Path Traversal: '\\UNC\share\name\' (Windows UNC Share)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-40 · Path Traversal: '\\UNC\share\name\' (Windows UNC Share)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts input that identifies a Windows UNC share ('\\UNC\share\name') that potentially redirects access to an unintended location or arbitrary file.
CWE-41 · Improper Resolution of Path Equivalence
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-41 · Improper Resolution of Path Equivalence
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory names. The associated manipulations are intended to generate multiple names for the same object.
CWE-42 · Path Equivalence: 'filename.' (Trailing Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-42 · Path Equivalence: 'filename.' (Trailing Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of trailing dot ('filedir.') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-43 · Path Equivalence: 'filename....' (Multiple Trailing Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-43 · Path Equivalence: 'filename....' (Multiple Trailing Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of multiple trailing dot ('filedir....') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-44 · Path Equivalence: 'file.name' (Internal Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-44 · Path Equivalence: 'file.name' (Internal Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of internal dot ('file.ordir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-45 · Path Equivalence: 'file...name' (Multiple Internal Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-45 · Path Equivalence: 'file...name' (Multiple Internal Dot)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of multiple internal dot ('file...dir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-46 · Path Equivalence: 'filename ' (Trailing Space)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-46 · Path Equivalence: 'filename ' (Trailing Space)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of trailing space ('filedir ') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-47 · Path Equivalence: ' filename' (Leading Space)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-47 · Path Equivalence: ' filename' (Leading Space)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of leading space (' filedir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-48 · Path Equivalence: 'file name' (Internal Whitespace)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-48 · Path Equivalence: 'file name' (Internal Whitespace)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of internal space ('file(SPACE)name') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-49 · Path Equivalence: 'filename/' (Trailing Slash)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-49 · Path Equivalence: 'filename/' (Trailing Slash)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of trailing slash ('filedir/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-50 · Path Equivalence: '//multiple/leading/slash'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-50 · Path Equivalence: '//multiple/leading/slash'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-51 · Path Equivalence: '/multiple//internal/slash'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-51 · Path Equivalence: '/multiple//internal/slash'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-52 · Path Equivalence: '/multiple/trailing/slash//'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-52 · Path Equivalence: '/multiple/trailing/slash//'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of multiple trailing slash ('/multiple/trailing/slash//') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-53 · Path Equivalence: '\multiple\\internal\backslash'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-53 · Path Equivalence: '\multiple\\internal\backslash'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of multiple internal backslash ('\multiple\trailing\\slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-54 · Path Equivalence: 'filedir\' (Trailing Backslash)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-54 · Path Equivalence: 'filedir\' (Trailing Backslash)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of trailing backslash ('filedir\') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-55 · Path Equivalence: '/./' (Single Dot Directory)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-55 · Path Equivalence: '/./' (Single Dot Directory)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of single dot directory exploit ('/./') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-56 · Path Equivalence: 'filedir*' (Wildcard)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-56 · Path Equivalence: 'filedir*' (Wildcard)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product accepts path input in the form of asterisk wildcard ('filedir*') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-57 · Path Equivalence: 'fakedir/../realdir/filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-57 · Path Equivalence: 'fakedir/../realdir/filename'
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product contains protection mechanisms to restrict access to 'realdir/filename', but it constructs pathnames using external input in the form of 'fakedir/../realdir/filename' that are not handled by those mechanisms. This allows attackers to perform unauthorized actions against the targeted file.
CWE-58 · Path Equivalence: Windows 8.3 Filename
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-58 · Path Equivalence: Windows 8.3 Filename
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product contains a protection mechanism that restricts access to a long filename on a Windows operating system, but it does not properly restrict access to the equivalent short "8.3" filename.
CWE-59 · Improper Link Resolution Before File Access ('Link Following')
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-59 · Improper Link Resolution Before File Access ('Link Following')
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product attempts to access a file based on the filename, but it does not properly prevent that filename from identifying a link or shortcut that resolves to an unintended resource.
CWE-61 · UNIX Symbolic Link (Symlink) Following
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-61 · UNIX Symbolic Link (Symlink) Following
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-62 · UNIX Hard Link
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-62 · UNIX Hard Link
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product, when opening a file or directory, does not sufficiently account for when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-64 · Windows Shortcut Following (.LNK)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-64 · Windows Shortcut Following (.LNK)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product, when opening a file or directory, does not sufficiently handle when the file is a Windows shortcut (.LNK) whose target is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-65 · Windows Hard Link
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-65 · Windows Hard Link
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-66 · Improper Handling of File Names that Identify Virtual Resources
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-66 · Improper Handling of File Names that Identify Virtual Resources
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-67 · Improper Handling of Windows Device Names
The product can expose information beyond the audience that should receive it.
Important
CWE-67 · Improper Handling of Windows Device Names
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a Windows device name such as AUX or CON. This typically leads to denial of service or an information exposure when the application attempts to process the pathname as a regular file.
CWE-69 · Improper Handling of Windows ::DATA Alternate Data Stream
Improper Handling of Windows ::DATA Alternate Data Stream
Technical detail
CWE-69 · Improper Handling of Windows ::DATA Alternate Data Stream
Improper Handling of Windows ::DATA Alternate Data Stream
In plain English
Improper Handling of Windows ::DATA Alternate Data Stream
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly prevent access to, or detect usage of, alternate data streams (ADS).
CWE-71 · DEPRECATED: Apple '.DS_Store'
DEPRECATED: Apple '.DS_Store'
Technical detail
CWE-71 · DEPRECATED: Apple '.DS_Store'
DEPRECATED: Apple '.DS_Store'
In plain English
DEPRECATED: Apple '.DS_Store'
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-72 · Improper Handling of Apple HFS+ Alternate Data Stream Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-72 · Improper Handling of Apple HFS+ Alternate Data Stream Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.
CWE-73 · External Control of File Name or Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-73 · External Control of File Name or Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product allows user input to control or influence paths or file names that are used in filesystem operations.
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
CWE-75 · Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-75 · Failure to Sanitize Special Elements into a Different Plane (Special Element Injection)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not adequately filter user-controlled input for special elements with control implications.
CWE-76 · Improper Neutralization of Equivalent Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-76 · Improper Neutralization of Equivalent Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')
Untrusted input reaches a command interpreter without adequate control.
Headline signal
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')
Untrusted input reaches a command interpreter without adequate control.
In plain English
Untrusted input reaches a command interpreter without adequate control.
What this can look like
A management feature passes user-supplied text into a system command, allowing unintended commands to run with the application’s privileges.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Input is incorporated into an operating-system command unsafely.
Headline signal
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Input is incorporated into an operating-system command unsafely.
In plain English
Input is incorporated into an operating-system command unsafely.
What this can look like
A diagnostic field intended for a hostname is interpreted as part of a shell command, so an attacker can make the device execute an additional command.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-80 · Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-80 · Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product 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.
CWE-81 · Improper Neutralization of Script in an Error Message Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-81 · Improper Neutralization of Script in an Error Message Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page.
CWE-82 · Improper Neutralization of Script in Attributes of IMG Tags in a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-82 · Improper Neutralization of Script in Attributes of IMG Tags in a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The web application does not neutralize or incorrectly neutralizes scripting elements within attributes of HTML IMG tags, such as the src attribute.
CWE-83 · Improper Neutralization of Script in Attributes in a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-83 · Improper Neutralization of Script in Attributes in a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not neutralize or incorrectly neutralizes "javascript:" or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style.
CWE-84 · Improper Neutralization of Encoded URI Schemes in a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-84 · Improper Neutralization of Encoded URI Schemes in a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings.
CWE-85 · Doubled Character XSS Manipulations
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-85 · Doubled Character XSS Manipulations
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.
CWE-86 · Improper Neutralization of Invalid Characters in Identifiers in Web Pages
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-86 · Improper Neutralization of Invalid Characters in Identifiers in Web Pages
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers.
CWE-87 · Improper Neutralization of Alternate XSS Syntax
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-87 · Improper Neutralization of Alternate XSS Syntax
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax.
CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-88 · Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Input can change the structure of a database query.
Important
CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Input can change the structure of a database query.
In plain English
Input can change the structure of a database query.
What this can look like
A login or search field is joined directly into SQL, allowing an attacker to alter what the database query does instead of supplying ordinary data.
A search, filter, or login value changes the meaning of a database query and exposes or modifies records outside the intended scope.
An application builds a query from untrusted text, letting crafted input affect the query structure rather than only the supplied value.
MITRE description from the synchronized CWE record
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. 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.
CWE-90 · Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-90 · Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product constructs all or part of an LDAP query using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended LDAP query when it is sent to a downstream component.
CWE-91 · XML Injection (aka Blind XPath Injection)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-91 · XML Injection (aka Blind XPath Injection)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not properly neutralize special elements that are used in XML, allowing attackers to modify the syntax, content, or commands of the XML before it is processed by an end system.
CWE-92 · DEPRECATED: Improper Sanitization of Custom Special Characters
DEPRECATED: Improper Sanitization of Custom Special Characters
Technical detail
CWE-92 · DEPRECATED: Improper Sanitization of Custom Special Characters
DEPRECATED: Improper Sanitization of Custom Special Characters
In plain English
DEPRECATED: Improper Sanitization of Custom Special Characters
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
CWE-94 · Improper Control of Generation of Code ('Code Injection')
Untrusted data can become executable code.
Headline signal
CWE-94 · Improper Control of Generation of Code ('Code Injection')
Untrusted data can become executable code.
In plain English
Untrusted data can become executable code.
What this can look like
A feature evaluates attacker-controlled content as code, allowing the attacker to run logic that the developer never intended.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-95 · Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before using the input in a dynamic evaluation call (e.g. "eval").
CWE-96 · Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-96 · Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes code syntax before inserting the input into an executable resource, such as a library, configuration file, or template.
CWE-97 · Improper Neutralization of Server-Side Includes (SSI) Within a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-97 · Improper Neutralization of Server-Side Includes (SSI) Within a Web Page
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product generates a web page, but does not neutralize or incorrectly neutralizes user-controllable input that could be interpreted as a server-side include (SSI) directive.
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-99 · Improper Control of Resource Identifiers ('Resource Injection')
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-99 · Improper Control of Resource Identifiers ('Resource Injection')
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control.
CWE-102 · Struts: Duplicate Validation Forms
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-102 · Struts: Duplicate Validation Forms
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses multiple validation forms with the same name, which might cause the Struts Validator to validate a form that the programmer does not expect.
CWE-103 · Struts: Incomplete validate() Method Definition
Struts: Incomplete validate() Method Definition
Technical detail
CWE-103 · Struts: Incomplete validate() Method Definition
Struts: Incomplete validate() Method Definition
In plain English
Struts: Incomplete validate() Method Definition
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has a validator form that either does not define a validate() method, or defines a validate() method but does not call super.validate().
CWE-104 · Struts: Form Bean Does Not Extend Validation Class
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-104 · Struts: Form Bean Does Not Extend Validation Class
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-105 · Struts: Form Field Without Validator
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-105 · Struts: Form Field Without Validator
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product has a form field that is not validated by a corresponding validation form, which can introduce other weaknesses related to insufficient input validation.
CWE-106 · Struts: Plug-in Framework not in Use
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-106 · Struts: Plug-in Framework not in Use
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-107 · Struts: Unused Validation Form
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-107 · Struts: Unused Validation Form
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
An unused validation form indicates that validation logic is not up-to-date.
CWE-108 · Struts: Unvalidated Action Form
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-108 · Struts: Unvalidated Action Form
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
Every Action Form must have a corresponding validation form.
CWE-109 · Struts: Validator Turned Off
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-109 · Struts: Validator Turned Off
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-110 · Struts: Validator Without Form Field
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-110 · Struts: Validator Without Form Field
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.
CWE-111 · Direct Use of Unsafe JNI
Direct Use of Unsafe JNI
Technical detail
CWE-111 · Direct Use of Unsafe JNI
Direct Use of Unsafe JNI
In plain English
Direct Use of Unsafe JNI
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-112 · Missing XML Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-112 · Missing XML Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product accepts XML from an untrusted source but does not validate the XML against the proper schema.
CWE-113 · Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-113 · Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives data from an HTTP agent/component (e.g., web server, proxy, browser, etc.), but it does not neutralize or incorrectly neutralizes CR and LF characters before the data is included in outgoing HTTP headers.
CWE-114 · Process Control
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-114 · Process Control
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
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.
CWE-115 · Misinterpretation of Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-115 · Misinterpretation of Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.
CWE-116 · Improper Encoding or Escaping of Output
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-116 · Improper Encoding or Escaping of Output
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
CWE-117 · Improper Output Neutralization for Logs
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-117 · Improper Output Neutralization for Logs
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
CWE-118 · Incorrect Access of Indexable Resource ('Range Error')
The product handles memory in an unsafe way.
Important
CWE-118 · Incorrect Access of Indexable Resource ('Range Error')
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product does not restrict or incorrectly restricts operations within the boundaries of a resource that is accessed using an index or pointer, such as memory or files.
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer
The product handles memory in an unsafe way.
Important
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory Buffer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Data can exceed the space reserved for it in memory.
Important
CWE-120 · Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')
Data can exceed the space reserved for it in memory.
In plain English
Data can exceed the space reserved for it in memory.
What this can look like
A network service copies an oversized value into a fixed-size buffer, corrupting nearby memory and potentially crashing the service or enabling code execution.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
CWE-121 · Stack-based Buffer Overflow
The product handles memory in an unsafe way.
Important
CWE-121 · Stack-based Buffer Overflow
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
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).
CWE-122 · Heap-based Buffer Overflow
The product handles memory in an unsafe way.
Important
CWE-122 · Heap-based Buffer Overflow
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
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().
CWE-123 · Write-what-where Condition
The product handles memory in an unsafe way.
Important
CWE-123 · Write-what-where Condition
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
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.
CWE-124 · Buffer Underwrite ('Buffer Underflow')
The product handles memory in an unsafe way.
Important
CWE-124 · Buffer Underwrite ('Buffer Underflow')
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.
CWE-125 · Out-of-bounds Read
The product handles memory in an unsafe way.
Important
CWE-125 · Out-of-bounds Read
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product reads data past the end, or before the beginning, of the intended buffer.
CWE-126 · Buffer Over-read
The product handles memory in an unsafe way.
Important
CWE-126 · Buffer Over-read
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.
CWE-127 · Buffer Under-read
The product handles memory in an unsafe way.
Important
CWE-127 · Buffer Under-read
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer.
CWE-128 · Wrap-around Error
Wrap-around Error
Technical detail
CWE-128 · Wrap-around Error
Wrap-around Error
In plain English
Wrap-around Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-129 · Improper Validation of Array Index
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-129 · Improper Validation of Array Index
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-130 · Improper Handling of Length Parameter Inconsistency
Improper Handling of Length Parameter Inconsistency
Technical detail
CWE-130 · Improper Handling of Length Parameter Inconsistency
Improper Handling of Length Parameter Inconsistency
In plain English
Improper Handling of Length Parameter Inconsistency
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product parses a formatted message or structure, but it does not handle or incorrectly handles a length field that is inconsistent with the actual length of the associated data.
CWE-131 · Incorrect Calculation of Buffer Size
The product handles memory in an unsafe way.
Important
CWE-131 · Incorrect Calculation of Buffer Size
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.
CWE-132 · DEPRECATED: Miscalculated Null Termination
DEPRECATED: Miscalculated Null Termination
Technical detail
CWE-132 · DEPRECATED: Miscalculated Null Termination
DEPRECATED: Miscalculated Null Termination
In plain English
DEPRECATED: Miscalculated Null Termination
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
This entry has been deprecated because it was a duplicate of CWE-170. All content has been transferred to CWE-170.
CWE-134 · Use of Externally-Controlled Format String
Use of Externally-Controlled Format String
Technical detail
CWE-134 · Use of Externally-Controlled Format String
Use of Externally-Controlled Format String
In plain English
Use of Externally-Controlled Format String
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a function that accepts a format string as an argument, but the format string originates from an external source.
CWE-135 · Incorrect Calculation of Multi-Byte String Length
Incorrect Calculation of Multi-Byte String Length
Technical detail
CWE-135 · Incorrect Calculation of Multi-Byte String Length
Incorrect Calculation of Multi-Byte String Length
In plain English
Incorrect Calculation of Multi-Byte String Length
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not correctly calculate the length of strings that can contain wide or multi-byte characters.
CWE-138 · Improper Neutralization of Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-138 · Improper Neutralization of Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as control elements or syntactic markers when they are sent to a downstream component.
CWE-140 · Improper Neutralization of Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-140 · Improper Neutralization of Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not neutralize or incorrectly neutralizes delimiters.
CWE-141 · Improper Neutralization of Parameter/Argument Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-141 · Improper Neutralization of Parameter/Argument Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as parameter or argument delimiters when they are sent to a downstream component.
CWE-142 · Improper Neutralization of Value Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-142 · Improper Neutralization of Value Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as value delimiters when they are sent to a downstream component.
CWE-143 · Improper Neutralization of Record Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-143 · Improper Neutralization of Record Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as record delimiters when they are sent to a downstream component.
CWE-144 · Improper Neutralization of Line Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-144 · Improper Neutralization of Line Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as line delimiters when they are sent to a downstream component.
CWE-145 · Improper Neutralization of Section Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-145 · Improper Neutralization of Section Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as section delimiters when they are sent to a downstream component.
CWE-146 · Improper Neutralization of Expression/Command Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-146 · Improper Neutralization of Expression/Command Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as expression or command delimiters when they are sent to a downstream component.
CWE-147 · Improper Neutralization of Input Terminators
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-147 · Improper Neutralization of Input Terminators
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as input terminators when they are sent to a downstream component.
CWE-148 · Improper Neutralization of Input Leaders
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-148 · Improper Neutralization of Input Leaders
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle when a leading character or sequence ("leader") is missing or malformed, or if multiple leaders are used when only one should be allowed.
CWE-149 · Improper Neutralization of Quoting Syntax
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-149 · Improper Neutralization of Quoting Syntax
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
Quotes injected into a product can be used to compromise a system. As data are parsed, an injected/absent/duplicate/malformed use of quotes may cause the process to take unexpected actions.
CWE-150 · Improper Neutralization of Escape, Meta, or Control Sequences
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-150 · Improper Neutralization of Escape, Meta, or Control Sequences
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as escape, meta, or control character sequences when they are sent to a downstream component.
CWE-151 · Improper Neutralization of Comment Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-151 · Improper Neutralization of Comment Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as comment delimiters when they are sent to a downstream component.
CWE-152 · Improper Neutralization of Macro Symbols
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-152 · Improper Neutralization of Macro Symbols
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as macro symbols when they are sent to a downstream component.
CWE-153 · Improper Neutralization of Substitution Characters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-153 · Improper Neutralization of Substitution Characters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as substitution characters when they are sent to a downstream component.
CWE-154 · Improper Neutralization of Variable Name Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-154 · Improper Neutralization of Variable Name Delimiters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as variable name delimiters when they are sent to a downstream component.
CWE-155 · Improper Neutralization of Wildcards or Matching Symbols
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-155 · Improper Neutralization of Wildcards or Matching Symbols
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as wildcards or matching symbols when they are sent to a downstream component.
CWE-156 · Improper Neutralization of Whitespace
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-156 · Improper Neutralization of Whitespace
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as whitespace when they are sent to a downstream component.
CWE-157 · Failure to Sanitize Paired Delimiters
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-157 · Failure to Sanitize Paired Delimiters
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
The product does not properly handle the characters that are used to mark the beginning and ending of a group of entities, such as parentheses, brackets, and braces.
CWE-158 · Improper Neutralization of Null Byte or NUL Character
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-158 · Improper Neutralization of Null Byte or NUL Character
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes NUL characters or null bytes when they are sent to a downstream component.
CWE-159 · Improper Handling of Invalid Use of Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-159 · Improper Handling of Invalid Use of Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-160 · Improper Neutralization of Leading Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-160 · Improper Neutralization of Leading Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes leading special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
CWE-161 · Improper Neutralization of Multiple Leading Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-161 · Improper Neutralization of Multiple Leading Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple leading special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
CWE-162 · Improper Neutralization of Trailing Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-162 · Improper Neutralization of Trailing Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
CWE-163 · Improper Neutralization of Multiple Trailing Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-163 · Improper Neutralization of Multiple Trailing Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple trailing special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
CWE-164 · Improper Neutralization of Internal Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-164 · Improper Neutralization of Internal Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes internal special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
CWE-165 · Improper Neutralization of Multiple Internal Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-165 · Improper Neutralization of Multiple Internal Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes multiple internal special elements that could be interpreted in unexpected ways when they are sent to a downstream component.
CWE-166 · Improper Handling of Missing Special Element
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-166 · Improper Handling of Missing Special Element
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not handle or incorrectly handles when an expected special element is missing.
CWE-167 · Improper Handling of Additional Special Element
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-167 · Improper Handling of Additional Special Element
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided.
CWE-168 · Improper Handling of Inconsistent Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-168 · Improper Handling of Inconsistent Special Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle input in which an inconsistency exists between two or more special characters or reserved words.
CWE-170 · Improper Null Termination
Improper Null Termination
Technical detail
CWE-170 · Improper Null Termination
Improper Null Termination
In plain English
Improper Null Termination
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.
CWE-172 · Encoding Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-172 · Encoding Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly encode or decode the data, resulting in unexpected values.
CWE-173 · Improper Handling of Alternate Encoding
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-173 · Improper Handling of Alternate Encoding
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.
CWE-174 · Double Decoding of the Same Data
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-174 · Double Decoding of the Same Data
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations.
CWE-175 · Improper Handling of Mixed Encoding
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-175 · Improper Handling of Mixed Encoding
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle when the same input uses several different (mixed) encodings.
CWE-176 · Improper Handling of Unicode Encoding
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-176 · Improper Handling of Unicode Encoding
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle when an input contains Unicode encoding.
CWE-177 · Improper Handling of URL Encoding (Hex Encoding)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-177 · Improper Handling of URL Encoding (Hex Encoding)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle when all or part of an input has been URL encoded.
CWE-178 · Improper Handling of Case Sensitivity
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-178 · Improper Handling of Case Sensitivity
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
CWE-179 · Incorrect Behavior Order: Early Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-179 · Incorrect Behavior Order: Early Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product validates input before applying protection mechanisms that modify the input, which could allow an attacker to bypass the validation via dangerous inputs that only arise after the modification.
CWE-180 · Incorrect Behavior Order: Validate Before Canonicalize
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-180 · Incorrect Behavior Order: Validate Before Canonicalize
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.
CWE-181 · Incorrect Behavior Order: Validate Before Filter
Incorrect Behavior Order: Validate Before Filter
Technical detail
CWE-181 · Incorrect Behavior Order: Validate Before Filter
Incorrect Behavior Order: Validate Before Filter
In plain English
Incorrect Behavior Order: Validate Before Filter
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product validates data before it has been filtered, which prevents the product from detecting data that becomes invalid after the filtering step.
CWE-182 · Collapse of Data into Unsafe Value
Collapse of Data into Unsafe Value
Technical detail
CWE-182 · Collapse of Data into Unsafe Value
Collapse of Data into Unsafe Value
In plain English
Collapse of Data into Unsafe Value
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product filters data in a way that causes it to be reduced or "collapsed" into an unsafe value that violates an expected security property.
CWE-183 · Permissive List of Allowed Inputs
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-183 · Permissive List of Allowed Inputs
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-184 · Incomplete List of Disallowed Inputs
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-184 · Incomplete List of Disallowed Inputs
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-185 · Incorrect Regular Expression
Incorrect Regular Expression
Technical detail
CWE-185 · Incorrect Regular Expression
Incorrect Regular Expression
In plain English
Incorrect Regular Expression
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product specifies a regular expression in a way that causes data to be improperly matched or compared.
CWE-186 · Overly Restrictive Regular Expression
Overly Restrictive Regular Expression
Technical detail
CWE-186 · Overly Restrictive Regular Expression
Overly Restrictive Regular Expression
In plain English
Overly Restrictive Regular Expression
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A regular expression is overly restrictive, which prevents dangerous values from being detected.
CWE-187 · Partial String Comparison
Partial String Comparison
Technical detail
CWE-187 · Partial String Comparison
Partial String Comparison
In plain English
Partial String Comparison
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs a comparison that only examines a portion of a factor before determining whether there is a match, such as a substring, leading to resultant weaknesses.
CWE-188 · Reliance on Data/Memory Layout
The product handles memory in an unsafe way.
Important
CWE-188 · Reliance on Data/Memory Layout
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product makes invalid assumptions about how protocol data or memory is organized at a lower level, resulting in unintended program behavior.
CWE-190 · Integer Overflow or Wraparound
Integer Overflow or Wraparound
Technical detail
CWE-190 · Integer Overflow or Wraparound
Integer Overflow or Wraparound
In plain English
Integer Overflow or Wraparound
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This 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 become a very small or negative number.
CWE-191 · Integer Underflow (Wrap or Wraparound)
Integer Underflow (Wrap or Wraparound)
Technical detail
CWE-191 · Integer Underflow (Wrap or Wraparound)
Integer Underflow (Wrap or Wraparound)
In plain English
Integer Underflow (Wrap or Wraparound)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-192 · Integer Coercion Error
Integer Coercion Error
Technical detail
CWE-192 · Integer Coercion Error
Integer Coercion Error
In plain English
Integer Coercion Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types.
CWE-193 · Off-by-one Error
Off-by-one Error
Technical detail
CWE-193 · Off-by-one Error
Off-by-one Error
In plain English
Off-by-one Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.
CWE-194 · Unexpected Sign Extension
Unexpected Sign Extension
Technical detail
CWE-194 · Unexpected Sign Extension
Unexpected Sign Extension
In plain English
Unexpected Sign Extension
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs an operation on a number that causes it to be sign extended when it is transformed into a larger data type. When the original number is negative, this can produce unexpected values that lead to resultant weaknesses.
CWE-195 · Signed to Unsigned Conversion Error
Signed to Unsigned Conversion Error
Technical detail
CWE-195 · Signed to Unsigned Conversion Error
Signed to Unsigned Conversion Error
In plain English
Signed to Unsigned Conversion Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a signed primitive and performs a cast to an unsigned primitive, which can produce an unexpected value if the value of the signed primitive can not be represented using an unsigned primitive.
CWE-196 · Unsigned to Signed Conversion Error
Unsigned to Signed Conversion Error
Technical detail
CWE-196 · Unsigned to Signed Conversion Error
Unsigned to Signed Conversion Error
In plain English
Unsigned to Signed Conversion Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses an unsigned primitive and performs a cast to a signed primitive, which can produce an unexpected value if the value of the unsigned primitive can not be represented using a signed primitive.
CWE-197 · Numeric Truncation Error
Numeric Truncation Error
Technical detail
CWE-197 · Numeric Truncation Error
Numeric Truncation Error
In plain English
Numeric Truncation Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.
CWE-198 · Use of Incorrect Byte Ordering
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-198 · Use of Incorrect Byte Ordering
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component, but it does not account for byte ordering (e.g. big-endian and little-endian) when processing the input, causing an incorrect number or value to be used.
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
Information is revealed to someone who should not receive it.
Important
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
Information is revealed to someone who should not receive it.
In plain English
Information is revealed to someone who should not receive it.
What this can look like
An unauthenticated status page exposes internal addresses, usernames, tokens, or configuration details that help an attacker understand the environment.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
CWE-201 · Insertion of Sensitive Information Into Sent Data
The product can expose information beyond the audience that should receive it.
Important
CWE-201 · Insertion of Sensitive Information Into Sent Data
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
CWE-202 · Exposure of Sensitive Information Through Data Queries
The product can expose information beyond the audience that should receive it.
Important
CWE-202 · Exposure of Sensitive Information Through Data Queries
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
CWE-203 · Observable Discrepancy
Observable Discrepancy
Technical detail
CWE-203 · Observable Discrepancy
Observable Discrepancy
In plain English
Observable Discrepancy
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor.
CWE-204 · Observable Response Discrepancy
Observable Response Discrepancy
Technical detail
CWE-204 · Observable Response Discrepancy
Observable Response Discrepancy
In plain English
Observable Response Discrepancy
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-205 · Observable Behavioral Discrepancy
Observable Behavioral Discrepancy
Technical detail
CWE-205 · Observable Behavioral Discrepancy
Observable Behavioral Discrepancy
In plain English
Observable Behavioral Discrepancy
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-206 · Observable Internal Behavioral Discrepancy
Observable Internal Behavioral Discrepancy
Technical detail
CWE-206 · Observable Internal Behavioral Discrepancy
Observable Internal Behavioral Discrepancy
In plain English
Observable Internal Behavioral Discrepancy
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-207 · Observable Behavioral Discrepancy With Equivalent Products
Observable Behavioral Discrepancy With Equivalent Products
Technical detail
CWE-207 · Observable Behavioral Discrepancy With Equivalent Products
Observable Behavioral Discrepancy With Equivalent Products
In plain English
Observable Behavioral Discrepancy With Equivalent Products
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-208 · Observable Timing Discrepancy
Observable Timing Discrepancy
Technical detail
CWE-208 · Observable Timing Discrepancy
Observable Timing Discrepancy
In plain English
Observable Timing Discrepancy
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-209 · Generation of Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-209 · Generation of Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product generates an error message that includes sensitive information about its environment, users, or associated data.
CWE-210 · Self-generated Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-210 · Self-generated Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.
CWE-211 · Externally-Generated Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-211 · Externally-Generated Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the product, such as an error generated by the programming language interpreter that a software application uses. The error can contain sensitive system information.
CWE-212 · Improper Removal of Sensitive Information Before Storage or Transfer
The product can expose information beyond the audience that should receive it.
Important
CWE-212 · Improper Removal of Sensitive Information Before Storage or Transfer
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
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.
CWE-213 · Exposure of Sensitive Information Due to Incompatible Policies
The product can expose information beyond the audience that should receive it.
Important
CWE-213 · Exposure of Sensitive Information Due to Incompatible Policies
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
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.
CWE-214 · Invocation of Process Using Visible Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-214 · Invocation of Process Using Visible Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
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.
CWE-215 · Insertion of Sensitive Information Into Debugging Code
The product can expose information beyond the audience that should receive it.
Important
CWE-215 · Insertion of Sensitive Information Into Debugging Code
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
CWE-216 · DEPRECATED: Containment Errors (Container Errors)
DEPRECATED: Containment Errors (Container Errors)
Technical detail
CWE-216 · DEPRECATED: Containment Errors (Container Errors)
DEPRECATED: Containment Errors (Container Errors)
In plain English
DEPRECATED: Containment Errors (Container Errors)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-217 · DEPRECATED: Failure to Protect Stored Data from Modification
DEPRECATED: Failure to Protect Stored Data from Modification
Technical detail
CWE-217 · DEPRECATED: Failure to Protect Stored Data from Modification
DEPRECATED: Failure to Protect Stored Data from Modification
In plain English
DEPRECATED: Failure to Protect Stored Data from Modification
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-218 · DEPRECATED: Failure to provide confidentiality for stored data
DEPRECATED: Failure to provide confidentiality for stored data
Technical detail
CWE-218 · DEPRECATED: Failure to provide confidentiality for stored data
DEPRECATED: Failure to provide confidentiality for stored data
In plain English
DEPRECATED: Failure to provide confidentiality for stored data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
This weakness has been deprecated because it was a duplicate of CWE-493. All content has been transferred to CWE-493.
CWE-219 · Storage of File with Sensitive Data Under Web Root
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-219 · Storage of File with Sensitive Data Under Web Root
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.
CWE-220 · Storage of File With Sensitive Data Under FTP Root
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-220 · Storage of File With Sensitive Data Under FTP Root
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product stores sensitive data under the FTP server root with insufficient access control, which might make it accessible to untrusted parties.
CWE-221 · Information Loss or Omission
Information Loss or Omission
Technical detail
CWE-221 · Information Loss or Omission
Information Loss or Omission
In plain English
Information Loss or Omission
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis.
CWE-222 · Truncation of Security-relevant Information
Truncation of Security-relevant Information
Technical detail
CWE-222 · Truncation of Security-relevant Information
Truncation of Security-relevant Information
In plain English
Truncation of Security-relevant Information
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product truncates the display, recording, or processing of security-relevant information in a way that can obscure the source or nature of an attack.
CWE-223 · Omission of Security-relevant Information
Omission of Security-relevant Information
Technical detail
CWE-223 · Omission of Security-relevant Information
Omission of Security-relevant Information
In plain English
Omission of Security-relevant Information
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not record or display information that would be important for identifying the source or nature of an attack, or determining if an action is safe.
CWE-224 · Obscured Security-relevant Information by Alternate Name
Obscured Security-relevant Information by Alternate Name
Technical detail
CWE-224 · Obscured Security-relevant Information by Alternate Name
Obscured Security-relevant Information by Alternate Name
In plain English
Obscured Security-relevant Information by Alternate Name
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product records security-relevant information according to an alternate name of the affected entity, instead of the canonical name.
CWE-225 · DEPRECATED: General Information Management Problems
DEPRECATED: General Information Management Problems
Technical detail
CWE-225 · DEPRECATED: General Information Management Problems
DEPRECATED: General Information Management Problems
In plain English
DEPRECATED: General Information Management Problems
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
This weakness can be found at CWE-199.
CWE-226 · Sensitive Information in Resource Not Removed Before Reuse
The product handles memory in an unsafe way.
Important
CWE-226 · Sensitive Information in Resource Not Removed Before Reuse
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
CWE-228 · Improper Handling of Syntactically Invalid Structure
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-228 · Improper Handling of Syntactically Invalid Structure
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification.
CWE-229 · Improper Handling of Values
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-229 · Improper Handling of Values
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle when the expected number of values for parameters, fields, or arguments is not provided in input, or if those values are undefined.
CWE-230 · Improper Handling of Missing Values
Improper Handling of Missing Values
Technical detail
CWE-230 · Improper Handling of Missing Values
Improper Handling of Missing Values
In plain English
Improper Handling of Missing Values
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when a parameter, field, or argument name is specified, but the associated value is missing, i.e. it is empty, blank, or null.
CWE-231 · Improper Handling of Extra Values
Improper Handling of Extra Values
Technical detail
CWE-231 · Improper Handling of Extra Values
Improper Handling of Extra Values
In plain English
Improper Handling of Extra Values
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when more values are provided than expected.
CWE-232 · Improper Handling of Undefined Values
Improper Handling of Undefined Values
Technical detail
CWE-232 · Improper Handling of Undefined Values
Improper Handling of Undefined Values
In plain English
Improper Handling of Undefined Values
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name.
CWE-233 · Improper Handling of Parameters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-233 · Improper Handling of Parameters
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly handle when the expected number of parameters, fields, or arguments is not provided in input, or if those parameters are undefined.
CWE-234 · Failure to Handle Missing Parameter
Failure to Handle Missing Parameter
Technical detail
CWE-234 · Failure to Handle Missing Parameter
Failure to Handle Missing Parameter
In plain English
Failure to Handle Missing Parameter
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-235 · Improper Handling of Extra Parameters
Improper Handling of Extra Parameters
Technical detail
CWE-235 · Improper Handling of Extra Parameters
Improper Handling of Extra Parameters
In plain English
Improper Handling of Extra Parameters
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount.
CWE-236 · Improper Handling of Undefined Parameters
Improper Handling of Undefined Parameters
Technical detail
CWE-236 · Improper Handling of Undefined Parameters
Improper Handling of Undefined Parameters
In plain English
Improper Handling of Undefined Parameters
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product.
CWE-237 · Improper Handling of Structural Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-237 · Improper Handling of Structural Elements
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles inputs that are related to complex structures.
CWE-238 · Improper Handling of Incomplete Structural Elements
Improper Handling of Incomplete Structural Elements
Technical detail
CWE-238 · Improper Handling of Incomplete Structural Elements
Improper Handling of Incomplete Structural Elements
In plain English
Improper Handling of Incomplete Structural Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when a particular structural element is not completely specified.
CWE-239 · Failure to Handle Incomplete Element
Failure to Handle Incomplete Element
Technical detail
CWE-239 · Failure to Handle Incomplete Element
Failure to Handle Incomplete Element
In plain English
Failure to Handle Incomplete Element
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly handle when a particular element is not completely specified.
CWE-240 · Improper Handling of Inconsistent Structural Elements
Improper Handling of Inconsistent Structural Elements
Technical detail
CWE-240 · Improper Handling of Inconsistent Structural Elements
Improper Handling of Inconsistent Structural Elements
In plain English
Improper Handling of Inconsistent Structural Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when two or more structural elements should be consistent, but are not.
CWE-241 · Improper Handling of Unexpected Data Type
Improper Handling of Unexpected Data Type
Technical detail
CWE-241 · Improper Handling of Unexpected Data Type
Improper Handling of Unexpected Data Type
In plain English
Improper Handling of Unexpected Data Type
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when a particular element is not the expected type, e.g. it expects a digit (0-9) but is provided with a letter (A-Z).
CWE-242 · Use of Inherently Dangerous Function
Use of Inherently Dangerous Function
Technical detail
CWE-242 · Use of Inherently Dangerous Function
Use of Inherently Dangerous Function
In plain English
Use of Inherently Dangerous Function
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a function that can never be guaranteed to work safely.
CWE-243 · Creation of chroot Jail Without Changing Working Directory
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-243 · Creation of chroot Jail Without Changing Working Directory
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses the chroot() system call to create a jail, but does not change the working directory afterward. This does not prevent access to files outside of the jail.
CWE-244 · Improper Clearing of Heap Memory Before Release ('Heap Inspection')
The product handles memory in an unsafe way.
Important
CWE-244 · Improper Clearing of Heap Memory Before Release ('Heap Inspection')
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.
CWE-245 · J2EE Bad Practices: Direct Management of Connections
J2EE Bad Practices: Direct Management of Connections
Technical detail
CWE-245 · J2EE Bad Practices: Direct Management of Connections
J2EE Bad Practices: Direct Management of Connections
In plain English
J2EE Bad Practices: Direct Management of Connections
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The J2EE application directly manages connections, instead of using the container's connection management facilities.
CWE-246 · J2EE Bad Practices: Direct Use of Sockets
J2EE Bad Practices: Direct Use of Sockets
Technical detail
CWE-246 · J2EE Bad Practices: Direct Use of Sockets
J2EE Bad Practices: Direct Use of Sockets
In plain English
J2EE Bad Practices: Direct Use of Sockets
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The J2EE application directly uses sockets instead of using framework method calls.
CWE-247 · DEPRECATED: Reliance on DNS Lookups in a Security Decision
DEPRECATED: Reliance on DNS Lookups in a Security Decision
Technical detail
CWE-247 · DEPRECATED: Reliance on DNS Lookups in a Security Decision
DEPRECATED: Reliance on DNS Lookups in a Security Decision
In plain English
DEPRECATED: Reliance on DNS Lookups in a Security Decision
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.
CWE-248 · Uncaught Exception
Uncaught Exception
Technical detail
CWE-248 · Uncaught Exception
Uncaught Exception
In plain English
Uncaught Exception
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An exception is thrown from a function, but it is not caught.
CWE-249 · DEPRECATED: Often Misused: Path Manipulation
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-249 · DEPRECATED: Often Misused: Path Manipulation
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
This entry has been deprecated because of name confusion and an accidental combination of multiple weaknesses. Most of its content has been transferred to CWE-785.
CWE-250 · Execution with Unnecessary Privileges
Execution with Unnecessary Privileges
Technical detail
CWE-250 · Execution with Unnecessary Privileges
Execution with Unnecessary Privileges
In plain English
Execution with Unnecessary Privileges
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses.
CWE-252 · Unchecked Return Value
Unchecked Return Value
Technical detail
CWE-252 · Unchecked Return Value
Unchecked Return Value
In plain English
Unchecked Return Value
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.
CWE-253 · Incorrect Check of Function Return Value
Incorrect Check of Function Return Value
Technical detail
CWE-253 · Incorrect Check of Function Return Value
Incorrect Check of Function Return Value
In plain English
Incorrect Check of Function Return Value
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.
CWE-256 · Plaintext Storage of a Password
Passwords are stored without effective protection.
Headline signal
CWE-256 · Plaintext Storage of a Password
Passwords are stored without effective protection.
In plain English
Passwords are stored without effective protection.
What this can look like
Someone who obtains the application database or configuration file can read user passwords directly rather than having to crack protected password hashes.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product stores a password in plaintext within resources such as memory or files.
CWE-257 · Storing Passwords in a Recoverable Format
Passwords are protected in a way that allows them to be recovered.
Headline signal
CWE-257 · Storing Passwords in a Recoverable Format
Passwords are protected in a way that allows them to be recovered.
In plain English
Passwords are protected in a way that allows them to be recovered.
What this can look like
A stolen configuration database contains encrypted passwords together with everything needed to decrypt them, allowing the original passwords to be recovered.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-258 · Empty Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-258 · Empty Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
Using an empty string as a password is insecure.
CWE-259 · Use of Hard-coded Password
A password is embedded in the product or firmware.
Headline signal
CWE-259 · Use of Hard-coded Password
A password is embedded in the product or firmware.
In plain English
A password is embedded in the product or firmware.
What this can look like
Different installations ship with the same built-in password, so learning it from one device may provide access to many others.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.
CWE-260 · Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-260 · Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product stores a password in a configuration file that might be accessible to actors who do not know the password.
CWE-261 · Weak Encoding for Password
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-261 · Weak Encoding for Password
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
Obscuring a password with a trivial encoding does not protect the password.
CWE-262 · Not Using Password Aging
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-262 · Not Using Password Aging
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product does not have a mechanism in place for managing password aging.
CWE-263 · Password Aging with Long Expiration
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-263 · Password Aging with Long Expiration
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product supports password aging, but the expiration period is too long.
CWE-266 · Incorrect Privilege Assignment
Incorrect Privilege Assignment
Technical detail
CWE-266 · Incorrect Privilege Assignment
Incorrect Privilege Assignment
In plain English
Incorrect Privilege Assignment
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
CWE-267 · Privilege Defined With Unsafe Actions
Privilege Defined With Unsafe Actions
Technical detail
CWE-267 · Privilege Defined With Unsafe Actions
Privilege Defined With Unsafe Actions
In plain English
Privilege Defined With Unsafe Actions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-268 · Privilege Chaining
Privilege Chaining
Technical detail
CWE-268 · Privilege Chaining
Privilege Chaining
In plain English
Privilege Chaining
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-269 · Improper Privilege Management
Privileges are assigned, retained, or checked incorrectly.
Headline signal
CWE-269 · Improper Privilege Management
Privileges are assigned, retained, or checked incorrectly.
In plain English
Privileges are assigned, retained, or checked incorrectly.
What this can look like
A low-privileged account can reach an administrative operation because the application does not correctly separate ordinary and privileged capabilities.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
CWE-270 · Privilege Context Switching Error
Privilege Context Switching Error
Technical detail
CWE-270 · Privilege Context Switching Error
Privilege Context Switching Error
In plain English
Privilege Context Switching Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.
CWE-271 · Privilege Dropping / Lowering Errors
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-271 · Privilege Dropping / Lowering Errors
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not drop privileges before passing control of a resource to an actor that does not have those privileges.
CWE-272 · Least Privilege Violation
Least Privilege Violation
Technical detail
CWE-272 · Least Privilege Violation
Least Privilege Violation
In plain English
Least Privilege Violation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.
CWE-273 · Improper Check for Dropped Privileges
Improper Check for Dropped Privileges
Technical detail
CWE-273 · Improper Check for Dropped Privileges
Improper Check for Dropped Privileges
In plain English
Improper Check for Dropped Privileges
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.
CWE-274 · Improper Handling of Insufficient Privileges
Improper Handling of Insufficient Privileges
Technical detail
CWE-274 · Improper Handling of Insufficient Privileges
Improper Handling of Insufficient Privileges
In plain English
Improper Handling of Insufficient Privileges
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.
CWE-276 · Incorrect Default Permissions
Files, services, or resources start with permissions that are too broad.
Important
CWE-276 · Incorrect Default Permissions
Files, services, or resources start with permissions that are too broad.
In plain English
Files, services, or resources start with permissions that are too broad.
What this can look like
A newly installed service leaves a sensitive configuration readable or writable by users who should not have access.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
During installation, installed file permissions are set to allow anyone to modify those files.
CWE-277 · Insecure Inherited Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-277 · Insecure Inherited Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
A product defines a set of insecure permissions that are inherited by objects that are created by the program.
CWE-278 · Insecure Preserved Inherited Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-278 · Insecure Preserved Inherited Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement.
CWE-279 · Incorrect Execution-Assigned Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-279 · Incorrect Execution-Assigned Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.
CWE-280 · Improper Handling of Insufficient Permissions or Privileges
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-280 · Improper Handling of Insufficient Permissions or Privileges
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles when it has insufficient privileges to access resources or functionality as specified by their permissions. This may cause it to follow unexpected code paths that may leave the product in an invalid state.
CWE-281 · Improper Preservation of Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-281 · Improper Preservation of Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restrictive permissions than intended.
CWE-282 · Improper Ownership Management
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-282 · Improper Ownership Management
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.
CWE-283 · Unverified Ownership
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-283 · Unverified Ownership
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not properly verify that a critical resource is owned by the proper entity.
CWE-284 · Improper Access Control
The product does not correctly enforce who may access a resource or operation.
Headline signal
CWE-284 · Improper Access Control
The product does not correctly enforce who may access a resource or operation.
In plain English
The product does not correctly enforce who may access a resource or operation.
What this can look like
A user changes an identifier in a request and gains access to another user’s data or an administrative function.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-285 · Improper Authorization
The product authenticates a user but does not correctly verify permission for an action.
Headline signal
CWE-285 · Improper Authorization
The product authenticates a user but does not correctly verify permission for an action.
In plain English
The product authenticates a user but does not correctly verify permission for an action.
What this can look like
A normal authenticated account can call an administrative endpoint because the authorization check is missing or incorrect.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
CWE-286 · Incorrect User Management
Incorrect User Management
Technical detail
CWE-286 · Incorrect User Management
Incorrect User Management
In plain English
Incorrect User Management
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly manage a user within its environment.
CWE-287 · Improper Authentication
Identity verification can be bypassed or is performed incorrectly.
Headline signal
CWE-287 · Improper Authentication
Identity verification can be bypassed or is performed incorrectly.
In plain English
Identity verification can be bypassed or is performed incorrectly.
What this can look like
A protected interface accepts a request path or token state that lets an attacker reach authenticated functionality without proving who they are.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-288 · Authentication Bypass Using an Alternate Path or Channel
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
CWE-289 · Authentication Bypass by Alternate Name
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-289 · Authentication Bypass by Alternate Name
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.
CWE-290 · Authentication Bypass by Spoofing
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-290 · Authentication Bypass by Spoofing
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
CWE-291 · Reliance on IP Address for Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-291 · Reliance on IP Address for Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses an IP address for authentication.
CWE-292 · DEPRECATED: Trusting Self-reported DNS Name
DEPRECATED: Trusting Self-reported DNS Name
Technical detail
CWE-292 · DEPRECATED: Trusting Self-reported DNS Name
DEPRECATED: Trusting Self-reported DNS Name
In plain English
DEPRECATED: Trusting Self-reported DNS Name
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.
CWE-293 · Using Referer Field for Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-293 · Using Referer Field for Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The referer field in HTTP requests can be easily modified and, as such, is not a valid means of message integrity checking.
CWE-294 · Authentication Bypass by Capture-replay
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-294 · Authentication Bypass by Capture-replay
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
CWE-295 · Improper Certificate Validation
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-295 · Improper Certificate Validation
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product does not validate, or incorrectly validates, a certificate.
CWE-296 · Improper Following of a Certificate's Chain of Trust
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-296 · Improper Following of a Certificate's Chain of Trust
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate.
CWE-297 · Improper Validation of Certificate with Host Mismatch
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-297 · Improper Validation of Certificate with Host Mismatch
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product communicates with a host that provides a certificate, but the product does not properly ensure that the certificate is actually associated with that host.
CWE-298 · Improper Validation of Certificate Expiration
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-298 · Improper Validation of Certificate Expiration
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
A certificate expiration is not validated or is incorrectly validated.
CWE-299 · Improper Check for Certificate Revocation
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-299 · Improper Check for Certificate Revocation
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product does not check or incorrectly checks the revocation status of a certificate, which may cause it to use a certificate that has been compromised.
CWE-300 · Channel Accessible by Non-Endpoint
Channel Accessible by Non-Endpoint
Technical detail
CWE-300 · Channel Accessible by Non-Endpoint
Channel Accessible by Non-Endpoint
In plain English
Channel Accessible by Non-Endpoint
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-301 · Reflection Attack in an Authentication Protocol
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-301 · Reflection Attack in an Authentication Protocol
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
Simple authentication protocols are subject to reflection attacks if a malicious user can use the target machine to impersonate a trusted user.
CWE-302 · Authentication Bypass by Assumed-Immutable Data
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-302 · Authentication Bypass by Assumed-Immutable Data
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.
CWE-303 · Incorrect Implementation of Authentication Algorithm
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-303 · Incorrect Implementation of Authentication Algorithm
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.
CWE-304 · Missing Critical Step in Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-304 · Missing Critical Step in Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product implements an authentication technique, but it skips a step that weakens the technique.
CWE-305 · Authentication Bypass by Primary Weakness
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-305 · Authentication Bypass by Primary Weakness
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-306 · Missing Authentication for Critical Function
A critical function is reachable without requiring authentication.
Headline signal
CWE-306 · Missing Authentication for Critical Function
A critical function is reachable without requiring authentication.
In plain English
A critical function is reachable without requiring authentication.
What this can look like
A remote administration or configuration endpoint can be used by anyone who can reach it, without first logging in.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
CWE-307 · Improper Restriction of Excessive Authentication Attempts
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-307 · Improper Restriction of Excessive Authentication Attempts
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame.
CWE-308 · Use of Single-factor Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-308 · Use of Single-factor Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses an authentication algorithm that uses a single factor (e.g., a password) in a security context that should require more than one factor.
CWE-309 · Use of Password System for Primary Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-309 · Use of Password System for Primary Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-311 · Missing Encryption of Sensitive Data
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-311 · Missing Encryption of Sensitive Data
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product does not encrypt sensitive or critical information before storage or transmission.
CWE-312 · Cleartext Storage of Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-312 · Cleartext Storage of Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
CWE-313 · Cleartext Storage in a File or on Disk
The product can expose information beyond the audience that should receive it.
Important
CWE-313 · Cleartext Storage in a File or on Disk
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product stores sensitive information in cleartext in a file, or on disk.
CWE-314 · Cleartext Storage in the Registry
The product can expose information beyond the audience that should receive it.
Important
CWE-314 · Cleartext Storage in the Registry
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product stores sensitive information in cleartext in the registry.
CWE-315 · Cleartext Storage of Sensitive Information in a Cookie
The product can expose information beyond the audience that should receive it.
Important
CWE-315 · Cleartext Storage of Sensitive Information in a Cookie
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product stores sensitive information in cleartext in a cookie.
CWE-316 · Cleartext Storage of Sensitive Information in Memory
The product handles memory in an unsafe way.
Important
CWE-316 · Cleartext Storage of Sensitive Information in Memory
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product stores sensitive information in cleartext in memory.
CWE-317 · Cleartext Storage of Sensitive Information in GUI
The product can expose information beyond the audience that should receive it.
Important
CWE-317 · Cleartext Storage of Sensitive Information in GUI
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product stores sensitive information in cleartext within the GUI.
CWE-318 · Cleartext Storage of Sensitive Information in Executable
The product can expose information beyond the audience that should receive it.
Important
CWE-318 · Cleartext Storage of Sensitive Information in Executable
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product stores sensitive information in cleartext in an executable.
CWE-319 · Cleartext Transmission of Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-319 · Cleartext Transmission of Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
CWE-321 · Use of Hard-coded Cryptographic Key
A cryptographic key is built into the product.
Headline signal
CWE-321 · Use of Hard-coded Cryptographic Key
A cryptographic key is built into the product.
In plain English
A cryptographic key is built into the product.
What this can look like
Extracting the key from one firmware image can allow protected traffic or stored data from other installations using the same key to be decrypted or forged.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses a hard-coded, unchangeable cryptographic key.
CWE-322 · Key Exchange without Entity Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-322 · Key Exchange without Entity Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product performs a key exchange with an actor without verifying the identity of that actor.
CWE-323 · Reusing a Nonce, Key Pair in Encryption
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-323 · Reusing a Nonce, Key Pair in Encryption
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
Nonces should be used for the present occasion and only once.
CWE-324 · Use of a Key Past its Expiration Date
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-324 · Use of a Key Past its Expiration Date
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-325 · Missing Cryptographic Step
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-325 · Missing Cryptographic Step
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.
CWE-326 · Inadequate Encryption Strength
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-326 · Inadequate Encryption Strength
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
CWE-327 · Use of a Broken or Risky Cryptographic Algorithm
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-327 · Use of a Broken or Risky Cryptographic Algorithm
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses a broken or risky cryptographic algorithm or protocol.
CWE-328 · Use of Weak Hash
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-328 · Use of Weak Hash
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses an algorithm that produces a digest (output value) that does not meet security expectations for a hash function that allows an adversary to reasonably determine the original input (preimage attack), find another input that can produce the same hash (2nd preimage attack), or find multiple inputs that evaluate to the same hash (birthday attack).
CWE-329 · Generation of Predictable IV with CBC Mode
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-329 · Generation of Predictable IV with CBC Mode
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product generates and uses a predictable initialization Vector (IV) with Cipher Block Chaining (CBC) Mode, which causes algorithms to be susceptible to dictionary attacks when they are encrypted under the same key.
CWE-330 · Use of Insufficiently Random Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-330 · Use of Insufficiently Random Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
CWE-331 · Insufficient Entropy
Insufficient Entropy
Technical detail
CWE-331 · Insufficient Entropy
Insufficient Entropy
In plain English
Insufficient Entropy
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.
CWE-332 · Insufficient Entropy in PRNG
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-332 · Insufficient Entropy in PRNG
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat.
CWE-333 · Improper Handling of Insufficient Entropy in TRNG
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-333 · Improper Handling of Insufficient Entropy in TRNG
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
True random number generators (TRNG) generally have a limited source of entropy and therefore can fail or block.
CWE-334 · Small Space of Random Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-334 · Small Space of Random Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The number of possible random values is smaller than needed by the product, making it more susceptible to brute force attacks.
CWE-335 · Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-335 · Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.
CWE-336 · Same Seed in Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-336 · Same Seed in Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
A Pseudo-Random Number Generator (PRNG) uses the same seed each time the product is initialized.
CWE-337 · Predictable Seed in Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-337 · Predictable Seed in Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.
CWE-338 · Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-338 · Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.
CWE-339 · Small Seed Space in PRNG
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-339 · Small Seed Space in PRNG
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
A Pseudo-Random Number Generator (PRNG) uses a relatively small seed space, which makes it more susceptible to brute force attacks.
CWE-340 · Generation of Predictable Numbers or Identifiers
Generation of Predictable Numbers or Identifiers
Technical detail
CWE-340 · Generation of Predictable Numbers or Identifiers
Generation of Predictable Numbers or Identifiers
In plain English
Generation of Predictable Numbers or Identifiers
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a scheme that generates numbers or identifiers that are more predictable than required.
CWE-341 · Predictable from Observable State
Predictable from Observable State
Technical detail
CWE-341 · Predictable from Observable State
Predictable from Observable State
In plain English
Predictable from Observable State
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-342 · Predictable Exact Value from Previous Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-342 · Predictable Exact Value from Previous Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
An exact value or random number can be precisely predicted by observing previous values.
CWE-343 · Predictable Value Range from Previous Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-343 · Predictable Value Range from Previous Values
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product's random number generator produces a series of values which, when observed, can be used to infer a relatively small range of possibilities for the next value that could be generated.
CWE-344 · Use of Invariant Value in Dynamically Changing Context
Use of Invariant Value in Dynamically Changing Context
Technical detail
CWE-344 · Use of Invariant Value in Dynamically Changing Context
Use of Invariant Value in Dynamically Changing Context
In plain English
Use of Invariant Value in Dynamically Changing Context
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a constant value, name, or reference, but this value can (or should) vary across different environments.
CWE-345 · Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity
Technical detail
CWE-345 · Insufficient Verification of Data Authenticity
Insufficient Verification of Data Authenticity
In plain English
Insufficient Verification of Data Authenticity
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.
CWE-346 · Origin Validation Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-346 · Origin Validation Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not properly verify that the source of data or communication is valid.
CWE-347 · Improper Verification of Cryptographic Signature
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-347 · Improper Verification of Cryptographic Signature
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
CWE-348 · Use of Less Trusted Source
Use of Less Trusted Source
Technical detail
CWE-348 · Use of Less Trusted Source
Use of Less Trusted Source
In plain English
Use of Less Trusted Source
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has two different sources of the same data or information, but it uses the source that has less support for verification, is less trusted, or is less resistant to attack.
CWE-349 · Acceptance of Extraneous Untrusted Data With Trusted Data
Acceptance of Extraneous Untrusted Data With Trusted Data
Technical detail
CWE-349 · Acceptance of Extraneous Untrusted Data With Trusted Data
Acceptance of Extraneous Untrusted Data With Trusted Data
In plain English
Acceptance of Extraneous Untrusted Data With Trusted Data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.
CWE-350 · Reliance on Reverse DNS Resolution for a Security-Critical Action
Reliance on Reverse DNS Resolution for a Security-Critical Action
Technical detail
CWE-350 · Reliance on Reverse DNS Resolution for a Security-Critical Action
Reliance on Reverse DNS Resolution for a Security-Critical Action
In plain English
Reliance on Reverse DNS Resolution for a Security-Critical Action
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs reverse DNS resolution on an IP address to obtain the hostname and make a security decision, but it does not properly ensure that the IP address is truly associated with the hostname.
CWE-351 · Insufficient Type Distinction
Insufficient Type Distinction
Technical detail
CWE-351 · Insufficient Type Distinction
Insufficient Type Distinction
In plain English
Insufficient Type Distinction
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.
CWE-352 · Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF)
Technical detail
CWE-352 · Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF)
In plain English
Cross-Site Request Forgery (CSRF)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
CWE-353 · Missing Support for Integrity Check
Missing Support for Integrity Check
Technical detail
CWE-353 · Missing Support for Integrity Check
Missing Support for Integrity Check
In plain English
Missing Support for Integrity Check
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
CWE-354 · Improper Validation of Integrity Check Value
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-354 · Improper Validation of Integrity Check Value
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
CWE-356 · Product UI does not Warn User of Unsafe Actions
Product UI does not Warn User of Unsafe Actions
Technical detail
CWE-356 · Product UI does not Warn User of Unsafe Actions
Product UI does not Warn User of Unsafe Actions
In plain English
Product UI does not Warn User of Unsafe Actions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product's user interface does not warn the user before undertaking an unsafe action on behalf of that user. This makes it easier for attackers to trick users into inflicting damage to their system.
CWE-357 · Insufficient UI Warning of Dangerous Operations
Insufficient UI Warning of Dangerous Operations
Technical detail
CWE-357 · Insufficient UI Warning of Dangerous Operations
Insufficient UI Warning of Dangerous Operations
In plain English
Insufficient UI Warning of Dangerous Operations
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention.
CWE-358 · Improperly Implemented Security Check for Standard
Improperly Implemented Security Check for Standard
Technical detail
CWE-358 · Improperly Implemented Security Check for Standard
Improperly Implemented Security Check for Standard
In plain English
Improperly Implemented Security Check for Standard
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
CWE-359 · Exposure of Private Personal Information to an Unauthorized Actor
Exposure of Private Personal Information to an Unauthorized Actor
Technical detail
CWE-359 · Exposure of Private Personal Information to an Unauthorized Actor
Exposure of Private Personal Information to an Unauthorized Actor
In plain English
Exposure of Private Personal Information to an Unauthorized Actor
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-360 · Trust of System Event Data
Trust of System Event Data
Technical detail
CWE-360 · Trust of System Event Data
Trust of System Event Data
In plain English
Trust of System Event Data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Security based on event locations are insecure and can be spoofed.
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-362 · Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product contains a concurrent code sequence that 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 operating concurrently.
CWE-363 · Race Condition Enabling Link Following
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-363 · Race Condition Enabling Link Following
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product checks the status of a file or directory before accessing it, which produces a race condition in which the file can be replaced with a link before the access is performed, causing the product to access the wrong file.
CWE-364 · Signal Handler Race Condition
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-364 · Signal Handler Race Condition
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
The product uses a signal handler that introduces a race condition.
CWE-365 · DEPRECATED: Race Condition in Switch
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-365 · DEPRECATED: Race Condition in Switch
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
This entry has been deprecated. There are no documented cases in which a switch's control expression is evaluated more than once.
CWE-366 · Race Condition within a Thread
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-366 · Race Condition within a Thread
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
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.
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-367 · Time-of-check Time-of-use (TOCTOU) Race Condition
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
CWE-368 · Context Switching Race Condition
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-368 · Context Switching Race Condition
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-369 · Divide By Zero
Divide By Zero
Technical detail
CWE-369 · Divide By Zero
Divide By Zero
In plain English
Divide By Zero
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product divides a value by zero.
CWE-370 · Missing Check for Certificate Revocation after Initial Check
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-370 · Missing Check for Certificate Revocation after Initial Check
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not check the revocation status of a certificate after its initial revocation check, which can cause the product to perform privileged actions even after the certificate is revoked at a later time.
CWE-372 · Incomplete Internal State Distinction
Incomplete Internal State Distinction
Technical detail
CWE-372 · Incomplete Internal State Distinction
Incomplete Internal State Distinction
In plain English
Incomplete Internal State Distinction
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly determine which state it is in, causing it to assume it is in state X when in fact it is in state Y, causing it to perform incorrect operations in a security-relevant manner.
CWE-373 · DEPRECATED: State Synchronization Error
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-373 · DEPRECATED: State Synchronization Error
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
This entry was deprecated because it overlapped the same concepts as race condition (CWE-362) and Improper Synchronization (CWE-662).
CWE-374 · Passing Mutable Objects to an Untrusted Method
Passing Mutable Objects to an Untrusted Method
Technical detail
CWE-374 · Passing Mutable Objects to an Untrusted Method
Passing Mutable Objects to an Untrusted Method
In plain English
Passing Mutable Objects to an Untrusted Method
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product sends non-cloned mutable data as an argument to a method or function.
CWE-375 · Returning a Mutable Object to an Untrusted Caller
Returning a Mutable Object to an Untrusted Caller
Technical detail
CWE-375 · Returning a Mutable Object to an Untrusted Caller
Returning a Mutable Object to an Untrusted Caller
In plain English
Returning a Mutable Object to an Untrusted Caller
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function.
CWE-377 · Insecure Temporary File
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-377 · Insecure Temporary File
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
Creating and using insecure temporary files can leave application and system data vulnerable to attack.
CWE-378 · Creation of Temporary File With Insecure Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-378 · Creation of Temporary File With Insecure Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.
CWE-379 · Creation of Temporary File in Directory with Insecure Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-379 · Creation of Temporary File in Directory with Insecure Permissions
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product creates a temporary file in a directory whose permissions allow unintended actors to determine the file's existence or otherwise access that file.
CWE-382 · J2EE Bad Practices: Use of System.exit()
J2EE Bad Practices: Use of System.exit()
Technical detail
CWE-382 · J2EE Bad Practices: Use of System.exit()
J2EE Bad Practices: Use of System.exit()
In plain English
J2EE Bad Practices: Use of System.exit()
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A J2EE application uses System.exit(), which also shuts down its container.
CWE-383 · J2EE Bad Practices: Direct Use of Threads
J2EE Bad Practices: Direct Use of Threads
Technical detail
CWE-383 · J2EE Bad Practices: Direct Use of Threads
J2EE Bad Practices: Direct Use of Threads
In plain English
J2EE Bad Practices: Direct Use of Threads
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Thread management in a Web application is forbidden in some circumstances and is always highly error prone.
CWE-384 · Session Fixation
Session Fixation
Technical detail
CWE-384 · Session Fixation
Session Fixation
In plain English
Session Fixation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-385 · Covert Timing Channel
Covert Timing Channel
Technical detail
CWE-385 · Covert Timing Channel
Covert Timing Channel
In plain English
Covert Timing Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
An undocumented account, command, trigger, or communication path provides capabilities that are absent from the normal product interface.
A component appears to perform a legitimate function while secretly collecting information, bypassing controls, or activating hidden behavior.
MITRE description from the synchronized CWE record
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.
CWE-386 · Symbolic Name not Mapping to Correct Object
Symbolic Name not Mapping to Correct Object
Technical detail
CWE-386 · Symbolic Name not Mapping to Correct Object
Symbolic Name not Mapping to Correct Object
In plain English
Symbolic Name not Mapping to Correct Object
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.
CWE-390 · Detection of Error Condition Without Action
Detection of Error Condition Without Action
Technical detail
CWE-390 · Detection of Error Condition Without Action
Detection of Error Condition Without Action
In plain English
Detection of Error Condition Without Action
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product detects a specific error, but takes no actions to handle the error.
CWE-391 · Unchecked Error Condition
Unchecked Error Condition
Technical detail
CWE-391 · Unchecked Error Condition
Unchecked Error Condition
In plain English
Unchecked Error Condition
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
[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.
CWE-392 · Missing Report of Error Condition
Missing Report of Error Condition
Technical detail
CWE-392 · Missing Report of Error Condition
Missing Report of Error Condition
In plain English
Missing Report of Error Condition
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product encounters an error but does not provide a status code or return value to indicate that an error has occurred.
CWE-393 · Return of Wrong Status Code
Return of Wrong Status Code
Technical detail
CWE-393 · Return of Wrong Status Code
Return of Wrong Status Code
In plain English
Return of Wrong Status Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A function or operation returns an incorrect return value or status code that does not indicate the true result of execution, causing the product to modify its behavior based on the incorrect result.
CWE-394 · Unexpected Status Code or Return Value
Unexpected Status Code or Return Value
Technical detail
CWE-394 · Unexpected Status Code or Return Value
Unexpected Status Code or Return Value
In plain English
Unexpected Status Code or Return Value
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product.
CWE-395 · Use of NullPointerException Catch to Detect NULL Pointer Dereference
The product handles memory in an unsafe way.
Important
CWE-395 · Use of NullPointerException Catch to Detect NULL Pointer Dereference
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
Catching NullPointerException should not be used as an alternative to programmatic checks to prevent dereferencing a null pointer.
CWE-396 · Declaration of Catch for Generic Exception
Declaration of Catch for Generic Exception
Technical detail
CWE-396 · Declaration of Catch for Generic Exception
Declaration of Catch for Generic Exception
In plain English
Declaration of Catch for Generic Exception
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.
CWE-397 · Declaration of Throws for Generic Exception
Declaration of Throws for Generic Exception
Technical detail
CWE-397 · Declaration of Throws for Generic Exception
Declaration of Throws for Generic Exception
In plain English
Declaration of Throws for Generic Exception
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product throws or raises an overly broad exceptions that can hide important details and produce inappropriate responses to certain conditions.
CWE-400 · Uncontrolled Resource Consumption
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-400 · Uncontrolled Resource Consumption
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not properly control the allocation and maintenance of a limited resource.
CWE-401 · Missing Release of Memory after Effective Lifetime
The product handles memory in an unsafe way.
Important
CWE-401 · Missing Release of Memory after Effective Lifetime
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
CWE-402 · Transmission of Private Resources into a New Sphere ('Resource Leak')
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-402 · Transmission of Private Resources into a New Sphere ('Resource Leak')
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product.
CWE-403 · Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak')
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-403 · Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak')
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-404 · Improper Resource Shutdown or Release
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-404 · Improper Resource Shutdown or Release
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not release or incorrectly releases a resource before it is made available for re-use.
CWE-405 · Asymmetric Resource Consumption (Amplification)
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-405 · Asymmetric Resource Consumption (Amplification)
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
CWE-406 · Insufficient Control of Network Message Volume (Network Amplification)
Insufficient Control of Network Message Volume (Network Amplification)
Technical detail
CWE-406 · Insufficient Control of Network Message Volume (Network Amplification)
Insufficient Control of Network Message Volume (Network Amplification)
In plain English
Insufficient Control of Network Message Volume (Network Amplification)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the product to transmit more traffic than should be allowed for that actor.
CWE-407 · Inefficient Algorithmic Complexity
Inefficient Algorithmic Complexity
Technical detail
CWE-407 · Inefficient Algorithmic Complexity
Inefficient Algorithmic Complexity
In plain English
Inefficient Algorithmic Complexity
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-408 · Incorrect Behavior Order: Early Amplification
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-408 · Incorrect Behavior Order: Early Amplification
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place.
CWE-409 · Improper Handling of Highly Compressed Data (Data Amplification)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-409 · Improper Handling of Highly Compressed Data (Data Amplification)
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.
CWE-410 · Insufficient Resource Pool
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-410 · Insufficient Resource Pool
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product's resource pool is not large enough to handle peak demand, which allows an attacker to prevent others from accessing the resource by using a (relatively) large number of requests for resources.
CWE-412 · Unrestricted Externally Accessible Lock
Unrestricted Externally Accessible Lock
Technical detail
CWE-412 · Unrestricted Externally Accessible Lock
Unrestricted Externally Accessible Lock
In plain English
Unrestricted Externally Accessible Lock
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control.
CWE-413 · Improper Resource Locking
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-413 · Improper Resource Locking
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.
CWE-414 · Missing Lock Check
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-414 · Missing Lock Check
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
A product does not check to see if a lock is present before performing sensitive operations on a resource.
CWE-415 · Double Free
The product handles memory in an unsafe way.
Important
CWE-415 · Double Free
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product calls free() twice on the same memory address.
CWE-416 · Use After Free
Software continues using memory after that memory has been released.
Headline signal
CWE-416 · Use After Free
Software continues using memory after that memory has been released.
In plain English
Software continues using memory after that memory has been released.
What this can look like
Carefully timed input causes the program to reuse freed memory in an unsafe way, which may crash the process or, in severe cases, enable code execution.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
CWE-419 · Unprotected Primary Channel
Unprotected Primary Channel
Technical detail
CWE-419 · Unprotected Primary Channel
Unprotected Primary Channel
In plain English
Unprotected Primary Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a primary channel for administration or restricted functionality, but it does not properly protect the channel.
CWE-420 · Unprotected Alternate Channel
Unprotected Alternate Channel
Technical detail
CWE-420 · Unprotected Alternate Channel
Unprotected Alternate Channel
In plain English
Unprotected Alternate Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product protects a primary channel, but it does not use the same level of protection for an alternate channel.
CWE-421 · Race Condition During Access to Alternate Channel
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-421 · Race Condition During Access to Alternate Channel
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors.
CWE-422 · Unprotected Windows Messaging Channel ('Shatter')
Unprotected Windows Messaging Channel ('Shatter')
Technical detail
CWE-422 · Unprotected Windows Messaging Channel ('Shatter')
Unprotected Windows Messaging Channel ('Shatter')
In plain English
Unprotected Windows Messaging Channel ('Shatter')
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not properly verify the source of a message in the Windows Messaging System while running at elevated privileges, creating an alternate channel through which an attacker can directly send a message to the product.
CWE-423 · DEPRECATED: Proxied Trusted Channel
DEPRECATED: Proxied Trusted Channel
Technical detail
CWE-423 · DEPRECATED: Proxied Trusted Channel
DEPRECATED: Proxied Trusted Channel
In plain English
DEPRECATED: Proxied Trusted Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
This entry has been deprecated because it was a duplicate of CWE-441. All content has been transferred to CWE-441.
CWE-424 · Improper Protection of Alternate Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-424 · Improper Protection of Alternate Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources.
CWE-425 · Direct Request ('Forced Browsing')
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-425 · Direct Request ('Forced Browsing')
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
CWE-426 · Untrusted Search Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-426 · Untrusted Search Path
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.
CWE-427 · Uncontrolled Search Path Element
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-427 · Uncontrolled Search Path Element
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-428 · Unquoted Search Path or Element
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-428 · Unquoted Search Path or Element
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-430 · Deployment of Wrong Handler
Deployment of Wrong Handler
Technical detail
CWE-430 · Deployment of Wrong Handler
Deployment of Wrong Handler
In plain English
Deployment of Wrong Handler
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The wrong "handler" is assigned to process an object.
CWE-431 · Missing Handler
Missing Handler
Technical detail
CWE-431 · Missing Handler
Missing Handler
In plain English
Missing Handler
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A handler is not available or implemented.
CWE-432 · Dangerous Signal Handler not Disabled During Sensitive Operations
Dangerous Signal Handler not Disabled During Sensitive Operations
Technical detail
CWE-432 · Dangerous Signal Handler not Disabled During Sensitive Operations
Dangerous Signal Handler not Disabled During Sensitive Operations
In plain English
Dangerous Signal Handler not Disabled During Sensitive Operations
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a signal handler that shares state with other signal handlers, but it does not properly mask or prevent those signal handlers from being invoked while the original signal handler is still running.
CWE-433 · Unparsed Raw Web Content Delivery
Unparsed Raw Web Content Delivery
Technical detail
CWE-433 · Unparsed Raw Web Content Delivery
Unparsed Raw Web Content Delivery
In plain English
Unparsed Raw Web Content Delivery
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.
CWE-434 · Unrestricted Upload of File with Dangerous Type
The product accepts files without sufficiently constraining what can be uploaded or where they are used.
Headline signal
CWE-434 · Unrestricted Upload of File with Dangerous Type
The product accepts files without sufficiently constraining what can be uploaded or where they are used.
In plain English
The product accepts files without sufficiently constraining what can be uploaded or where they are used.
What this can look like
A web interface intended for images accepts an executable server-side file that is later processed as code.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
CWE-435 · Improper Interaction Between Multiple Correctly-Behaving Entities
Improper Interaction Between Multiple Correctly-Behaving Entities
Technical detail
CWE-435 · Improper Interaction Between Multiple Correctly-Behaving Entities
Improper Interaction Between Multiple Correctly-Behaving Entities
In plain English
Improper Interaction Between Multiple Correctly-Behaving Entities
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-436 · Interpretation Conflict
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-436 · Interpretation Conflict
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-437 · Incomplete Model of Endpoint Features
Incomplete Model of Endpoint Features
Technical detail
CWE-437 · Incomplete Model of Endpoint Features
Incomplete Model of Endpoint Features
In plain English
Incomplete Model of Endpoint Features
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-439 · Behavioral Change in New Version or Environment
Behavioral Change in New Version or Environment
Technical detail
CWE-439 · Behavioral Change in New Version or Environment
Behavioral Change in New Version or Environment
In plain English
Behavioral Change in New Version or Environment
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A's behavior or functionality changes with a new version of A, or a new environment, which is not known (or manageable) by B.
CWE-440 · Expected Behavior Violation
Expected Behavior Violation
Technical detail
CWE-440 · Expected Behavior Violation
Expected Behavior Violation
In plain English
Expected Behavior Violation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A feature, API, or function does not perform according to its specification.
CWE-441 · Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy')
Technical detail
CWE-441 · Unintended Proxy or Intermediary ('Confused Deputy')
Unintended Proxy or Intermediary ('Confused Deputy')
In plain English
Unintended Proxy or Intermediary ('Confused Deputy')
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-443 · DEPRECATED: HTTP response splitting
DEPRECATED: HTTP response splitting
Technical detail
CWE-443 · DEPRECATED: HTTP response splitting
DEPRECATED: HTTP response splitting
In plain English
DEPRECATED: HTTP response splitting
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
This weakness can be found at CWE-113.
CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Technical detail
CWE-444 · Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
In plain English
Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product acts as an intermediary HTTP agent (such as a proxy or firewall) in the data flow between two entities such as a client and server, but it does not interpret malformed HTTP requests or responses in ways that are consistent with how the messages will be processed by those entities that are at the ultimate destination.
CWE-446 · UI Discrepancy for Security Feature
UI Discrepancy for Security Feature
Technical detail
CWE-446 · UI Discrepancy for Security Feature
UI Discrepancy for Security Feature
In plain English
UI Discrepancy for Security Feature
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-447 · Unimplemented or Unsupported Feature in UI
Unimplemented or Unsupported Feature in UI
Technical detail
CWE-447 · Unimplemented or Unsupported Feature in UI
Unimplemented or Unsupported Feature in UI
In plain English
Unimplemented or Unsupported Feature in UI
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-448 · Obsolete Feature in UI
Obsolete Feature in UI
Technical detail
CWE-448 · Obsolete Feature in UI
Obsolete Feature in UI
In plain English
Obsolete Feature in UI
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A UI function is obsolete and the product does not warn the user.
CWE-449 · The UI Performs the Wrong Action
The UI Performs the Wrong Action
Technical detail
CWE-449 · The UI Performs the Wrong Action
The UI Performs the Wrong Action
In plain English
The UI Performs the Wrong Action
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The UI performs the wrong action with respect to the user's request.
CWE-450 · Multiple Interpretations of UI Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-450 · Multiple Interpretations of UI Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The UI has multiple interpretations of user input but does not prompt the user when it selects the less secure interpretation.
CWE-451 · User Interface (UI) Misrepresentation of Critical Information
User Interface (UI) Misrepresentation of Critical Information
Technical detail
CWE-451 · User Interface (UI) Misrepresentation of Critical Information
User Interface (UI) Misrepresentation of Critical Information
In plain English
User Interface (UI) Misrepresentation of Critical Information
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-453 · Insecure Default Variable Initialization
Insecure Default Variable Initialization
Technical detail
CWE-453 · Insecure Default Variable Initialization
Insecure Default Variable Initialization
In plain English
Insecure Default Variable Initialization
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product, by default, initializes an internal variable with an insecure or less secure value than is possible.
CWE-454 · External Initialization of Trusted Variables or Data Stores
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-454 · External Initialization of Trusted Variables or Data Stores
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.
CWE-455 · Non-exit on Failed Initialization
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-455 · Non-exit on Failed Initialization
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product does not exit or otherwise modify its operation when security-relevant errors occur during initialization, such as when a configuration file has a format error or a hardware security module (HSM) cannot be activated, which can cause the product to execute in a less secure fashion than intended by the administrator.
CWE-456 · Missing Initialization of a Variable
Missing Initialization of a Variable
Technical detail
CWE-456 · Missing Initialization of a Variable
Missing Initialization of a Variable
In plain English
Missing Initialization of a Variable
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not initialize critical variables, which causes the execution environment to use unexpected values.
CWE-457 · Use of Uninitialized Variable
Use of Uninitialized Variable
Technical detail
CWE-457 · Use of Uninitialized Variable
Use of Uninitialized Variable
In plain English
Use of Uninitialized Variable
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
CWE-458 · DEPRECATED: Incorrect Initialization
DEPRECATED: Incorrect Initialization
Technical detail
CWE-458 · DEPRECATED: Incorrect Initialization
DEPRECATED: Incorrect Initialization
In plain English
DEPRECATED: Incorrect Initialization
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-459 · Incomplete Cleanup
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-459 · Incomplete Cleanup
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not properly "clean up" and remove temporary or supporting resources after they have been used.
CWE-460 · Improper Cleanup on Thrown Exception
Improper Cleanup on Thrown Exception
Technical detail
CWE-460 · Improper Cleanup on Thrown Exception
Improper Cleanup on Thrown Exception
In plain English
Improper Cleanup on Thrown Exception
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-462 · Duplicate Key in Associative List (Alist)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-462 · Duplicate Key in Associative List (Alist)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.
CWE-463 · Deletion of Data Structure Sentinel
Deletion of Data Structure Sentinel
Technical detail
CWE-463 · Deletion of Data Structure Sentinel
Deletion of Data Structure Sentinel
In plain English
Deletion of Data Structure Sentinel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The accidental deletion of a data-structure sentinel can cause serious programming logic problems.
CWE-464 · Addition of Data Structure Sentinel
Addition of Data Structure Sentinel
Technical detail
CWE-464 · Addition of Data Structure Sentinel
Addition of Data Structure Sentinel
In plain English
Addition of Data Structure Sentinel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The accidental addition of a data-structure sentinel can cause serious programming logic problems.
CWE-466 · Return of Pointer Value Outside of Expected Range
The product handles memory in an unsafe way.
Important
CWE-466 · Return of Pointer Value Outside of Expected Range
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.
CWE-467 · Use of sizeof() on a Pointer Type
The product handles memory in an unsafe way.
Important
CWE-467 · Use of sizeof() on a Pointer Type
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The code calls sizeof() on a pointer type, which can be an incorrect calculation if the programmer intended to determine the size of the data that is being pointed to.
CWE-468 · Incorrect Pointer Scaling
The product handles memory in an unsafe way.
Important
CWE-468 · Incorrect Pointer Scaling
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled.
CWE-469 · Use of Pointer Subtraction to Determine Size
The product handles memory in an unsafe way.
Important
CWE-469 · Use of Pointer Subtraction to Determine Size
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product subtracts one pointer from another in order to determine size, but this calculation can be incorrect if the pointers do not exist in the same memory chunk.
CWE-470 · Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-470 · Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses external input with reflection to select which classes or code to use, but it does not sufficiently prevent the input from selecting improper classes or code.
CWE-471 · Modification of Assumed-Immutable Data (MAID)
Modification of Assumed-Immutable Data (MAID)
Technical detail
CWE-471 · Modification of Assumed-Immutable Data (MAID)
Modification of Assumed-Immutable Data (MAID)
In plain English
Modification of Assumed-Immutable Data (MAID)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly protect an assumed-immutable element from being modified by an attacker.
CWE-472 · External Control of Assumed-Immutable Web Parameter
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-472 · External Control of Assumed-Immutable Web Parameter
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.
CWE-473 · PHP External Variable Modification
PHP External Variable Modification
Technical detail
CWE-473 · PHP External Variable Modification
PHP External Variable Modification
In plain English
PHP External Variable Modification
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-474 · Use of Function with Inconsistent Implementations
Use of Function with Inconsistent Implementations
Technical detail
CWE-474 · Use of Function with Inconsistent Implementations
Use of Function with Inconsistent Implementations
In plain English
Use of Function with Inconsistent Implementations
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses a function that has inconsistent implementations across operating systems and versions.
CWE-475 · Undefined Behavior for Input to API
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-475 · Undefined Behavior for Input to API
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The behavior of this function is undefined unless its control parameter is set to a specific value.
CWE-476 · NULL Pointer Dereference
The product handles memory in an unsafe way.
Important
CWE-476 · NULL Pointer Dereference
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product dereferences a pointer that it expects to be valid but is NULL.
CWE-477 · Use of Obsolete Function
Use of Obsolete Function
Technical detail
CWE-477 · Use of Obsolete Function
Use of Obsolete Function
In plain English
Use of Obsolete Function
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.
CWE-478 · Missing Default Case in Multiple Condition Expression
Missing Default Case in Multiple Condition Expression
Technical detail
CWE-478 · Missing Default Case in Multiple Condition Expression
Missing Default Case in Multiple Condition Expression
In plain English
Missing Default Case in Multiple Condition Expression
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code does not have a default case in an expression with multiple conditions, such as a switch statement.
CWE-479 · Signal Handler Use of a Non-reentrant Function
Signal Handler Use of a Non-reentrant Function
Technical detail
CWE-479 · Signal Handler Use of a Non-reentrant Function
Signal Handler Use of a Non-reentrant Function
In plain English
Signal Handler Use of a Non-reentrant Function
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product defines a signal handler that calls a non-reentrant function.
CWE-480 · Use of Incorrect Operator
Use of Incorrect Operator
Technical detail
CWE-480 · Use of Incorrect Operator
Use of Incorrect Operator
In plain English
Use of Incorrect Operator
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product accidentally uses the wrong operator, which changes the logic in security-relevant ways.
CWE-481 · Assigning instead of Comparing
Assigning instead of Comparing
Technical detail
CWE-481 · Assigning instead of Comparing
Assigning instead of Comparing
In plain English
Assigning instead of Comparing
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses an operator for assignment when the intention was to perform a comparison.
CWE-482 · Comparing instead of Assigning
Comparing instead of Assigning
Technical detail
CWE-482 · Comparing instead of Assigning
Comparing instead of Assigning
In plain English
Comparing instead of Assigning
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses an operator for comparison when the intention was to perform an assignment.
CWE-483 · Incorrect Block Delimitation
Incorrect Block Delimitation
Technical detail
CWE-483 · Incorrect Block Delimitation
Incorrect Block Delimitation
In plain English
Incorrect Block Delimitation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code does not explicitly delimit a block that is intended to contain 2 or more statements, creating a logic error.
CWE-484 · Omitted Break Statement in Switch
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-484 · Omitted Break Statement in Switch
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product omits a break statement within a switch or similar construct, causing code associated with multiple conditions to execute. This can cause problems when the programmer only intended to execute code associated with one condition.
CWE-486 · Comparison of Classes by Name
Comparison of Classes by Name
Technical detail
CWE-486 · Comparison of Classes by Name
Comparison of Classes by Name
In plain English
Comparison of Classes by Name
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name.
CWE-487 · Reliance on Package-level Scope
Reliance on Package-level Scope
Technical detail
CWE-487 · Reliance on Package-level Scope
Reliance on Package-level Scope
In plain English
Reliance on Package-level Scope
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Java packages are not inherently closed; therefore, relying on them for code security is not a good practice.
CWE-488 · Exposure of Data Element to Wrong Session
Exposure of Data Element to Wrong Session
Technical detail
CWE-488 · Exposure of Data Element to Wrong Session
Exposure of Data Element to Wrong Session
In plain English
Exposure of Data Element to Wrong Session
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-489 · Active Debug Code
Active Debug Code
Technical detail
CWE-489 · Active Debug Code
Active Debug Code
In plain English
Active Debug Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product is released with debugging code still enabled or active.
CWE-491 · Public cloneable() Method Without Final ('Object Hijack')
Public cloneable() Method Without Final ('Object Hijack')
Technical detail
CWE-491 · Public cloneable() Method Without Final ('Object Hijack')
Public cloneable() Method Without Final ('Object Hijack')
In plain English
Public cloneable() Method Without Final ('Object Hijack')
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-492 · Use of Inner Class Containing Sensitive Data
Use of Inner Class Containing Sensitive Data
Technical detail
CWE-492 · Use of Inner Class Containing Sensitive Data
Use of Inner Class Containing Sensitive Data
In plain English
Use of Inner Class Containing Sensitive Data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-493 · Critical Public Variable Without Final Modifier
Critical Public Variable Without Final Modifier
Technical detail
CWE-493 · Critical Public Variable Without Final Modifier
Critical Public Variable Without Final Modifier
In plain English
Critical Public Variable Without Final Modifier
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has a critical public variable that is not final, which allows the variable to be modified to contain unexpected values.
CWE-494 · Download of Code Without Integrity Check
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-494 · Download of Code Without Integrity Check
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
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.
CWE-495 · Private Data Structure Returned From A Public Method
Private Data Structure Returned From A Public Method
Technical detail
CWE-495 · Private Data Structure Returned From A Public Method
Private Data Structure Returned From A Public Method
In plain English
Private Data Structure Returned From A Public Method
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-496 · Public Data Assigned to Private Array-Typed Field
Public Data Assigned to Private Array-Typed Field
Technical detail
CWE-496 · Public Data Assigned to Private Array-Typed Field
Public Data Assigned to Private Array-Typed Field
In plain English
Public Data Assigned to Private Array-Typed Field
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Assigning public data to a private array is equivalent to giving public access to the array.
CWE-497 · Exposure of Sensitive System Information to an Unauthorized Control Sphere
The product reveals details about the system that should not be public.
Important
CWE-497 · Exposure of Sensitive System Information to an Unauthorized Control Sphere
The product reveals details about the system that should not be public.
In plain English
The product reveals details about the system that should not be public.
What this can look like
An unauthenticated endpoint discloses software versions, internal paths, addresses, or configuration details that make targeted attacks easier.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
CWE-498 · Cloneable Class Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-498 · Cloneable Class Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class.
CWE-499 · Serializable Class Containing Sensitive Data
Serializable Class Containing Sensitive Data
Technical detail
CWE-499 · Serializable Class Containing Sensitive Data
Serializable Class Containing Sensitive Data
In plain English
Serializable Class Containing Sensitive Data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-500 · Public Static Field Not Marked Final
Public Static Field Not Marked Final
Technical detail
CWE-500 · Public Static Field Not Marked Final
Public Static Field Not Marked Final
In plain English
Public Static Field Not Marked Final
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An object contains a public static field that is not marked final, which might allow it to be modified in unexpected ways.
CWE-501 · Trust Boundary Violation
Trust Boundary Violation
Technical detail
CWE-501 · Trust Boundary Violation
Trust Boundary Violation
In plain English
Trust Boundary Violation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product mixes trusted and untrusted data in the same data structure or structured message.
CWE-502 · Deserialization of Untrusted Data
Untrusted serialized data is reconstructed without adequate safeguards.
Headline signal
CWE-502 · Deserialization of Untrusted Data
Untrusted serialized data is reconstructed without adequate safeguards.
In plain English
Untrusted serialized data is reconstructed without adequate safeguards.
What this can look like
A service accepts a crafted serialized object that triggers unintended behavior while it is being reconstructed, potentially leading to code execution.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
CWE-506 · Embedded Malicious Code
The product contains code intentionally designed to perform a malicious action.
Headline signal
CWE-506 · Embedded Malicious Code
The product contains code intentionally designed to perform a malicious action.
In plain English
The product contains code intentionally designed to perform a malicious action.
What this can look like
A shipped component contains functionality that secretly alters, destroys, exfiltrates, or provides unauthorized access to data or systems.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains code that appears to be malicious in nature.
CWE-507 · Trojan Horse
Apparently legitimate functionality hides a malicious purpose.
Headline signal
CWE-507 · Trojan Horse
Apparently legitimate functionality hides a malicious purpose.
In plain English
Apparently legitimate functionality hides a malicious purpose.
What this can look like
A normal-looking software component includes concealed behavior that activates unauthorized access or harmful actions.
An undocumented account, command, trigger, or communication path provides capabilities that are absent from the normal product interface.
A component appears to perform a legitimate function while secretly collecting information, bypassing controls, or activating hidden behavior.
MITRE description from the synchronized CWE record
The product appears to contain benign or useful functionality, but it also contains code that is hidden from normal operation that violates the intended security policy of the user or the system administrator.
CWE-508 · Non-Replicating Malicious Code
Non-Replicating Malicious Code
Technical detail
CWE-508 · Non-Replicating Malicious Code
Non-Replicating Malicious Code
In plain English
Non-Replicating Malicious Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Non-replicating malicious code only resides on the target system or product that is attacked; it does not attempt to spread to other systems.
CWE-509 · Replicating Malicious Code (Virus or Worm)
Replicating Malicious Code (Virus or Worm)
Technical detail
CWE-509 · Replicating Malicious Code (Virus or Worm)
Replicating Malicious Code (Virus or Worm)
In plain English
Replicating Malicious Code (Virus or Worm)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or the product.
CWE-510 · Trapdoor
A hidden mechanism bypasses normal security controls.
Headline signal
CWE-510 · Trapdoor
A hidden mechanism bypasses normal security controls.
In plain English
A hidden mechanism bypasses normal security controls.
What this can look like
An undocumented account, command, key sequence, or service allows privileged access without following the normal authentication path.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
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.
CWE-511 · Logic/Time Bomb
Hidden functionality activates when a particular condition or time is reached.
Headline signal
CWE-511 · Logic/Time Bomb
Hidden functionality activates when a particular condition or time is reached.
In plain English
Hidden functionality activates when a particular condition or time is reached.
What this can look like
Code behaves normally until a date, counter, user, or other trigger causes destructive or unauthorized behavior.
An undocumented account, command, trigger, or communication path provides capabilities that are absent from the normal product interface.
A component appears to perform a legitimate function while secretly collecting information, bypassing controls, or activating hidden behavior.
MITRE description from the synchronized CWE record
The product contains code that is designed to disrupt the legitimate operation of the product (or its environment) when a certain time passes, or when a certain logical condition is met.
CWE-512 · Spyware
The product covertly monitors or collects information.
Headline signal
CWE-512 · Spyware
The product covertly monitors or collects information.
In plain English
The product covertly monitors or collects information.
What this can look like
Software silently records user or system information and sends or exposes it without the expected authorization or transparency.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product collects personally identifiable information about a human user or the user's activities, but the product accesses this information using other resources besides itself, and it does not require that user's explicit approval or direct input into the product.
CWE-514 · Covert Channel
The product enables hidden communication through a channel not intended for information transfer.
Headline signal
CWE-514 · Covert Channel
The product enables hidden communication through a channel not intended for information transfer.
In plain English
The product enables hidden communication through a channel not intended for information transfer.
What this can look like
Two components encode information in timing, resource usage, or another indirect signal to bypass normal communication controls.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
A covert channel is a path that can be used to transfer information in a way not intended by the system's designers.
CWE-515 · Covert Storage Channel
Information is hidden in a shared storage mechanism to bypass intended controls.
Headline signal
CWE-515 · Covert Storage Channel
Information is hidden in a shared storage mechanism to bypass intended controls.
In plain English
Information is hidden in a shared storage mechanism to bypass intended controls.
What this can look like
One component writes secret state into metadata or another shared resource that a second component can read despite normal access restrictions.
An undocumented account, command, trigger, or communication path provides capabilities that are absent from the normal product interface.
A component appears to perform a legitimate function while secretly collecting information, bypassing controls, or activating hidden behavior.
MITRE description from the synchronized CWE record
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.
CWE-516 · DEPRECATED: Covert Timing Channel
DEPRECATED: Covert Timing Channel
Technical detail
CWE-516 · DEPRECATED: Covert Timing Channel
DEPRECATED: Covert Timing Channel
In plain English
DEPRECATED: Covert Timing Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
An undocumented account, command, trigger, or communication path provides capabilities that are absent from the normal product interface.
A component appears to perform a legitimate function while secretly collecting information, bypassing controls, or activating hidden behavior.
MITRE description from the synchronized CWE record
This weakness can be found at CWE-385.
CWE-520 · .NET Misconfiguration: Use of Impersonation
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-520 · .NET Misconfiguration: Use of Impersonation
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-521 · Weak Password Requirements
The system permits passwords that are too easy to guess or reuse.
Important
CWE-521 · Weak Password Requirements
The system permits passwords that are too easy to guess or reuse.
In plain English
The system permits passwords that are too easy to guess or reuse.
What this can look like
Users can choose extremely short or common passwords, making password guessing substantially easier.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product does not require that users should have strong passwords.
CWE-522 · Insufficiently Protected Credentials
Credentials are not adequately protected from disclosure or misuse.
Headline signal
CWE-522 · Insufficiently Protected Credentials
Credentials are not adequately protected from disclosure or misuse.
In plain English
Credentials are not adequately protected from disclosure or misuse.
What this can look like
Passwords, tokens, or authentication secrets are stored or handled in a way that makes them easier to recover after another compromise.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
CWE-523 · Unprotected Transport of Credentials
Credentials are sent without adequate transport protection.
Headline signal
CWE-523 · Unprotected Transport of Credentials
Credentials are sent without adequate transport protection.
In plain English
Credentials are sent without adequate transport protection.
What this can look like
A login is transmitted over an unencrypted or otherwise unprotected channel where another party on the network could capture it.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-524 · Use of Cache Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-524 · Use of Cache Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.
CWE-525 · Use of Web Browser Cache Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-525 · Use of Web Browser Cache Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
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.
CWE-526 · Cleartext Storage of Sensitive Information in an Environment Variable
The product can expose information beyond the audience that should receive it.
Important
CWE-526 · Cleartext Storage of Sensitive Information in an Environment Variable
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product uses an environment variable to store unencrypted sensitive information.
CWE-527 · Exposure of Version-Control Repository to an Unauthorized Control Sphere
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-527 · Exposure of Version-Control Repository to an Unauthorized Control Sphere
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-528 · Exposure of Core Dump File to an Unauthorized Control Sphere
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-528 · Exposure of Core Dump File to an Unauthorized Control Sphere
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-529 · Exposure of Access Control List Files to an Unauthorized Control Sphere
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-529 · Exposure of Access Control List Files to an Unauthorized Control Sphere
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.
CWE-530 · Exposure of Backup File to an Unauthorized Control Sphere
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-530 · Exposure of Backup File to an Unauthorized Control Sphere
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
A backup file is stored in a directory or archive that is made accessible to unauthorized actors.
CWE-531 · Inclusion of Sensitive Information in Test Code
The product can expose information beyond the audience that should receive it.
Important
CWE-531 · Inclusion of Sensitive Information in Test Code
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
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.
CWE-532 · Insertion of Sensitive Information into Log File
The product can expose information beyond the audience that should receive it.
Important
CWE-532 · Insertion of Sensitive Information into Log File
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product writes sensitive information to a log file.
CWE-533 · DEPRECATED: Information Exposure Through Server Log Files
The product can expose information beyond the audience that should receive it.
Important
CWE-533 · DEPRECATED: Information Exposure Through Server Log Files
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
This entry has been deprecated because its abstraction was too low-level. See CWE-532.
CWE-534 · DEPRECATED: Information Exposure Through Debug Log Files
The product can expose information beyond the audience that should receive it.
Important
CWE-534 · DEPRECATED: Information Exposure Through Debug Log Files
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
This entry has been deprecated because its abstraction was too low-level. See CWE-532.
CWE-535 · Exposure of Information Through Shell Error Message
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-535 · Exposure of Information Through Shell Error Message
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
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.
CWE-536 · Servlet Runtime Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-536 · Servlet Runtime Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
A servlet error message indicates that there exists an unhandled exception in the web application code and may provide useful information to an attacker.
CWE-537 · Java Runtime Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-537 · Java Runtime Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.
CWE-538 · Insertion of Sensitive Information into Externally-Accessible File or Directory
The product can expose information beyond the audience that should receive it.
Important
CWE-538 · Insertion of Sensitive Information into Externally-Accessible File or Directory
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
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.
CWE-539 · Use of Persistent Cookies Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-539 · Use of Persistent Cookies Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The web application uses persistent cookies, but the cookies contain sensitive information.
CWE-540 · Inclusion of Sensitive Information in Source Code
The product can expose information beyond the audience that should receive it.
Important
CWE-540 · Inclusion of Sensitive Information in Source Code
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.
CWE-541 · Inclusion of Sensitive Information in an Include File
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-541 · Inclusion of Sensitive Information in an Include File
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-542 · DEPRECATED: Information Exposure Through Cleanup Log Files
The product can expose information beyond the audience that should receive it.
Important
CWE-542 · DEPRECATED: Information Exposure Through Cleanup Log Files
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
This entry has been deprecated because its abstraction was too low-level. See CWE-532.
CWE-543 · Use of Singleton Pattern Without Synchronization in a Multithreaded Context
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-543 · Use of Singleton Pattern Without Synchronization in a Multithreaded Context
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses the singleton pattern when creating a resource within a multithreaded environment.
CWE-544 · Missing Standardized Error Handling Mechanism
Missing Standardized Error Handling Mechanism
Technical detail
CWE-544 · Missing Standardized Error Handling Mechanism
Missing Standardized Error Handling Mechanism
In plain English
Missing Standardized Error Handling Mechanism
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses.
CWE-545 · DEPRECATED: Use of Dynamic Class Loading
DEPRECATED: Use of Dynamic Class Loading
Technical detail
CWE-545 · DEPRECATED: Use of Dynamic Class Loading
DEPRECATED: Use of Dynamic Class Loading
In plain English
DEPRECATED: Use of Dynamic Class Loading
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-546 · Suspicious Comment
Suspicious Comment
Technical detail
CWE-546 · Suspicious Comment
Suspicious Comment
In plain English
Suspicious Comment
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.
CWE-547 · Use of Hard-coded, Security-relevant Constants
Use of Hard-coded, Security-relevant Constants
Technical detail
CWE-547 · Use of Hard-coded, Security-relevant Constants
Use of Hard-coded, Security-relevant Constants
In plain English
Use of Hard-coded, Security-relevant Constants
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or security policy change.
CWE-548 · Exposure of Information Through Directory Listing
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-548 · Exposure of Information Through Directory Listing
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product inappropriately exposes a directory listing with an index of all the resources located inside of the directory.
CWE-549 · Missing Password Field Masking
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-549 · Missing Password Field Masking
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.
CWE-550 · Server-generated Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-550 · Server-generated Error Message Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
Certain conditions, such as network failure, will cause a server error message to be displayed.
CWE-551 · Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-551 · Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-552 · Files or Directories Accessible to External Parties
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-552 · Files or Directories Accessible to External Parties
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product makes files or directories accessible to unauthorized actors, even though they should not be.
CWE-553 · Command Shell in Externally Accessible Directory
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-553 · Command Shell in Externally Accessible Directory
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
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.
CWE-554 · ASP.NET Misconfiguration: Not Using Input Validation Framework
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-554 · ASP.NET Misconfiguration: Not Using Input Validation Framework
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The ASP.NET application does not use an input validation framework.
CWE-555 · J2EE Misconfiguration: Plaintext Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-555 · J2EE Misconfiguration: Plaintext Password in Configuration File
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The J2EE application stores a plaintext password in a configuration file.
CWE-556 · ASP.NET Misconfiguration: Use of Identity Impersonation
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-556 · ASP.NET Misconfiguration: Use of Identity Impersonation
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
Configuring an ASP.NET application to run with impersonated credentials may give the application unnecessary privileges.
CWE-558 · Use of getlogin() in Multithreaded Application
Use of getlogin() in Multithreaded Application
Technical detail
CWE-558 · Use of getlogin() in Multithreaded Application
Use of getlogin() in Multithreaded Application
In plain English
Use of getlogin() in Multithreaded Application
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values.
CWE-560 · Use of umask() with chmod-style Argument
Use of umask() with chmod-style Argument
Technical detail
CWE-560 · Use of umask() with chmod-style Argument
Use of umask() with chmod-style Argument
In plain English
Use of umask() with chmod-style Argument
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls umask() with an incorrect argument that is specified as if it is an argument to chmod().
CWE-561 · Dead Code
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-561 · Dead Code
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product contains dead code, which can never be executed.
CWE-562 · Return of Stack Variable Address
Return of Stack Variable Address
Technical detail
CWE-562 · Return of Stack Variable Address
Return of Stack Variable Address
In plain English
Return of Stack Variable Address
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A function returns the address of a stack variable, which will cause unintended program behavior, typically in the form of a crash.
CWE-563 · Assignment to Variable without Use
Assignment to Variable without Use
Technical detail
CWE-563 · Assignment to Variable without Use
Assignment to Variable without Use
In plain English
Assignment to Variable without Use
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The variable's value is assigned but never used, making it a dead store.
CWE-564 · SQL Injection: Hibernate
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-564 · SQL Injection: Hibernate
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
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.
CWE-565 · Reliance on Cookies without Validation and Integrity Checking
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-565 · Reliance on Cookies without Validation and Integrity Checking
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product relies on the existence or values of cookies when performing security-critical operations, but it does not properly ensure that the setting is valid for the associated user.
CWE-566 · Authorization Bypass Through User-Controlled SQL Primary Key
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-566 · Authorization Bypass Through User-Controlled SQL Primary Key
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses a database table that includes records that should not be accessible to an actor, but it executes a SQL statement with a primary key that can be controlled by that actor.
CWE-567 · Unsynchronized Access to Shared Data in a Multithreaded Context
Unsynchronized Access to Shared Data in a Multithreaded Context
Technical detail
CWE-567 · Unsynchronized Access to Shared Data in a Multithreaded Context
Unsynchronized Access to Shared Data in a Multithreaded Context
In plain English
Unsynchronized Access to Shared Data in a Multithreaded Context
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes.
CWE-568 · finalize() Method Without super.finalize()
finalize() Method Without super.finalize()
Technical detail
CWE-568 · finalize() Method Without super.finalize()
finalize() Method Without super.finalize()
In plain English
finalize() Method Without super.finalize()
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a finalize() method that does not call super.finalize().
CWE-570 · Expression is Always False
Expression is Always False
Technical detail
CWE-570 · Expression is Always False
Expression is Always False
In plain English
Expression is Always False
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains an expression that will always evaluate to false.
CWE-571 · Expression is Always True
Expression is Always True
Technical detail
CWE-571 · Expression is Always True
Expression is Always True
In plain English
Expression is Always True
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains an expression that will always evaluate to true.
CWE-572 · Call to Thread run() instead of start()
Call to Thread run() instead of start()
Technical detail
CWE-572 · Call to Thread run() instead of start()
Call to Thread run() instead of start()
In plain English
Call to Thread run() instead of start()
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a thread's run() method instead of calling start(), which causes the code to run in the thread of the caller instead of the callee.
CWE-573 · Improper Following of Specification by Caller
Improper Following of Specification by Caller
Technical detail
CWE-573 · Improper Following of Specification by Caller
Improper Following of Specification by Caller
In plain English
Improper Following of Specification by Caller
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.
CWE-574 · EJB Bad Practices: Use of Synchronization Primitives
EJB Bad Practices: Use of Synchronization Primitives
Technical detail
CWE-574 · EJB Bad Practices: Use of Synchronization Primitives
EJB Bad Practices: Use of Synchronization Primitives
In plain English
EJB Bad Practices: Use of Synchronization Primitives
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.
CWE-575 · EJB Bad Practices: Use of AWT Swing
EJB Bad Practices: Use of AWT Swing
Technical detail
CWE-575 · EJB Bad Practices: Use of AWT Swing
EJB Bad Practices: Use of AWT Swing
In plain English
EJB Bad Practices: Use of AWT Swing
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing.
CWE-576 · EJB Bad Practices: Use of Java I/O
EJB Bad Practices: Use of Java I/O
Technical detail
CWE-576 · EJB Bad Practices: Use of Java I/O
EJB Bad Practices: Use of Java I/O
In plain English
EJB Bad Practices: Use of Java I/O
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product violates the Enterprise JavaBeans (EJB) specification by using the java.io package.
CWE-577 · EJB Bad Practices: Use of Sockets
EJB Bad Practices: Use of Sockets
Technical detail
CWE-577 · EJB Bad Practices: Use of Sockets
EJB Bad Practices: Use of Sockets
In plain English
EJB Bad Practices: Use of Sockets
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product violates the Enterprise JavaBeans (EJB) specification by using sockets.
CWE-578 · EJB Bad Practices: Use of Class Loader
EJB Bad Practices: Use of Class Loader
Technical detail
CWE-578 · EJB Bad Practices: Use of Class Loader
EJB Bad Practices: Use of Class Loader
In plain English
EJB Bad Practices: Use of Class Loader
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product violates the Enterprise JavaBeans (EJB) specification by using the class loader.
CWE-579 · J2EE Bad Practices: Non-serializable Object Stored in Session
J2EE Bad Practices: Non-serializable Object Stored in Session
Technical detail
CWE-579 · J2EE Bad Practices: Non-serializable Object Stored in Session
J2EE Bad Practices: Non-serializable Object Stored in Session
In plain English
J2EE Bad Practices: Non-serializable Object Stored in Session
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product stores a non-serializable object as an HttpSession attribute, which can hurt reliability.
CWE-580 · clone() Method Without super.clone()
clone() Method Without super.clone()
Technical detail
CWE-580 · clone() Method Without super.clone()
clone() Method Without super.clone()
In plain English
clone() Method Without super.clone()
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a clone() method that does not call super.clone() to obtain the new object.
CWE-581 · Object Model Violation: Just One of Equals and Hashcode Defined
Object Model Violation: Just One of Equals and Hashcode Defined
Technical detail
CWE-581 · Object Model Violation: Just One of Equals and Hashcode Defined
Object Model Violation: Just One of Equals and Hashcode Defined
In plain English
Object Model Violation: Just One of Equals and Hashcode Defined
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product does not maintain equal hashcodes for equal objects.
CWE-582 · Array Declared Public, Final, and Static
Array Declared Public, Final, and Static
Technical detail
CWE-582 · Array Declared Public, Final, and Static
Array Declared Public, Final, and Static
In plain English
Array Declared Public, Final, and Static
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product declares an array public, final, and static, which is not sufficient to prevent the array's contents from being modified.
CWE-583 · finalize() Method Declared Public
finalize() Method Declared Public
Technical detail
CWE-583 · finalize() Method Declared Public
finalize() Method Declared Public
In plain English
finalize() Method Declared Public
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product violates secure coding principles for mobile code by declaring a finalize() method public.
CWE-584 · Return Inside Finally Block
Return Inside Finally Block
Technical detail
CWE-584 · Return Inside Finally Block
Return Inside Finally Block
In plain English
Return Inside Finally Block
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.
CWE-585 · Empty Synchronized Block
Empty Synchronized Block
Technical detail
CWE-585 · Empty Synchronized Block
Empty Synchronized Block
In plain English
Empty Synchronized Block
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains an empty synchronized block.
CWE-586 · Explicit Call to Finalize()
Explicit Call to Finalize()
Technical detail
CWE-586 · Explicit Call to Finalize()
Explicit Call to Finalize()
In plain English
Explicit Call to Finalize()
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product makes an explicit call to the finalize() method from outside the finalizer.
CWE-587 · Assignment of a Fixed Address to a Pointer
The product handles memory in an unsafe way.
Important
CWE-587 · Assignment of a Fixed Address to a Pointer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product sets a pointer to a specific address other than NULL or 0.
CWE-588 · Attempt to Access Child of a Non-structure Pointer
The product handles memory in an unsafe way.
Important
CWE-588 · Attempt to Access Child of a Non-structure Pointer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption.
CWE-589 · Call to Non-ubiquitous API
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-589 · Call to Non-ubiquitous API
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses an API function that does not exist on all versions of the target platform. This could cause portability problems or inconsistencies that allow denial of service or other consequences.
CWE-590 · Free of Memory not on the Heap
The product handles memory in an unsafe way.
Important
CWE-590 · Free of Memory not on the Heap
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().
CWE-591 · Sensitive Data Storage in Improperly Locked Memory
The product handles memory in an unsafe way.
Important
CWE-591 · Sensitive Data Storage in Improperly Locked Memory
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product stores sensitive data in memory that is not locked, or that has been incorrectly locked, which might cause the memory to be written to swap files on disk by the virtual memory manager. This can make the data more accessible to external actors.
CWE-592 · DEPRECATED: Authentication Bypass Issues
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-592 · DEPRECATED: Authentication Bypass Issues
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
This weakness has been deprecated because it covered redundant concepts already described in CWE-287.
CWE-593 · Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-593 · Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product modifies the SSL context after connection creation has begun.
CWE-594 · J2EE Framework: Saving Unserializable Objects to Disk
J2EE Framework: Saving Unserializable Objects to Disk
Technical detail
CWE-594 · J2EE Framework: Saving Unserializable Objects to Disk
J2EE Framework: Saving Unserializable Objects to Disk
In plain English
J2EE Framework: Saving Unserializable Objects to Disk
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
When the J2EE container attempts to write unserializable objects to disk there is no guarantee that the process will complete successfully.
CWE-595 · Comparison of Object References Instead of Object Contents
Comparison of Object References Instead of Object Contents
Technical detail
CWE-595 · Comparison of Object References Instead of Object Contents
Comparison of Object References Instead of Object Contents
In plain English
Comparison of Object References Instead of Object Contents
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product compares object references instead of the contents of the objects themselves, preventing it from detecting equivalent objects.
CWE-596 · DEPRECATED: Incorrect Semantic Object Comparison
DEPRECATED: Incorrect Semantic Object Comparison
Technical detail
CWE-596 · DEPRECATED: Incorrect Semantic Object Comparison
DEPRECATED: Incorrect Semantic Object Comparison
In plain English
DEPRECATED: Incorrect Semantic Object Comparison
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-597 · Use of Wrong Operator in String Comparison
Use of Wrong Operator in String Comparison
Technical detail
CWE-597 · Use of Wrong Operator in String Comparison
Use of Wrong Operator in String Comparison
In plain English
Use of Wrong Operator in String Comparison
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead.
CWE-598 · Use of HTTP Request With Sensitive Query String
The product can expose information beyond the audience that should receive it.
Important
CWE-598 · Use of HTTP Request With Sensitive Query String
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The web application uses an HTTP method to process a request, but the request includes sensitive information in the query string.
CWE-599 · Missing Validation of OpenSSL Certificate
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-599 · Missing Validation of OpenSSL Certificate
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses OpenSSL and trusts or uses a certificate without using the SSL_get_verify_result() function to ensure that the certificate satisfies all necessary security requirements.
CWE-600 · Uncaught Exception in Servlet
Uncaught Exception in Servlet
Technical detail
CWE-600 · Uncaught Exception in Servlet
Uncaught Exception in Servlet
In plain English
Uncaught Exception in Servlet
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The Servlet does not catch all exceptions, which may reveal sensitive debugging information.
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
CWE-602 · Client-Side Enforcement of Server-Side Security
Client-Side Enforcement of Server-Side Security
Technical detail
CWE-602 · Client-Side Enforcement of Server-Side Security
Client-Side Enforcement of Server-Side Security
In plain English
Client-Side Enforcement of Server-Side Security
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
CWE-603 · Use of Client-Side Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-603 · Use of Client-Side Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-605 · Multiple Binds to the Same Port
Multiple Binds to the Same Port
Technical detail
CWE-605 · Multiple Binds to the Same Port
Multiple Binds to the Same Port
In plain English
Multiple Binds to the Same Port
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.
CWE-606 · Unchecked Input for Loop Condition
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-606 · Unchecked Input for Loop Condition
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
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.
CWE-607 · Public Static Final Field References Mutable Object
Public Static Final Field References Mutable Object
Technical detail
CWE-607 · Public Static Final Field References Mutable Object
Public Static Final Field References Mutable Object
In plain English
Public Static Final Field References Mutable Object
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-608 · Struts: Non-private Field in ActionForm Class
Struts: Non-private Field in ActionForm Class
Technical detail
CWE-608 · Struts: Non-private Field in ActionForm Class
Struts: Non-private Field in ActionForm Class
In plain English
Struts: Non-private Field in ActionForm Class
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter.
CWE-609 · Double-Checked Locking
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-609 · Double-Checked Locking
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.
CWE-610 · Externally Controlled Reference to a Resource in Another Sphere
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-610 · Externally Controlled Reference to a Resource in Another Sphere
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.
CWE-611 · Improper Restriction of XML External Entity Reference
XML processing permits external entities or similar unsafe references.
Important
CWE-611 · Improper Restriction of XML External Entity Reference
XML processing permits external entities or similar unsafe references.
In plain English
XML processing permits external entities or similar unsafe references.
What this can look like
A crafted XML document causes the parser to read a local file or make an unintended network request while resolving an external entity.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product to embed incorrect documents into its output.
CWE-612 · Improper Authorization of Index Containing Sensitive Information
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-612 · Improper Authorization of Index Containing Sensitive Information
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-613 · Insufficient Session Expiration
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-613 · Insufficient Session Expiration
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
CWE-614 · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Technical detail
CWE-614 · Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
In plain English
Sensitive Cookie in HTTPS Session Without 'Secure' Attribute
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The Secure attribute for sensitive cookies in HTTPS sessions is not set.
CWE-615 · Inclusion of Sensitive Information in Source Code Comments
The product can expose information beyond the audience that should receive it.
Important
CWE-615 · Inclusion of Sensitive Information in Source Code Comments
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
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.
CWE-616 · Incomplete Identification of Uploaded File Variables (PHP)
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-616 · Incomplete Identification of Uploaded File Variables (PHP)
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-617 · Reachable Assertion
Reachable Assertion
Technical detail
CWE-617 · Reachable Assertion
Reachable Assertion
In plain English
Reachable Assertion
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-618 · Exposed Unsafe ActiveX Method
Exposed Unsafe ActiveX Method
Technical detail
CWE-618 · Exposed Unsafe ActiveX Method
Exposed Unsafe ActiveX Method
In plain English
Exposed Unsafe ActiveX Method
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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).
CWE-619 · Dangling Database Cursor ('Cursor Injection')
Dangling Database Cursor ('Cursor Injection')
Technical detail
CWE-619 · Dangling Database Cursor ('Cursor Injection')
Dangling Database Cursor ('Cursor Injection')
In plain English
Dangling Database Cursor ('Cursor Injection')
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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."
CWE-620 · Unverified Password Change
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-620 · Unverified Password Change
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.
CWE-621 · Variable Extraction Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-621 · Variable Extraction Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-622 · Improper Validation of Function Hook Arguments
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-622 · Improper Validation of Function Hook Arguments
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product adds hooks to user-accessible API functions, but it does not properly validate the arguments. This could lead to resultant vulnerabilities.
CWE-623 · Unsafe ActiveX Control Marked Safe For Scripting
Unsafe ActiveX Control Marked Safe For Scripting
Technical detail
CWE-623 · Unsafe ActiveX Control Marked Safe For Scripting
Unsafe ActiveX Control Marked Safe For Scripting
In plain English
Unsafe ActiveX Control Marked Safe For Scripting
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.
CWE-624 · Executable Regular Expression Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-624 · Executable Regular Expression Error
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-625 · Permissive Regular Expression
Permissive Regular Expression
Technical detail
CWE-625 · Permissive Regular Expression
Permissive Regular Expression
In plain English
Permissive Regular Expression
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a regular expression that does not sufficiently restrict the set of allowed values.
CWE-626 · Null Byte Interaction Error (Poison Null Byte)
Null Byte Interaction Error (Poison Null Byte)
Technical detail
CWE-626 · Null Byte Interaction Error (Poison Null Byte)
Null Byte Interaction Error (Poison Null Byte)
In plain English
Null Byte Interaction Error (Poison Null Byte)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly handle null bytes or NUL characters when passing data between different representations or components.
CWE-627 · Dynamic Variable Evaluation
Dynamic Variable Evaluation
Technical detail
CWE-627 · Dynamic Variable Evaluation
Dynamic Variable Evaluation
In plain English
Dynamic Variable Evaluation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-628 · Function Call with Incorrectly Specified Arguments
Function Call with Incorrectly Specified Arguments
Technical detail
CWE-628 · Function Call with Incorrectly Specified Arguments
Function Call with Incorrectly Specified Arguments
In plain English
Function Call with Incorrectly Specified Arguments
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses.
CWE-636 · Not Failing Securely ('Failing Open')
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-636 · Not Failing Securely ('Failing Open')
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-637 · Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
Technical detail
CWE-637 · Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
In plain English
Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a more complex mechanism than necessary, which could lead to resultant weaknesses when the mechanism is not correctly understood, modeled, configured, implemented, or used.
CWE-638 · Not Using Complete Mediation
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-638 · Not Using Complete Mediation
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not perform access checks on a resource every time the resource is accessed by an entity, which can create resultant weaknesses if that entity's rights or privileges change over time.
CWE-639 · Authorization Bypass Through User-Controlled Key
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-639 · Authorization Bypass Through User-Controlled Key
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-640 · Weak Password Recovery Mechanism for Forgotten Password
Account recovery can be abused to take over an account.
Important
CWE-640 · Weak Password Recovery Mechanism for Forgotten Password
Account recovery can be abused to take over an account.
In plain English
Account recovery can be abused to take over an account.
What this can look like
A reset flow relies on predictable questions, tokens, or insufficient identity checks, allowing someone other than the account owner to reset the password.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.
CWE-641 · Improper Restriction of Names for Files and Other Resources
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-641 · Improper Restriction of Names for Files and Other Resources
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product constructs the name of a file or other resource using input from an upstream component, but it does not restrict or incorrectly restricts the resulting name.
CWE-642 · External Control of Critical State Data
External Control of Critical State Data
Technical detail
CWE-642 · External Control of Critical State Data
External Control of Critical State Data
In plain English
External Control of Critical State Data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product stores security-critical state information about its users, or the product itself, in a location that is accessible to unauthorized actors.
CWE-643 · Improper Neutralization of Data within XPath Expressions ('XPath Injection')
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-643 · Improper Neutralization of Data within XPath Expressions ('XPath Injection')
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses external input to dynamically construct an XPath expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query.
CWE-644 · Improper Neutralization of HTTP Headers for Scripting Syntax
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-644 · Improper Neutralization of HTTP Headers for Scripting Syntax
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash.
CWE-645 · Overly Restrictive Account Lockout Mechanism
Overly Restrictive Account Lockout Mechanism
Technical detail
CWE-645 · Overly Restrictive Account Lockout Mechanism
Overly Restrictive Account Lockout Mechanism
In plain English
Overly Restrictive Account Lockout Mechanism
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily, which allows attackers to deny service to legitimate users by causing their accounts to be locked out.
CWE-646 · Reliance on File Name or Extension of Externally-Supplied File
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-646 · Reliance on File Name or Extension of Externally-Supplied File
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product allows a file to be uploaded, but it relies on the file name or extension of the file to determine the appropriate behaviors. This could be used by attackers to cause the file to be misclassified and processed in a dangerous fashion.
CWE-647 · Use of Non-Canonical URL Paths for Authorization Decisions
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-647 · Use of Non-Canonical URL Paths for Authorization Decisions
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization.
CWE-648 · Incorrect Use of Privileged APIs
Incorrect Use of Privileged APIs
Technical detail
CWE-648 · Incorrect Use of Privileged APIs
Incorrect Use of Privileged APIs
In plain English
Incorrect Use of Privileged APIs
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
CWE-649 · Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-649 · Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.
CWE-650 · Trusting HTTP Permission Methods on the Server Side
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-650 · Trusting HTTP Permission Methods on the Server Side
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-651 · Exposure of WSDL File Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-651 · Exposure of WSDL File Containing Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
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).
CWE-652 · Improper Neutralization of Data within XQuery Expressions ('XQuery Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-652 · Improper Neutralization of Data within XQuery Expressions ('XQuery Injection')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses external input to dynamically construct an XQuery expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query.
CWE-653 · Improper Isolation or Compartmentalization
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-653 · Improper Isolation or Compartmentalization
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.
CWE-654 · Reliance on a Single Factor in a Security Decision
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-654 · Reliance on a Single Factor in a Security Decision
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
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.
CWE-655 · Insufficient Psychological Acceptability
Insufficient Psychological Acceptability
Technical detail
CWE-655 · Insufficient Psychological Acceptability
Insufficient Psychological Acceptability
In plain English
Insufficient Psychological Acceptability
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has a protection mechanism that is too difficult or inconvenient to use, encouraging non-malicious users to disable or bypass the mechanism, whether by accident or on purpose.
CWE-656 · Reliance on Security Through Obscurity
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-656 · Reliance on Security Through Obscurity
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism.
CWE-657 · Violation of Secure Design Principles
Violation of Secure Design Principles
Technical detail
CWE-657 · Violation of Secure Design Principles
Violation of Secure Design Principles
In plain English
Violation of Secure Design Principles
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product violates well-established principles for secure design.
CWE-662 · Improper Synchronization
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-662 · Improper Synchronization
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product utilizes multiple threads, processes, components, or systems 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.
CWE-663 · Use of a Non-reentrant Function in a Concurrent Context
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-663 · Use of a Non-reentrant Function in a Concurrent Context
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
The product calls a non-reentrant function in a concurrent context in which a competing code sequence (e.g. thread or signal handler) may have an opportunity to call the same function or otherwise influence its state.
CWE-664 · Improper Control of a Resource Through its Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-664 · Improper Control of a Resource Through its Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.
CWE-665 · Improper Initialization
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-665 · Improper Initialization
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not initialize or incorrectly initializes a resource, which might leave the resource in an unexpected state when it is accessed or used.
CWE-666 · Operation on Resource in Wrong Phase of Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-666 · Operation on Resource in Wrong Phase of Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product performs an operation on a resource at the wrong phase of the resource's lifecycle, which can lead to unexpected behaviors.
CWE-667 · Improper Locking
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-667 · Improper Locking
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
CWE-668 · Exposure of Resource to Wrong Sphere
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-668 · Exposure of Resource to Wrong Sphere
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
CWE-669 · Incorrect Resource Transfer Between Spheres
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-669 · Incorrect Resource Transfer Between Spheres
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
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.
CWE-670 · Always-Incorrect Control Flow Implementation
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-670 · Always-Incorrect Control Flow Implementation
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
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.
CWE-671 · Lack of Administrator Control over Security
Lack of Administrator Control over Security
Technical detail
CWE-671 · Lack of Administrator Control over Security
Lack of Administrator Control over Security
In plain English
Lack of Administrator Control over Security
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-672 · Operation on a Resource after Expiration or Release
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-672 · Operation on a Resource after Expiration or Release
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.
CWE-673 · External Influence of Sphere Definition
External Influence of Sphere Definition
Technical detail
CWE-673 · External Influence of Sphere Definition
External Influence of Sphere Definition
In plain English
External Influence of Sphere Definition
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not prevent the definition of control spheres from external actors.
CWE-674 · Uncontrolled Recursion
The product handles memory in an unsafe way.
Important
CWE-674 · Uncontrolled Recursion
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.
CWE-675 · Multiple Operations on Resource in Single-Operation Context
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-675 · Multiple Operations on Resource in Single-Operation Context
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product performs the same operation on a resource two or more times, when the operation should only be applied once.
CWE-676 · Use of Potentially Dangerous Function
Use of Potentially Dangerous Function
Technical detail
CWE-676 · Use of Potentially Dangerous Function
Use of Potentially Dangerous Function
In plain English
Use of Potentially Dangerous Function
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product invokes a potentially dangerous function that could introduce a vulnerability if it is used incorrectly, but the function can also be used safely.
CWE-680 · Integer Overflow to Buffer Overflow
The product handles memory in an unsafe way.
Important
CWE-680 · Integer Overflow to Buffer Overflow
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
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.
CWE-681 · Incorrect Conversion between Numeric Types
Incorrect Conversion between Numeric Types
Technical detail
CWE-681 · Incorrect Conversion between Numeric Types
Incorrect Conversion between Numeric Types
In plain English
Incorrect Conversion between Numeric Types
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-682 · Incorrect Calculation
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-682 · Incorrect Calculation
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.
CWE-683 · Function Call With Incorrect Order of Arguments
Function Call With Incorrect Order of Arguments
Technical detail
CWE-683 · Function Call With Incorrect Order of Arguments
Function Call With Incorrect Order of Arguments
In plain English
Function Call With Incorrect Order of Arguments
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses.
CWE-684 · Incorrect Provision of Specified Functionality
Incorrect Provision of Specified Functionality
Technical detail
CWE-684 · Incorrect Provision of Specified Functionality
Incorrect Provision of Specified Functionality
In plain English
Incorrect Provision of Specified Functionality
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code does not function according to its published specifications, potentially leading to incorrect usage.
CWE-685 · Function Call With Incorrect Number of Arguments
Function Call With Incorrect Number of Arguments
Technical detail
CWE-685 · Function Call With Incorrect Number of Arguments
Function Call With Incorrect Number of Arguments
In plain English
Function Call With Incorrect Number of Arguments
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a function, procedure, or routine, but the caller specifies too many arguments, or too few arguments, which may lead to undefined behavior and resultant weaknesses.
CWE-686 · Function Call With Incorrect Argument Type
Function Call With Incorrect Argument Type
Technical detail
CWE-686 · Function Call With Incorrect Argument Type
Function Call With Incorrect Argument Type
In plain English
Function Call With Incorrect Argument Type
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a function, procedure, or routine, but the caller specifies an argument that is the wrong data type, which may lead to resultant weaknesses.
CWE-687 · Function Call With Incorrectly Specified Argument Value
Function Call With Incorrectly Specified Argument Value
Technical detail
CWE-687 · Function Call With Incorrectly Specified Argument Value
Function Call With Incorrectly Specified Argument Value
In plain English
Function Call With Incorrectly Specified Argument Value
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a function, procedure, or routine, but the caller specifies an argument that contains the wrong value, which may lead to resultant weaknesses.
CWE-688 · Function Call With Incorrect Variable or Reference as Argument
Function Call With Incorrect Variable or Reference as Argument
Technical detail
CWE-688 · Function Call With Incorrect Variable or Reference as Argument
Function Call With Incorrect Variable or Reference as Argument
In plain English
Function Call With Incorrect Variable or Reference as Argument
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product calls a function, procedure, or routine, but the caller specifies the wrong variable or reference as one of the arguments, which may lead to undefined behavior and resultant weaknesses.
CWE-689 · Permission Race Condition During Resource Copy
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-689 · Permission Race Condition During Resource Copy
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-690 · Unchecked Return Value to NULL Pointer Dereference
The product handles memory in an unsafe way.
Important
CWE-690 · Unchecked Return Value to NULL Pointer Dereference
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
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.
CWE-691 · Insufficient Control Flow Management
Insufficient Control Flow Management
Technical detail
CWE-691 · Insufficient Control Flow Management
Insufficient Control Flow Management
In plain English
Insufficient Control Flow Management
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.
CWE-692 · Incomplete Denylist to Cross-Site Scripting
Incomplete Denylist to Cross-Site Scripting
Technical detail
CWE-692 · Incomplete Denylist to Cross-Site Scripting
Incomplete Denylist to Cross-Site Scripting
In plain English
Incomplete Denylist to Cross-Site Scripting
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a denylist-based protection mechanism to defend against XSS attacks, but the denylist is incomplete, allowing XSS variants to succeed.
CWE-693 · Protection Mechanism Failure
Protection Mechanism Failure
Technical detail
CWE-693 · Protection Mechanism Failure
Protection Mechanism Failure
In plain English
Protection Mechanism Failure
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.
CWE-694 · Use of Multiple Resources with Duplicate Identifier
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-694 · Use of Multiple Resources with Duplicate Identifier
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.
CWE-695 · Use of Low-Level Functionality
Use of Low-Level Functionality
Technical detail
CWE-695 · Use of Low-Level Functionality
Use of Low-Level Functionality
In plain English
Use of Low-Level Functionality
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses low-level functionality that is explicitly prohibited by the framework or specification under which the product is supposed to operate.
CWE-696 · Incorrect Behavior Order
Incorrect Behavior Order
Technical detail
CWE-696 · Incorrect Behavior Order
Incorrect Behavior Order
In plain English
Incorrect Behavior Order
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways that may produce resultant weaknesses.
CWE-697 · Incorrect Comparison
Incorrect Comparison
Technical detail
CWE-697 · Incorrect Comparison
Incorrect Comparison
In plain English
Incorrect Comparison
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product compares two entities in a security-relevant context, but the comparison is incorrect.
CWE-698 · Execution After Redirect (EAR)
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-698 · Execution After Redirect (EAR)
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The web application sends a redirect to another location, but instead of exiting, it executes additional code.
CWE-703 · Improper Check or Handling of Exceptional Conditions
Improper Check or Handling of Exceptional Conditions
Technical detail
CWE-703 · Improper Check or Handling of Exceptional Conditions
Improper Check or Handling of Exceptional Conditions
In plain English
Improper Check or Handling of Exceptional Conditions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.
CWE-704 · Incorrect Type Conversion or Cast
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-704 · Incorrect Type Conversion or Cast
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not correctly convert an object, resource, or structure from one type to a different type.
CWE-705 · Incorrect Control Flow Scoping
Incorrect Control Flow Scoping
Technical detail
CWE-705 · Incorrect Control Flow Scoping
Incorrect Control Flow Scoping
In plain English
Incorrect Control Flow Scoping
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.
CWE-706 · Use of Incorrectly-Resolved Name or Reference
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-706 · Use of Incorrectly-Resolved Name or Reference
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.
CWE-707 · Improper Neutralization
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-707 · Improper Neutralization
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
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.
CWE-708 · Incorrect Ownership Assignment
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-708 · Incorrect Ownership Assignment
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product assigns an owner to a resource, but the owner is outside of the intended control sphere.
CWE-710 · Improper Adherence to Coding Standards
Improper Adherence to Coding Standards
Technical detail
CWE-710 · Improper Adherence to Coding Standards
Improper Adherence to Coding Standards
In plain English
Improper Adherence to Coding Standards
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.
CWE-732 · Incorrect Permission Assignment for Critical Resource
A critical resource receives permissions that are broader than intended.
Important
CWE-732 · Incorrect Permission Assignment for Critical Resource
A critical resource receives permissions that are broader than intended.
In plain English
A critical resource receives permissions that are broader than intended.
What this can look like
A service creates a sensitive file or object writable by ordinary users, allowing its contents or behavior to be changed.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
CWE-733 · Compiler Optimization Removal or Modification of Security-critical Code
Compiler Optimization Removal or Modification of Security-critical Code
Technical detail
CWE-733 · Compiler Optimization Removal or Modification of Security-critical Code
Compiler Optimization Removal or Modification of Security-critical Code
In plain English
Compiler Optimization Removal or Modification of Security-critical Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-749 · Exposed Dangerous Method or Function
Exposed Dangerous Method or Function
Technical detail
CWE-749 · Exposed Dangerous Method or Function
Exposed Dangerous Method or Function
In plain English
Exposed Dangerous Method or Function
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous method or function that is not properly restricted.
CWE-754 · Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions
Technical detail
CWE-754 · Improper Check for Unusual or Exceptional Conditions
Improper Check for Unusual or Exceptional Conditions
In plain English
Improper Check for Unusual or Exceptional Conditions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not check or incorrectly checks for unusual or exceptional conditions that are not expected to occur frequently during day to day operation of the product.
CWE-755 · Improper Handling of Exceptional Conditions
Improper Handling of Exceptional Conditions
Technical detail
CWE-755 · Improper Handling of Exceptional Conditions
Improper Handling of Exceptional Conditions
In plain English
Improper Handling of Exceptional Conditions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not handle or incorrectly handles an exceptional condition.
CWE-756 · Missing Custom Error Page
The product can expose information beyond the audience that should receive it.
Important
CWE-756 · Missing Custom Error Page
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product does not return custom error pages to the user, possibly exposing sensitive information.
CWE-757 · Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-757 · Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
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.
CWE-758 · Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
Technical detail
CWE-758 · Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
In plain English
Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses an API function, data structure, or other entity in a way that relies on properties that are not always guaranteed to hold for that entity.
CWE-759 · Use of a One-Way Hash without a Salt
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-759 · Use of a One-Way Hash without a Salt
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input.
CWE-760 · Use of a One-Way Hash with a Predictable Salt
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-760 · Use of a One-Way Hash with a Predictable Salt
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product uses a predictable salt as part of the input.
CWE-761 · Free of Pointer not at Start of Buffer
The product handles memory in an unsafe way.
Important
CWE-761 · Free of Pointer not at Start of Buffer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product calls free() on a pointer to a memory resource that was allocated on the heap, but the pointer is not at the start of the buffer.
CWE-762 · Mismatched Memory Management Routines
The product handles memory in an unsafe way.
Important
CWE-762 · Mismatched Memory Management Routines
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource.
CWE-763 · Release of Invalid Pointer or Reference
The product handles memory in an unsafe way.
Important
CWE-763 · Release of Invalid Pointer or Reference
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
CWE-764 · Multiple Locks of a Critical Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-764 · Multiple Locks of a Critical Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product locks a critical resource more times than intended, leading to an unexpected state in the system.
CWE-765 · Multiple Unlocks of a Critical Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-765 · Multiple Unlocks of a Critical Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.
CWE-766 · Critical Data Element Declared Public
Critical Data Element Declared Public
Technical detail
CWE-766 · Critical Data Element Declared Public
Critical Data Element Declared Public
In plain English
Critical Data Element Declared Public
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product declares a critical variable, field, or member to be public when intended security policy requires it to be private.
CWE-767 · Access to Critical Private Variable via Public Method
Access to Critical Private Variable via Public Method
Technical detail
CWE-767 · Access to Critical Private Variable via Public Method
Access to Critical Private Variable via Public Method
In plain English
Access to Critical Private Variable via Public Method
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product defines a public method that reads or modifies a private variable.
CWE-768 · Incorrect Short Circuit Evaluation
Incorrect Short Circuit Evaluation
Technical detail
CWE-768 · Incorrect Short Circuit Evaluation
Incorrect Short Circuit Evaluation
In plain English
Incorrect Short Circuit Evaluation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a conditional statement with multiple logical expressions in which one of the non-leading expressions may produce side effects. This may lead to an unexpected state in the program after the execution of the conditional, because short-circuiting logic may prevent the side effects from occurring.
CWE-769 · DEPRECATED: Uncontrolled File Descriptor Consumption
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-769 · DEPRECATED: Uncontrolled File Descriptor Consumption
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
This entry has been deprecated because it was a duplicate of CWE-774. All content has been transferred to CWE-774.
CWE-770 · Allocation of Resources Without Limits or Throttling
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-770 · Allocation of Resources Without Limits or Throttling
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product allocates a reusable resource or group of resources on behalf of an actor without imposing any intended restrictions on the size or number of resources that can be allocated.
CWE-771 · Missing Reference to Active Allocated Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-771 · Missing Reference to Active Allocated Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not properly maintain a reference to a resource that has been allocated, which prevents the resource from being reclaimed.
CWE-772 · Missing Release of Resource after Effective Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-772 · Missing Release of Resource after Effective Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.
CWE-773 · Missing Reference to Active File Descriptor or Handle
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-773 · Missing Reference to Active File Descriptor or Handle
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not properly maintain references to a file descriptor or handle, which prevents that file descriptor/handle from being reclaimed.
CWE-774 · Allocation of File Descriptors or Handles Without Limits or Throttling
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-774 · Allocation of File Descriptors or Handles Without Limits or Throttling
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product allocates file descriptors or handles on behalf of an actor without imposing any restrictions on how many descriptors can be allocated, in violation of the intended security policy for that actor.
CWE-775 · Missing Release of File Descriptor or Handle after Effective Lifetime
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-775 · Missing Release of File Descriptor or Handle after Effective Lifetime
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not release a file descriptor or handle after its effective lifetime has ended, i.e., after the file descriptor/handle is no longer needed.
CWE-776 · Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
Technical detail
CWE-776 · Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
In plain English
Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion')
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses XML documents and allows their structure to be defined with a Document Type Definition (DTD), but it does not properly control the number of recursive definitions of entities.
CWE-777 · Regular Expression without Anchors
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-777 · Regular Expression without Anchors
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses a regular expression to perform neutralization, but the regular expression is not anchored and may allow malicious or malformed data to slip through.
CWE-778 · Insufficient Logging
Insufficient Logging
Technical detail
CWE-778 · Insufficient Logging
Insufficient Logging
In plain English
Insufficient Logging
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.
CWE-779 · Logging of Excessive Data
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-779 · Logging of Excessive Data
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.
CWE-780 · Use of RSA Algorithm without OAEP
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-780 · Use of RSA Algorithm without OAEP
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses the RSA algorithm but does not incorporate Optimal Asymmetric Encryption Padding (OAEP), which might weaken the encryption.
CWE-781 · Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-781 · Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product defines an IOCTL that uses METHOD_NEITHER for I/O, but it does not validate or incorrectly validates the addresses that are provided.
CWE-782 · Exposed IOCTL with Insufficient Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-782 · Exposed IOCTL with Insufficient Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.
CWE-783 · Operator Precedence Logic Error
Operator Precedence Logic Error
Technical detail
CWE-783 · Operator Precedence Logic Error
Operator Precedence Logic Error
In plain English
Operator Precedence Logic Error
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses an expression in which operator precedence causes incorrect logic to be used.
CWE-784 · Reliance on Cookies without Validation and Integrity Checking in a Security Decision
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-784 · Reliance on Cookies without Validation and Integrity Checking in a Security Decision
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses a protection mechanism that relies on the existence or values of a cookie, but it does not properly ensure that the cookie is valid for the associated user.
CWE-785 · Use of Path Manipulation Function without Maximum-sized Buffer
The product handles memory in an unsafe way.
Important
CWE-785 · Use of Path Manipulation Function without Maximum-sized Buffer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product invokes a function for normalizing paths or file names, but it provides an output buffer that is smaller than the maximum possible size, such as PATH_MAX.
CWE-786 · Access of Memory Location Before Start of Buffer
The product handles memory in an unsafe way.
Important
CWE-786 · Access of Memory Location Before Start of Buffer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product reads or writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.
CWE-787 · Out-of-bounds Write
Software writes data outside the memory region intended for it.
Headline signal
CWE-787 · Out-of-bounds Write
Software writes data outside the memory region intended for it.
In plain English
Software writes data outside the memory region intended for it.
What this can look like
A specially crafted input makes a parser write beyond a buffer boundary, potentially crashing the process or corrupting control data used by the program.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product writes data past the end, or before the beginning, of the intended buffer.
CWE-788 · Access of Memory Location After End of Buffer
The product handles memory in an unsafe way.
Important
CWE-788 · Access of Memory Location After End of Buffer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.
CWE-789 · Memory Allocation with Excessive Size Value
The product handles memory in an unsafe way.
Important
CWE-789 · Memory Allocation with Excessive Size Value
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
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.
CWE-790 · Improper Filtering of Special Elements
Improper Filtering of Special Elements
Technical detail
CWE-790 · Improper Filtering of Special Elements
Improper Filtering of Special Elements
In plain English
Improper Filtering of Special Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but does not filter or incorrectly filters special elements before sending it to a downstream component.
CWE-791 · Incomplete Filtering of Special Elements
Incomplete Filtering of Special Elements
Technical detail
CWE-791 · Incomplete Filtering of Special Elements
Incomplete Filtering of Special Elements
In plain English
Incomplete Filtering of Special Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.
CWE-792 · Incomplete Filtering of One or More Instances of Special Elements
Incomplete Filtering of One or More Instances of Special Elements
Technical detail
CWE-792 · Incomplete Filtering of One or More Instances of Special Elements
Incomplete Filtering of One or More Instances of Special Elements
In plain English
Incomplete Filtering of One or More Instances of Special Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but does not completely filter one or more instances of special elements before sending it to a downstream component.
CWE-793 · Only Filtering One Instance of a Special Element
Only Filtering One Instance of a Special Element
Technical detail
CWE-793 · Only Filtering One Instance of a Special Element
Only Filtering One Instance of a Special Element
In plain English
Only Filtering One Instance of a Special Element
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but only filters a single instance of a special element before sending it to a downstream component.
CWE-794 · Incomplete Filtering of Multiple Instances of Special Elements
Incomplete Filtering of Multiple Instances of Special Elements
Technical detail
CWE-794 · Incomplete Filtering of Multiple Instances of Special Elements
Incomplete Filtering of Multiple Instances of Special Elements
In plain English
Incomplete Filtering of Multiple Instances of Special Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but does not filter all instances of a special element before sending it to a downstream component.
CWE-795 · Only Filtering Special Elements at a Specified Location
Only Filtering Special Elements at a Specified Location
Technical detail
CWE-795 · Only Filtering Special Elements at a Specified Location
Only Filtering Special Elements at a Specified Location
In plain English
Only Filtering Special Elements at a Specified Location
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but only accounts for special elements at a specified location, thereby missing remaining special elements that may exist before sending it to a downstream component.
CWE-796 · Only Filtering Special Elements Relative to a Marker
Only Filtering Special Elements Relative to a Marker
Technical detail
CWE-796 · Only Filtering Special Elements Relative to a Marker
Only Filtering Special Elements Relative to a Marker
In plain English
Only Filtering Special Elements Relative to a Marker
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but only accounts for special elements positioned relative to a marker (e.g. "at the beginning/end of a string; the second argument"), thereby missing remaining special elements that may exist before sending it to a downstream component.
CWE-797 · Only Filtering Special Elements at an Absolute Position
Only Filtering Special Elements at an Absolute Position
Technical detail
CWE-797 · Only Filtering Special Elements at an Absolute Position
Only Filtering Special Elements at an Absolute Position
In plain English
Only Filtering Special Elements at an Absolute Position
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product receives data from an upstream component, but only accounts for special elements at an absolute position (e.g. "byte number 10"), thereby missing remaining special elements that may exist before sending it to a downstream component.
CWE-798 · Use of Hard-coded Credentials
Credentials are embedded in software, firmware, or configuration distributed with the product.
Headline signal
CWE-798 · Use of Hard-coded Credentials
Credentials are embedded in software, firmware, or configuration distributed with the product.
In plain English
Credentials are embedded in software, firmware, or configuration distributed with the product.
What this can look like
An attacker discovers a built-in administrative username and password and reuses them against other devices that shipped with the same credentials.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product contains hard-coded credentials, such as a password or cryptographic key.
CWE-799 · Improper Control of Interaction Frequency
Improper Control of Interaction Frequency
Technical detail
CWE-799 · Improper Control of Interaction Frequency
Improper Control of Interaction Frequency
In plain English
Improper Control of Interaction Frequency
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly limit the number or frequency of interactions that it has with an actor, such as the number of incoming requests.
CWE-804 · Guessable CAPTCHA
Guessable CAPTCHA
Technical detail
CWE-804 · Guessable CAPTCHA
Guessable CAPTCHA
In plain English
Guessable CAPTCHA
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor.
CWE-805 · Buffer Access with Incorrect Length Value
The product handles memory in an unsafe way.
Important
CWE-805 · Buffer Access with Incorrect Length Value
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.
CWE-806 · Buffer Access Using Size of Source Buffer
The product handles memory in an unsafe way.
Important
CWE-806 · Buffer Access Using Size of Source Buffer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product uses the size of a source buffer when reading from or writing to a destination buffer, which may cause it to access memory that is outside of the bounds of the buffer.
CWE-807 · Reliance on Untrusted Inputs in a Security Decision
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-807 · Reliance on Untrusted Inputs in a Security Decision
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.
CWE-820 · Missing Synchronization
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-820 · Missing Synchronization
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource.
CWE-821 · Incorrect Synchronization
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-821 · Incorrect Synchronization
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.
CWE-822 · Untrusted Pointer Dereference
The product handles memory in an unsafe way.
Important
CWE-822 · Untrusted Pointer Dereference
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.
CWE-823 · Use of Out-of-range Pointer Offset
The product handles memory in an unsafe way.
Important
CWE-823 · Use of Out-of-range Pointer Offset
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer.
CWE-824 · Access of Uninitialized Pointer
The product handles memory in an unsafe way.
Important
CWE-824 · Access of Uninitialized Pointer
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product accesses or uses a pointer that has not been initialized.
CWE-825 · Expired Pointer Dereference
The product handles memory in an unsafe way.
Important
CWE-825 · Expired Pointer Dereference
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
CWE-826 · Premature Release of Resource During Expected Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-826 · Premature Release of Resource During Expected Lifetime
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product releases a resource that is still intended to be used by itself or another actor.
CWE-827 · Improper Control of Document Type Definition
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-827 · Improper Control of Document Type Definition
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product does not restrict a reference to a Document Type Definition (DTD) to the intended control sphere. This might allow attackers to reference arbitrary DTDs, possibly causing the product to expose files, consume excessive system resources, or execute arbitrary http requests on behalf of the attacker.
CWE-828 · Signal Handler with Functionality that is not Asynchronous-Safe
Signal Handler with Functionality that is not Asynchronous-Safe
Technical detail
CWE-828 · Signal Handler with Functionality that is not Asynchronous-Safe
Signal Handler with Functionality that is not Asynchronous-Safe
In plain English
Signal Handler with Functionality that is not Asynchronous-Safe
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product defines a signal handler that contains code sequences that are not asynchronous-safe, i.e., the functionality is not reentrant, or it can be interrupted.
CWE-829 · Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere
Technical detail
CWE-829 · Inclusion of Functionality from Untrusted Control Sphere
Inclusion of Functionality from Untrusted Control Sphere
In plain English
Inclusion of Functionality from Untrusted Control Sphere
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
CWE-830 · Inclusion of Web Functionality from an Untrusted Source
Inclusion of Web Functionality from an Untrusted Source
Technical detail
CWE-830 · Inclusion of Web Functionality from an Untrusted Source
Inclusion of Web Functionality from an Untrusted Source
In plain English
Inclusion of Web Functionality from an Untrusted Source
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the product, potentially granting total access and control of the product to the untrusted source.
CWE-831 · Signal Handler Function Associated with Multiple Signals
Signal Handler Function Associated with Multiple Signals
Technical detail
CWE-831 · Signal Handler Function Associated with Multiple Signals
Signal Handler Function Associated with Multiple Signals
In plain English
Signal Handler Function Associated with Multiple Signals
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product defines a function that is used as a handler for more than one signal.
CWE-832 · Unlock of a Resource that is not Locked
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-832 · Unlock of a Resource that is not Locked
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product attempts to unlock a resource that is not locked.
CWE-833 · Deadlock
Deadlock
Technical detail
CWE-833 · Deadlock
Deadlock
In plain English
Deadlock
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.
CWE-834 · Excessive Iteration
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-834 · Excessive Iteration
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-835 · Loop with Unreachable Exit Condition ('Infinite Loop')
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
CWE-836 · Use of Password Hash Instead of Password for Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-836 · Use of Password Hash Instead of Password for Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.
CWE-837 · Improper Enforcement of a Single, Unique Action
Improper Enforcement of a Single, Unique Action
Technical detail
CWE-837 · Improper Enforcement of a Single, Unique Action
Improper Enforcement of a Single, Unique Action
In plain English
Improper Enforcement of a Single, Unique Action
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or improperly enforces this restriction.
CWE-838 · Inappropriate Encoding for Output Context
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-838 · Inappropriate Encoding for Output Context
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.
CWE-839 · Numeric Range Comparison Without Minimum Check
Numeric Range Comparison Without Minimum Check
Technical detail
CWE-839 · Numeric Range Comparison Without Minimum Check
Numeric Range Comparison Without Minimum Check
In plain English
Numeric Range Comparison Without Minimum Check
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product checks a value to ensure that it is less than or equal to a maximum, but it does not also verify that the value is greater than or equal to the minimum.
CWE-841 · Improper Enforcement of Behavioral Workflow
Improper Enforcement of Behavioral Workflow
Technical detail
CWE-841 · Improper Enforcement of Behavioral Workflow
Improper Enforcement of Behavioral Workflow
In plain English
Improper Enforcement of Behavioral Workflow
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product supports a session in which more than one behavior must be performed by an actor, but it does not properly ensure that the actor performs the behaviors in the required sequence.
CWE-842 · Placement of User into Incorrect Group
Placement of User into Incorrect Group
Technical detail
CWE-842 · Placement of User into Incorrect Group
Placement of User into Incorrect Group
In plain English
Placement of User into Incorrect Group
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product or the administrator places a user into an incorrect group.
CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')
The product handles memory in an unsafe way.
Important
CWE-843 · Access of Resource Using Incompatible Type ('Type Confusion')
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.
CWE-862 · Missing Authorization
A sensitive action lacks an authorization check.
Headline signal
CWE-862 · Missing Authorization
A sensitive action lacks an authorization check.
In plain English
A sensitive action lacks an authorization check.
What this can look like
A logged-in ordinary user directly calls an administrative operation because the application never verifies that the user has administrative rights.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-863 · Incorrect Authorization
An authorization check exists but makes the wrong decision.
Headline signal
CWE-863 · Incorrect Authorization
An authorization check exists but makes the wrong decision.
In plain English
An authorization check exists but makes the wrong decision.
What this can look like
A permission rule checks the wrong object or role and unintentionally allows one user to perform another user’s privileged action.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.
CWE-908 · Use of Uninitialized Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-908 · Use of Uninitialized Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses or accesses a resource that has not been initialized.
CWE-909 · Missing Initialization of Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-909 · Missing Initialization of Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not initialize a critical resource.
CWE-910 · Use of Expired File Descriptor
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-910 · Use of Expired File Descriptor
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses or accesses a file descriptor after it has been closed.
CWE-911 · Improper Update of Reference Count
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-911 · Improper Update of Reference Count
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.
CWE-912 · Hidden Functionality
The product contains functionality that is not expected or disclosed to its users.
Headline signal
CWE-912 · Hidden Functionality
The product contains functionality that is not expected or disclosed to its users.
In plain English
The product contains functionality that is not expected or disclosed to its users.
What this can look like
An undocumented service, account, command, or maintenance feature provides capabilities that are absent from the normal interface and documentation.
An undocumented account, command, trigger, or communication path provides capabilities that are absent from the normal product interface.
A component appears to perform a legitimate function while secretly collecting information, bypassing controls, or activating hidden behavior.
MITRE description from the synchronized CWE record
The product contains functionality that is not documented, not part of the specification, and not accessible through an interface or command sequence that is obvious to the product's users or administrators.
CWE-913 · Improper Control of Dynamically-Managed Code Resources
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-913 · Improper Control of Dynamically-Managed Code Resources
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product does not properly restrict reading from or writing to dynamically-managed code resources such as variables, objects, classes, attributes, functions, or executable instructions or statements.
CWE-914 · Improper Control of Dynamically-Identified Variables
Improper Control of Dynamically-Identified Variables
Technical detail
CWE-914 · Improper Control of Dynamically-Identified Variables
Improper Control of Dynamically-Identified Variables
In plain English
Improper Control of Dynamically-Identified Variables
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly restrict reading from or writing to dynamically-identified variables.
CWE-915 · Improperly Controlled Modification of Dynamically-Determined Object Attributes
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-915 · Improperly Controlled Modification of Dynamically-Determined Object Attributes
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.
CWE-916 · Use of Password Hash With Insufficient Computational Effort
Passwords are hashed using an unsuitable or insufficiently expensive method.
Important
CWE-916 · Use of Password Hash With Insufficient Computational Effort
Passwords are hashed using an unsuitable or insufficiently expensive method.
In plain English
Passwords are hashed using an unsuitable or insufficiently expensive method.
What this can look like
After obtaining a password database, an attacker can test password guesses much faster than they could against a modern password-hashing scheme.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product generates a hash for a password, but it uses a scheme that does not provide a sufficient level of computational effort that would make password cracking attacks infeasible or expensive.
CWE-917 · Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-917 · Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.
CWE-918 · Server-Side Request Forgery (SSRF)
An attacker can make the server initiate requests to unintended destinations.
Important
CWE-918 · Server-Side Request Forgery (SSRF)
An attacker can make the server initiate requests to unintended destinations.
In plain English
An attacker can make the server initiate requests to unintended destinations.
What this can look like
A URL-fetching feature is pointed at an internal-only service, allowing the attacker to reach resources that are not directly exposed to them.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
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.
CWE-920 · Improper Restriction of Power Consumption
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-920 · Improper Restriction of Power Consumption
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product operates in an environment in which power is a limited resource that cannot be automatically replenished, but the product does not properly restrict the amount of power that its operation consumes.
CWE-921 · Storage of Sensitive Data in a Mechanism without Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-921 · Storage of Sensitive Data in a Mechanism without Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product stores sensitive information in a file system or device that does not have built-in access control.
CWE-922 · Insecure Storage of Sensitive Information
The product can expose information beyond the audience that should receive it.
Important
CWE-922 · Insecure Storage of Sensitive Information
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product stores sensitive information without properly limiting read or write access by unauthorized actors.
CWE-923 · Improper Restriction of Communication Channel to Intended Endpoints
Improper Restriction of Communication Channel to Intended Endpoints
Technical detail
CWE-923 · Improper Restriction of Communication Channel to Intended Endpoints
Improper Restriction of Communication Channel to Intended Endpoints
In plain English
Improper Restriction of Communication Channel to Intended Endpoints
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.
CWE-924 · Improper Enforcement of Message Integrity During Transmission in a Communication Channel
Improper Enforcement of Message Integrity During Transmission in a Communication Channel
Technical detail
CWE-924 · Improper Enforcement of Message Integrity During Transmission in a Communication Channel
Improper Enforcement of Message Integrity During Transmission in a Communication Channel
In plain English
Improper Enforcement of Message Integrity During Transmission in a Communication Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission.
CWE-925 · Improper Verification of Intent by Broadcast Receiver
Improper Verification of Intent by Broadcast Receiver
Technical detail
CWE-925 · Improper Verification of Intent by Broadcast Receiver
Improper Verification of Intent by Broadcast Receiver
In plain English
Improper Verification of Intent by Broadcast Receiver
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.
CWE-926 · Improper Export of Android Application Components
Improper Export of Android Application Components
Technical detail
CWE-926 · Improper Export of Android Application Components
Improper Export of Android Application Components
In plain English
Improper Export of Android Application Components
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.
CWE-927 · Use of Implicit Intent for Sensitive Communication
Use of Implicit Intent for Sensitive Communication
Technical detail
CWE-927 · Use of Implicit Intent for Sensitive Communication
Use of Implicit Intent for Sensitive Communication
In plain English
Use of Implicit Intent for Sensitive Communication
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The Android application uses an implicit intent for transmitting sensitive data to other applications.
CWE-939 · Improper Authorization in Handler for Custom URL Scheme
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-939 · Improper Authorization in Handler for Custom URL Scheme
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses a handler for a custom URL scheme, but it does not properly restrict which actors can invoke the handler using the scheme.
CWE-940 · Improper Verification of Source of a Communication Channel
Improper Verification of Source of a Communication Channel
Technical detail
CWE-940 · Improper Verification of Source of a Communication Channel
Improper Verification of Source of a Communication Channel
In plain English
Improper Verification of Source of a Communication Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product establishes a communication channel to handle an incoming request that has been initiated by an actor, but it does not properly verify that the request is coming from the expected origin.
CWE-941 · Incorrectly Specified Destination in a Communication Channel
Incorrectly Specified Destination in a Communication Channel
Technical detail
CWE-941 · Incorrectly Specified Destination in a Communication Channel
Incorrectly Specified Destination in a Communication Channel
In plain English
Incorrectly Specified Destination in a Communication Channel
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product creates a communication channel to initiate an outgoing request to an actor, but it does not correctly specify the intended destination for that actor.
CWE-942 · Permissive Cross-domain Security Policy with Untrusted Domains
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-942 · Permissive Cross-domain Security Policy with Untrusted Domains
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
CWE-943 · Improper Neutralization of Special Elements in Data Query Logic
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-943 · Improper Neutralization of Special Elements in Data Query Logic
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
CWE-1004 · Sensitive Cookie Without 'HttpOnly' Flag
The product can expose information beyond the audience that should receive it.
Important
CWE-1004 · Sensitive Cookie Without 'HttpOnly' Flag
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.
CWE-1007 · Insufficient Visual Distinction of Homoglyphs Presented to User
Insufficient Visual Distinction of Homoglyphs Presented to User
Technical detail
CWE-1007 · Insufficient Visual Distinction of Homoglyphs Presented to User
Insufficient Visual Distinction of Homoglyphs Presented to User
In plain English
Insufficient Visual Distinction of Homoglyphs Presented to User
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product displays information or identifiers to a user, but the display mechanism does not make it easy for the user to distinguish between visually similar or identical glyphs (homoglyphs), which may cause the user to misinterpret a glyph and perform an unintended, insecure action.
CWE-1021 · Improper Restriction of Rendered UI Layers or Frames
Improper Restriction of Rendered UI Layers or Frames
Technical detail
CWE-1021 · Improper Restriction of Rendered UI Layers or Frames
Improper Restriction of Rendered UI Layers or Frames
In plain English
Improper Restriction of Rendered UI Layers or Frames
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain.
CWE-1022 · Use of Web Link to Untrusted Target with window.opener Access
Use of Web Link to Untrusted Target with window.opener Access
Technical detail
CWE-1022 · Use of Web Link to Untrusted Target with window.opener Access
Use of Web Link to Untrusted Target with window.opener Access
In plain English
Use of Web Link to Untrusted Target with window.opener Access
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The web application produces links to untrusted external sites outside of its sphere of control, but it does not properly prevent the external site from modifying security-critical properties of the window.opener object, such as the location property.
CWE-1023 · Incomplete Comparison with Missing Factors
Incomplete Comparison with Missing Factors
Technical detail
CWE-1023 · Incomplete Comparison with Missing Factors
Incomplete Comparison with Missing Factors
In plain English
Incomplete Comparison with Missing Factors
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs a comparison between entities that must consider multiple factors or characteristics of each entity, but the comparison does not include one or more of these factors.
CWE-1024 · Comparison of Incompatible Types
Comparison of Incompatible Types
Technical detail
CWE-1024 · Comparison of Incompatible Types
Comparison of Incompatible Types
In plain English
Comparison of Incompatible Types
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs a comparison between two entities, but the entities are of different, incompatible types that cannot be guaranteed to provide correct results when they are directly compared.
CWE-1025 · Comparison Using Wrong Factors
Comparison Using Wrong Factors
Technical detail
CWE-1025 · Comparison Using Wrong Factors
Comparison Using Wrong Factors
In plain English
Comparison Using Wrong Factors
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code performs a comparison between two entities, but the comparison examines the wrong factors or characteristics of the entities, which can lead to incorrect results and resultant weaknesses.
CWE-1037 · Processor Optimization Removal or Modification of Security-critical Code
Processor Optimization Removal or Modification of Security-critical Code
Technical detail
CWE-1037 · Processor Optimization Removal or Modification of Security-critical Code
Processor Optimization Removal or Modification of Security-critical Code
In plain English
Processor Optimization Removal or Modification of Security-critical Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The developer builds a security-critical protection mechanism into the software, but the processor optimizes the execution of the program such that the mechanism is removed or modified.
CWE-1038 · Insecure Automated Optimizations
Insecure Automated Optimizations
Technical detail
CWE-1038 · Insecure Automated Optimizations
Insecure Automated Optimizations
In plain English
Insecure Automated Optimizations
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a mechanism that automatically optimizes code, e.g. to improve a characteristic such as performance, but the optimizations can have an unintended side effect that might violate an intended security assumption.
CWE-1039 · Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1039 · Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses an automated mechanism such as machine learning to recognize complex data inputs (e.g. image or audio) as a particular concept or category, but it does not properly detect or handle inputs that have been modified or constructed in a way that causes the mechanism to detect a different, incorrect concept.
CWE-1041 · Use of Redundant Code
Use of Redundant Code
Technical detail
CWE-1041 · Use of Redundant Code
Use of Redundant Code
In plain English
Use of Redundant Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has multiple functions, methods, procedures, macros, etc. that contain the same code.
CWE-1042 · Static Member Data Element outside of a Singleton Class Element
Static Member Data Element outside of a Singleton Class Element
Technical detail
CWE-1042 · Static Member Data Element outside of a Singleton Class Element
Static Member Data Element outside of a Singleton Class Element
In plain English
Static Member Data Element outside of a Singleton Class Element
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains a member element that is declared as static (but not final), in which its parent class element is not a singleton class - that is, a class element that can be used only once in the 'to' association of a Create action.
CWE-1043 · Data Element Aggregating an Excessively Large Number of Non-Primitive Elements
Data Element Aggregating an Excessively Large Number of Non-Primitive Elements
Technical detail
CWE-1043 · Data Element Aggregating an Excessively Large Number of Non-Primitive Elements
Data Element Aggregating an Excessively Large Number of Non-Primitive Elements
In plain English
Data Element Aggregating an Excessively Large Number of Non-Primitive Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a data element that has an excessively large number of sub-elements with non-primitive data types such as structures or aggregated objects.
CWE-1044 · Architecture with Number of Horizontal Layers Outside of Expected Range
Architecture with Number of Horizontal Layers Outside of Expected Range
Technical detail
CWE-1044 · Architecture with Number of Horizontal Layers Outside of Expected Range
Architecture with Number of Horizontal Layers Outside of Expected Range
In plain English
Architecture with Number of Horizontal Layers Outside of Expected Range
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product's architecture contains too many - or too few - horizontal layers.
CWE-1045 · Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor
Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor
Technical detail
CWE-1045 · Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor
Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor
In plain English
Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A parent class has a virtual destructor method, but the parent has a child class that does not have a virtual destructor.
CWE-1046 · Creation of Immutable Text Using String Concatenation
Creation of Immutable Text Using String Concatenation
Technical detail
CWE-1046 · Creation of Immutable Text Using String Concatenation
Creation of Immutable Text Using String Concatenation
In plain English
Creation of Immutable Text Using String Concatenation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product creates an immutable text string using string concatenation operations.
CWE-1047 · Modules with Circular Dependencies
Modules with Circular Dependencies
Technical detail
CWE-1047 · Modules with Circular Dependencies
Modules with Circular Dependencies
In plain English
Modules with Circular Dependencies
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains modules in which one module has references that cycle back to itself, i.e., there are circular dependencies.
CWE-1048 · Invokable Control Element with Large Number of Outward Calls
Invokable Control Element with Large Number of Outward Calls
Technical detail
CWE-1048 · Invokable Control Element with Large Number of Outward Calls
Invokable Control Element with Large Number of Outward Calls
In plain English
Invokable Control Element with Large Number of Outward Calls
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains callable control elements that contain an excessively large number of references to other application objects external to the context of the callable, i.e. a Fan-Out value that is excessively large.
CWE-1049 · Excessive Data Query Operations in a Large Data Table
Excessive Data Query Operations in a Large Data Table
Technical detail
CWE-1049 · Excessive Data Query Operations in a Large Data Table
Excessive Data Query Operations in a Large Data Table
In plain English
Excessive Data Query Operations in a Large Data Table
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs a data query with a large number of joins and sub-queries on a large data table.
CWE-1050 · Excessive Platform Resource Consumption within a Loop
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-1050 · Excessive Platform Resource Consumption within a Loop
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product has a loop body or loop condition that contains a control element that directly or indirectly consumes platform resources, e.g. messaging, sessions, locks, or file descriptors.
CWE-1051 · Initialization with Hard-Coded Network Resource Configuration Data
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1051 · Initialization with Hard-Coded Network Resource Configuration Data
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product initializes data using hard-coded values that act as network resource identifiers.
CWE-1052 · Excessive Use of Hard-Coded Literals in Initialization
Excessive Use of Hard-Coded Literals in Initialization
Technical detail
CWE-1052 · Excessive Use of Hard-Coded Literals in Initialization
Excessive Use of Hard-Coded Literals in Initialization
In plain English
Excessive Use of Hard-Coded Literals in Initialization
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product initializes a data element using a hard-coded literal that is not a simple integer or static constant element.
CWE-1053 · Missing Documentation for Design
Missing Documentation for Design
Technical detail
CWE-1053 · Missing Documentation for Design
Missing Documentation for Design
In plain English
Missing Documentation for Design
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not have documentation that represents how it is designed.
CWE-1054 · Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer
Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer
Technical detail
CWE-1054 · Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer
Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer
In plain English
Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code at one architectural layer invokes code that resides at a deeper layer than the adjacent layer, i.e., the invocation skips at least one layer, and the invoked code is not part of a vertical utility layer that can be referenced from any horizontal layer.
CWE-1055 · Multiple Inheritance from Concrete Classes
Multiple Inheritance from Concrete Classes
Technical detail
CWE-1055 · Multiple Inheritance from Concrete Classes
Multiple Inheritance from Concrete Classes
In plain English
Multiple Inheritance from Concrete Classes
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a class with inheritance from more than one concrete class.
CWE-1056 · Invokable Control Element with Variadic Parameters
Invokable Control Element with Variadic Parameters
Technical detail
CWE-1056 · Invokable Control Element with Variadic Parameters
Invokable Control Element with Variadic Parameters
In plain English
Invokable Control Element with Variadic Parameters
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A named-callable or method control element has a signature that supports a variable (variadic) number of parameters or arguments.
CWE-1057 · Data Access Operations Outside of Expected Data Manager Component
Data Access Operations Outside of Expected Data Manager Component
Technical detail
CWE-1057 · Data Access Operations Outside of Expected Data Manager Component
Data Access Operations Outside of Expected Data Manager Component
In plain English
Data Access Operations Outside of Expected Data Manager Component
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a dedicated, central data manager component as required by design, but it contains code that performs data-access operations that do not use this data manager.
CWE-1058 · Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
Technical detail
CWE-1058 · Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
In plain English
Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains a function or method that operates in a multi-threaded environment but owns an unsafe non-final static storable or member data element.
CWE-1059 · Insufficient Technical Documentation
Insufficient Technical Documentation
Technical detail
CWE-1059 · Insufficient Technical Documentation
Insufficient Technical Documentation
In plain English
Insufficient Technical Documentation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not contain sufficient technical or engineering documentation (whether on paper or in electronic form) that contains descriptions of all the relevant software/hardware elements of the product, such as its usage, structure, architectural components, interfaces, design, implementation, configuration, operation, etc.
CWE-1060 · Excessive Number of Inefficient Server-Side Data Accesses
Excessive Number of Inefficient Server-Side Data Accesses
Technical detail
CWE-1060 · Excessive Number of Inefficient Server-Side Data Accesses
Excessive Number of Inefficient Server-Side Data Accesses
In plain English
Excessive Number of Inefficient Server-Side Data Accesses
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs too many data queries without using efficient data processing functionality such as stored procedures.
CWE-1061 · Insufficient Encapsulation
Insufficient Encapsulation
Technical detail
CWE-1061 · Insufficient Encapsulation
Insufficient Encapsulation
In plain English
Insufficient Encapsulation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not sufficiently hide the internal representation and implementation details of data or methods, which might allow external components or modules to modify data unexpectedly, invoke unexpected functionality, or introduce dependencies that the programmer did not intend.
CWE-1062 · Parent Class with References to Child Class
Parent Class with References to Child Class
Technical detail
CWE-1062 · Parent Class with References to Child Class
Parent Class with References to Child Class
In plain English
Parent Class with References to Child Class
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code has a parent class that contains references to a child class, its methods, or its members.
CWE-1063 · Creation of Class Instance within a Static Code Block
Creation of Class Instance within a Static Code Block
Technical detail
CWE-1063 · Creation of Class Instance within a Static Code Block
Creation of Class Instance within a Static Code Block
In plain English
Creation of Class Instance within a Static Code Block
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A static code block creates an instance of a class.
CWE-1064 · Invokable Control Element with Signature Containing an Excessive Number of Parameters
Invokable Control Element with Signature Containing an Excessive Number of Parameters
Technical detail
CWE-1064 · Invokable Control Element with Signature Containing an Excessive Number of Parameters
Invokable Control Element with Signature Containing an Excessive Number of Parameters
In plain English
Invokable Control Element with Signature Containing an Excessive Number of Parameters
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a function, subroutine, or method whose signature has an unnecessarily large number of parameters/arguments.
CWE-1065 · Runtime Resource Management Control Element in a Component Built to Run on Application Servers
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1065 · Runtime Resource Management Control Element in a Component Built to Run on Application Servers
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses deployed components from application servers, but it also uses low-level functions/methods for management of resources, instead of the API provided by the application server.
CWE-1066 · Missing Serialization Control Element
Missing Serialization Control Element
Technical detail
CWE-1066 · Missing Serialization Control Element
Missing Serialization Control Element
In plain English
Missing Serialization Control Element
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a serializable data element that does not have an associated serialization method.
CWE-1067 · Excessive Execution of Sequential Searches of Data Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1067 · Excessive Execution of Sequential Searches of Data Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A search, filter, or login value changes the meaning of a database query and exposes or modifies records outside the intended scope.
An application builds a query from untrusted text, letting crafted input affect the query structure rather than only the supplied value.
MITRE description from the synchronized CWE record
The product contains a data query against an SQL table or view that is configured in a way that does not utilize an index and may cause sequential searches to be performed.
CWE-1068 · Inconsistency Between Implementation and Documented Design
Inconsistency Between Implementation and Documented Design
Technical detail
CWE-1068 · Inconsistency Between Implementation and Documented Design
Inconsistency Between Implementation and Documented Design
In plain English
Inconsistency Between Implementation and Documented Design
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The implementation of the product is not consistent with the design as described within the relevant documentation.
CWE-1069 · Empty Exception Block
Empty Exception Block
Technical detail
CWE-1069 · Empty Exception Block
Empty Exception Block
In plain English
Empty Exception Block
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.
CWE-1070 · Serializable Data Element Containing non-Serializable Item Elements
Serializable Data Element Containing non-Serializable Item Elements
Technical detail
CWE-1070 · Serializable Data Element Containing non-Serializable Item Elements
Serializable Data Element Containing non-Serializable Item Elements
In plain English
Serializable Data Element Containing non-Serializable Item Elements
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a serializable, storable data element such as a field or member, but the data element contains member elements that are not serializable.
CWE-1071 · Empty Code Block
Empty Code Block
Technical detail
CWE-1071 · Empty Code Block
Empty Code Block
In plain English
Empty Code Block
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code contains a block that does not contain any code, i.e., the block is empty.
CWE-1072 · Data Resource Access without Use of Connection Pooling
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1072 · Data Resource Access without Use of Connection Pooling
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product accesses a data resource through a database without using a connection pooling capability.
CWE-1073 · Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1073 · Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A search, filter, or login value changes the meaning of a database query and exposes or modifies records outside the intended scope.
An application builds a query from untrusted text, letting crafted input affect the query structure rather than only the supplied value.
MITRE description from the synchronized CWE record
The product contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities.
CWE-1074 · Class with Excessively Deep Inheritance
Class with Excessively Deep Inheritance
Technical detail
CWE-1074 · Class with Excessively Deep Inheritance
Class with Excessively Deep Inheritance
In plain English
Class with Excessively Deep Inheritance
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A class has an inheritance level that is too high, i.e., it has a large number of parent classes.
CWE-1075 · Unconditional Control Flow Transfer outside of Switch Block
Unconditional Control Flow Transfer outside of Switch Block
Technical detail
CWE-1075 · Unconditional Control Flow Transfer outside of Switch Block
Unconditional Control Flow Transfer outside of Switch Block
In plain English
Unconditional Control Flow Transfer outside of Switch Block
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs unconditional control transfer (such as a "goto") in code outside of a branching structure such as a switch block.
CWE-1076 · Insufficient Adherence to Expected Conventions
Insufficient Adherence to Expected Conventions
Technical detail
CWE-1076 · Insufficient Adherence to Expected Conventions
Insufficient Adherence to Expected Conventions
In plain English
Insufficient Adherence to Expected Conventions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product's architecture, source code, design, documentation, or other artifact does not follow required conventions.
CWE-1077 · Floating Point Comparison with Incorrect Operator
Floating Point Comparison with Incorrect Operator
Technical detail
CWE-1077 · Floating Point Comparison with Incorrect Operator
Floating Point Comparison with Incorrect Operator
In plain English
Floating Point Comparison with Incorrect Operator
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code performs a comparison such as an equality test between two float (floating point) values, but it uses comparison operators that do not account for the possibility of loss of precision.
CWE-1078 · Inappropriate Source Code Style or Formatting
Inappropriate Source Code Style or Formatting
Technical detail
CWE-1078 · Inappropriate Source Code Style or Formatting
Inappropriate Source Code Style or Formatting
In plain English
Inappropriate Source Code Style or Formatting
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code does not follow desired style or formatting for indentation, white space, comments, etc.
CWE-1079 · Parent Class without Virtual Destructor Method
Parent Class without Virtual Destructor Method
Technical detail
CWE-1079 · Parent Class without Virtual Destructor Method
Parent Class without Virtual Destructor Method
In plain English
Parent Class without Virtual Destructor Method
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A parent class contains one or more child classes, but the parent class does not have a virtual destructor method.
CWE-1080 · Source Code File with Excessive Number of Lines of Code
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-1080 · Source Code File with Excessive Number of Lines of Code
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
A source code file has too many lines of code.
CWE-1082 · Class Instance Self Destruction Control Element
Class Instance Self Destruction Control Element
Technical detail
CWE-1082 · Class Instance Self Destruction Control Element
Class Instance Self Destruction Control Element
In plain English
Class Instance Self Destruction Control Element
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains a class instance that calls the method or function to delete or destroy itself.
CWE-1083 · Data Access from Outside Expected Data Manager Component
Data Access from Outside Expected Data Manager Component
Technical detail
CWE-1083 · Data Access from Outside Expected Data Manager Component
Data Access from Outside Expected Data Manager Component
In plain English
Data Access from Outside Expected Data Manager Component
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A search, filter, or login value changes the meaning of a database query and exposes or modifies records outside the intended scope.
An application builds a query from untrusted text, letting crafted input affect the query structure rather than only the supplied value.
MITRE description from the synchronized CWE record
The product is intended to manage data access through a particular data manager component such as a relational or non-SQL database, but it contains code that performs data access operations without using that component.
CWE-1084 · Invokable Control Element with Excessive File or Data Access Operations
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-1084 · Invokable Control Element with Excessive File or Data Access Operations
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
A function or method contains too many operations that utilize a data manager or file resource.
CWE-1085 · Invokable Control Element with Excessive Volume of Commented-out Code
Invokable Control Element with Excessive Volume of Commented-out Code
Technical detail
CWE-1085 · Invokable Control Element with Excessive Volume of Commented-out Code
Invokable Control Element with Excessive Volume of Commented-out Code
In plain English
Invokable Control Element with Excessive Volume of Commented-out Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A function, method, procedure, etc. contains an excessive amount of code that has been commented out within its body.
CWE-1086 · Class with Excessive Number of Child Classes
Class with Excessive Number of Child Classes
Technical detail
CWE-1086 · Class with Excessive Number of Child Classes
Class with Excessive Number of Child Classes
In plain English
Class with Excessive Number of Child Classes
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A class contains an unnecessarily large number of children.
CWE-1087 · Class with Virtual Method without a Virtual Destructor
Class with Virtual Method without a Virtual Destructor
Technical detail
CWE-1087 · Class with Virtual Method without a Virtual Destructor
Class with Virtual Method without a Virtual Destructor
In plain English
Class with Virtual Method without a Virtual Destructor
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A class contains a virtual method, but the method does not have an associated virtual destructor.
CWE-1088 · Synchronous Access of Remote Resource without Timeout
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1088 · Synchronous Access of Remote Resource without Timeout
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.
CWE-1089 · Large Data Table with Excessive Number of Indices
Large Data Table with Excessive Number of Indices
Technical detail
CWE-1089 · Large Data Table with Excessive Number of Indices
Large Data Table with Excessive Number of Indices
In plain English
Large Data Table with Excessive Number of Indices
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a large data table that contains an excessively large number of indices.
CWE-1090 · Method Containing Access of a Member Element from Another Class
Method Containing Access of a Member Element from Another Class
Technical detail
CWE-1090 · Method Containing Access of a Member Element from Another Class
Method Containing Access of a Member Element from Another Class
In plain English
Method Containing Access of a Member Element from Another Class
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A method for a class performs an operation that directly accesses a member element from another class.
CWE-1091 · Use of Object without Invoking Destructor Method
Use of Object without Invoking Destructor Method
Technical detail
CWE-1091 · Use of Object without Invoking Destructor Method
Use of Object without Invoking Destructor Method
In plain English
Use of Object without Invoking Destructor Method
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains a method that accesses an object but does not later invoke the element's associated finalize/destructor method.
CWE-1092 · Use of Same Invokable Control Element in Multiple Architectural Layers
Use of Same Invokable Control Element in Multiple Architectural Layers
Technical detail
CWE-1092 · Use of Same Invokable Control Element in Multiple Architectural Layers
Use of Same Invokable Control Element in Multiple Architectural Layers
In plain English
Use of Same Invokable Control Element in Multiple Architectural Layers
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses the same control element across multiple architectural layers.
CWE-1093 · Excessively Complex Data Representation
Excessively Complex Data Representation
Technical detail
CWE-1093 · Excessively Complex Data Representation
Excessively Complex Data Representation
In plain English
Excessively Complex Data Representation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses an unnecessarily complex internal representation for its data structures or interrelationships between those structures.
CWE-1094 · Excessive Index Range Scan for a Data Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1094 · Excessive Index Range Scan for a Data Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product contains an index range scan for a large data table, but the scan can cover a large number of rows.
CWE-1095 · Loop Condition Value Update within the Loop
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1095 · Loop Condition Value Update within the Loop
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses a loop with a control flow condition based on a value that is updated within the body of the loop.
CWE-1096 · Singleton Class Instance Creation without Proper Locking or Synchronization
Singleton Class Instance Creation without Proper Locking or Synchronization
Technical detail
CWE-1096 · Singleton Class Instance Creation without Proper Locking or Synchronization
Singleton Class Instance Creation without Proper Locking or Synchronization
In plain English
Singleton Class Instance Creation without Proper Locking or Synchronization
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product implements a Singleton design pattern but does not use appropriate locking or other synchronization mechanism to ensure that the singleton class is only instantiated once.
CWE-1097 · Persistent Storable Data Element without Associated Comparison Control Element
Persistent Storable Data Element without Associated Comparison Control Element
Technical detail
CWE-1097 · Persistent Storable Data Element without Associated Comparison Control Element
Persistent Storable Data Element without Associated Comparison Control Element
In plain English
Persistent Storable Data Element without Associated Comparison Control Element
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a storable data element that does not have all of the associated functions or methods that are necessary to support comparison.
CWE-1098 · Data Element containing Pointer Item without Proper Copy Control Element
The product handles memory in an unsafe way.
Important
CWE-1098 · Data Element containing Pointer Item without Proper Copy Control Element
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The code contains a data element with a pointer that does not have an associated copy or constructor method.
CWE-1099 · Inconsistent Naming Conventions for Identifiers
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-1099 · Inconsistent Naming Conventions for Identifiers
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product's code, documentation, or other artifacts do not consistently use the same naming conventions for variables, callables, groups of related callables, I/O capabilities, data types, file names, or similar types of elements.
CWE-1100 · Insufficient Isolation of System-Dependent Functions
Insufficient Isolation of System-Dependent Functions
Technical detail
CWE-1100 · Insufficient Isolation of System-Dependent Functions
Insufficient Isolation of System-Dependent Functions
In plain English
Insufficient Isolation of System-Dependent Functions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product or code does not isolate system-dependent functionality into separate standalone modules.
CWE-1101 · Reliance on Runtime Component in Generated Code
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-1101 · Reliance on Runtime Component in Generated Code
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product uses automatically-generated code that cannot be executed without a specific runtime support component.
CWE-1102 · Reliance on Machine-Dependent Data Representation
Reliance on Machine-Dependent Data Representation
Technical detail
CWE-1102 · Reliance on Machine-Dependent Data Representation
Reliance on Machine-Dependent Data Representation
In plain English
Reliance on Machine-Dependent Data Representation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, OSes, or other physical components.
CWE-1103 · Use of Platform-Dependent Third Party Components
Use of Platform-Dependent Third Party Components
Technical detail
CWE-1103 · Use of Platform-Dependent Third Party Components
Use of Platform-Dependent Third Party Components
In plain English
Use of Platform-Dependent Third Party Components
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product relies on third-party components that do not provide equivalent functionality across all desirable platforms.
CWE-1104 · Use of Unmaintained Third Party Components
Use of Unmaintained Third Party Components
Technical detail
CWE-1104 · Use of Unmaintained Third Party Components
Use of Unmaintained Third Party Components
In plain English
Use of Unmaintained Third Party Components
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product relies on third-party components that are not actively supported or maintained by the original developer or a trusted proxy for the original developer.
CWE-1105 · Insufficient Encapsulation of Machine-Dependent Functionality
Insufficient Encapsulation of Machine-Dependent Functionality
Technical detail
CWE-1105 · Insufficient Encapsulation of Machine-Dependent Functionality
Insufficient Encapsulation of Machine-Dependent Functionality
In plain English
Insufficient Encapsulation of Machine-Dependent Functionality
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product or code uses machine-dependent functionality, but it does not sufficiently encapsulate or isolate this functionality from the rest of the code.
CWE-1106 · Insufficient Use of Symbolic Constants
Insufficient Use of Symbolic Constants
Technical detail
CWE-1106 · Insufficient Use of Symbolic Constants
Insufficient Use of Symbolic Constants
In plain English
Insufficient Use of Symbolic Constants
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code uses literal constants that may need to change or evolve over time, instead of using symbolic constants.
CWE-1107 · Insufficient Isolation of Symbolic Constant Definitions
Insufficient Isolation of Symbolic Constant Definitions
Technical detail
CWE-1107 · Insufficient Isolation of Symbolic Constant Definitions
Insufficient Isolation of Symbolic Constant Definitions
In plain English
Insufficient Isolation of Symbolic Constant Definitions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code uses symbolic constants, but it does not sufficiently place the definitions of these constants into a more centralized or isolated location.
CWE-1108 · Excessive Reliance on Global Variables
Excessive Reliance on Global Variables
Technical detail
CWE-1108 · Excessive Reliance on Global Variables
Excessive Reliance on Global Variables
In plain English
Excessive Reliance on Global Variables
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code is structured in a way that relies too much on using or setting global variables throughout various points in the code, instead of preserving the associated information in a narrower, more local context.
CWE-1109 · Use of Same Variable for Multiple Purposes
Use of Same Variable for Multiple Purposes
Technical detail
CWE-1109 · Use of Same Variable for Multiple Purposes
Use of Same Variable for Multiple Purposes
In plain English
Use of Same Variable for Multiple Purposes
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains a callable, block, or other code element in which the same variable is used to control more than one unique task or store more than one instance of data.
CWE-1110 · Incomplete Design Documentation
Incomplete Design Documentation
Technical detail
CWE-1110 · Incomplete Design Documentation
Incomplete Design Documentation
In plain English
Incomplete Design Documentation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product's design documentation does not adequately describe control flow, data flow, system initialization, relationships between tasks, components, rationales, or other important aspects of the design.
CWE-1111 · Incomplete I/O Documentation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1111 · Incomplete I/O Documentation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product's documentation does not adequately define inputs, outputs, or system/software interfaces.
CWE-1112 · Incomplete Documentation of Program Execution
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-1112 · Incomplete Documentation of Program Execution
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The document does not fully define all mechanisms that are used to control or influence how product-specific programs are executed.
CWE-1113 · Inappropriate Comment Style
Inappropriate Comment Style
Technical detail
CWE-1113 · Inappropriate Comment Style
Inappropriate Comment Style
In plain English
Inappropriate Comment Style
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code uses comment styles or formats that are inconsistent or do not follow expected standards for the product.
CWE-1114 · Inappropriate Whitespace Style
Inappropriate Whitespace Style
Technical detail
CWE-1114 · Inappropriate Whitespace Style
Inappropriate Whitespace Style
In plain English
Inappropriate Whitespace Style
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code contains whitespace that is inconsistent across the code or does not follow expected standards for the product.
CWE-1115 · Source Code Element without Standard Prologue
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-1115 · Source Code Element without Standard Prologue
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The source code contains elements such as source files that do not consistently provide a prologue or header that has been standardized for the project.
CWE-1116 · Inaccurate Source Code Comments
Inaccurate Source Code Comments
Technical detail
CWE-1116 · Inaccurate Source Code Comments
Inaccurate Source Code Comments
In plain English
Inaccurate Source Code Comments
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code contains comments that do not accurately describe or explain aspects of the portion of the code with which the comment is associated.
CWE-1117 · Callable with Insufficient Behavioral Summary
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1117 · Callable with Insufficient Behavioral Summary
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The code contains a function or method whose signature and/or associated inline documentation does not sufficiently describe the callable's inputs, outputs, side effects, assumptions, or return codes.
CWE-1118 · Insufficient Documentation of Error Handling Techniques
Insufficient Documentation of Error Handling Techniques
Technical detail
CWE-1118 · Insufficient Documentation of Error Handling Techniques
Insufficient Documentation of Error Handling Techniques
In plain English
Insufficient Documentation of Error Handling Techniques
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The documentation does not sufficiently describe the techniques that are used for error handling, exception processing, or similar mechanisms.
CWE-1119 · Excessive Use of Unconditional Branching
Excessive Use of Unconditional Branching
Technical detail
CWE-1119 · Excessive Use of Unconditional Branching
Excessive Use of Unconditional Branching
In plain English
Excessive Use of Unconditional Branching
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses too many unconditional branches (such as "goto").
CWE-1120 · Excessive Code Complexity
Excessive Code Complexity
Technical detail
CWE-1120 · Excessive Code Complexity
Excessive Code Complexity
In plain English
Excessive Code Complexity
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code is too complex, as calculated using a well-defined, quantitative measure.
CWE-1121 · Excessive McCabe Cyclomatic Complexity
Excessive McCabe Cyclomatic Complexity
Technical detail
CWE-1121 · Excessive McCabe Cyclomatic Complexity
Excessive McCabe Cyclomatic Complexity
In plain English
Excessive McCabe Cyclomatic Complexity
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains McCabe cyclomatic complexity that exceeds a desirable maximum.
CWE-1122 · Excessive Halstead Complexity
Excessive Halstead Complexity
Technical detail
CWE-1122 · Excessive Halstead Complexity
Excessive Halstead Complexity
In plain English
Excessive Halstead Complexity
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code is structured in a way that a Halstead complexity measure exceeds a desirable maximum.
CWE-1123 · Excessive Use of Self-Modifying Code
Excessive Use of Self-Modifying Code
Technical detail
CWE-1123 · Excessive Use of Self-Modifying Code
Excessive Use of Self-Modifying Code
In plain English
Excessive Use of Self-Modifying Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses too much self-modifying code.
CWE-1124 · Excessively Deep Nesting
Excessively Deep Nesting
Technical detail
CWE-1124 · Excessively Deep Nesting
Excessively Deep Nesting
In plain English
Excessively Deep Nesting
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code contains a callable or other code grouping in which the nesting / branching is too deep.
CWE-1125 · Excessive Attack Surface
Excessive Attack Surface
Technical detail
CWE-1125 · Excessive Attack Surface
Excessive Attack Surface
In plain English
Excessive Attack Surface
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has an attack surface whose quantitative measurement exceeds a desirable maximum.
CWE-1126 · Declaration of Variable with Unnecessarily Wide Scope
Declaration of Variable with Unnecessarily Wide Scope
Technical detail
CWE-1126 · Declaration of Variable with Unnecessarily Wide Scope
Declaration of Variable with Unnecessarily Wide Scope
In plain English
Declaration of Variable with Unnecessarily Wide Scope
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The source code declares a variable in one scope, but the variable is only used within a narrower scope.
CWE-1127 · Compilation with Insufficient Warnings or Errors
Compilation with Insufficient Warnings or Errors
Technical detail
CWE-1127 · Compilation with Insufficient Warnings or Errors
Compilation with Insufficient Warnings or Errors
In plain English
Compilation with Insufficient Warnings or Errors
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code is compiled without sufficient warnings enabled, which may prevent the detection of subtle bugs or quality issues.
CWE-1164 · Irrelevant Code
Irrelevant Code
Technical detail
CWE-1164 · Irrelevant Code
Irrelevant Code
In plain English
Irrelevant Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product contains code that is not essential for execution, i.e. makes no state changes and has no side effects that alter data or control flow, such that removal of the code would have no impact to functionality or correctness.
CWE-1173 · Improper Use of Validation Framework
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1173 · Improper Use of Validation Framework
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product does not use, or incorrectly uses, an input validation framework that is provided by the source language or an independent library.
CWE-1174 · ASP.NET Misconfiguration: Improper Model Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1174 · ASP.NET Misconfiguration: Improper Model Validation
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The ASP.NET application does not use, or incorrectly uses, the model validation framework.
CWE-1176 · Inefficient CPU Computation
Inefficient CPU Computation
Technical detail
CWE-1176 · Inefficient CPU Computation
Inefficient CPU Computation
In plain English
Inefficient CPU Computation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs CPU computations using algorithms that are not as efficient as they could be for the needs of the developer, i.e., the computations can be optimized further.
CWE-1177 · Use of Prohibited Code
Use of Prohibited Code
Technical detail
CWE-1177 · Use of Prohibited Code
Use of Prohibited Code
In plain English
Use of Prohibited Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a function, library, or third party component that has been explicitly prohibited, whether by the developer or the customer.
CWE-1187 · DEPRECATED: Use of Uninitialized Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1187 · DEPRECATED: Use of Uninitialized Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
This entry has been deprecated because it was a duplicate of CWE-908. All content has been transferred to CWE-908.
CWE-1188 · Initialization of a Resource with an Insecure Default
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1188 · Initialization of a Resource with an Insecure Default
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the default is not secure.
CWE-1189 · Improper Isolation of Shared Resources on System-on-a-Chip (SoC)
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1189 · Improper Isolation of Shared Resources on System-on-a-Chip (SoC)
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents.
CWE-1190 · DMA Device Enabled Too Early in Boot Phase
The product handles memory in an unsafe way.
Important
CWE-1190 · DMA Device Enabled Too Early in Boot Phase
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product enables a Direct Memory Access (DMA) capable device before the security configuration settings are established, which allows an attacker to extract data from or gain privileges on the product.
CWE-1191 · On-Chip Debug and Test Interface With Improper Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1191 · On-Chip Debug and Test Interface With Improper Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes through the physical debug/test interface.
CWE-1192 · Improper Identifier for IP Block used in System-On-Chip (SOC)
Improper Identifier for IP Block used in System-On-Chip (SOC)
Technical detail
CWE-1192 · Improper Identifier for IP Block used in System-On-Chip (SOC)
Improper Identifier for IP Block used in System-On-Chip (SOC)
In plain English
Improper Identifier for IP Block used in System-On-Chip (SOC)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.
CWE-1193 · Power-On of Untrusted Execution Core Before Enabling Fabric Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1193 · Power-On of Untrusted Execution Core Before Enabling Fabric Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product enables components that contain untrusted firmware before memory and fabric access controls have been enabled.
CWE-1204 · Generation of Weak Initialization Vector (IV)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-1204 · Generation of Weak Initialization Vector (IV)
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses a cryptographic primitive that uses an Initialization Vector (IV), but the product does not generate IVs that are sufficiently unpredictable or unique according to the expected cryptographic requirements for that primitive.
CWE-1209 · Failure to Disable Reserved Bits
Failure to Disable Reserved Bits
Technical detail
CWE-1209 · Failure to Disable Reserved Bits
Failure to Disable Reserved Bits
In plain English
Failure to Disable Reserved Bits
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
An undocumented account, command, trigger, or communication path provides capabilities that are absent from the normal product interface.
A component appears to perform a legitimate function while secretly collecting information, bypassing controls, or activating hidden behavior.
MITRE description from the synchronized CWE record
The reserved bits in a hardware design are not disabled prior to production. Typically, reserved bits are used for future capabilities and should not support any functional logic in the design. However, designers might covertly use these bits to debug or further develop new capabilities in production hardware. Adversaries with access to these bits will write to them in hopes of compromising hardware state.
CWE-1220 · Insufficient Granularity of Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1220 · Insufficient Granularity of Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product implements access controls via a policy or other feature with the intention to disable or restrict accesses (reads and/or writes) to assets in a system from untrusted agents. However, implemented access controls lack required granularity, which renders the control policy too broad because it allows accesses from unauthorized agents to the security-sensitive assets.
CWE-1221 · Incorrect Register Defaults or Module Parameters
Incorrect Register Defaults or Module Parameters
Technical detail
CWE-1221 · Incorrect Register Defaults or Module Parameters
Incorrect Register Defaults or Module Parameters
In plain English
Incorrect Register Defaults or Module Parameters
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Hardware description language code incorrectly defines register defaults or hardware Intellectual Property (IP) parameters to insecure values.
CWE-1222 · Insufficient Granularity of Address Regions Protected by Register Locks
Insufficient Granularity of Address Regions Protected by Register Locks
Technical detail
CWE-1222 · Insufficient Granularity of Address Regions Protected by Register Locks
Insufficient Granularity of Address Regions Protected by Register Locks
In plain English
Insufficient Granularity of Address Regions Protected by Register Locks
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product defines a large address region protected from modification by the same register lock control bit. This results in a conflict between the functional requirement that some addresses need to be writable by software during operation and the security requirement that the system configuration lock bit must be set during the boot process.
CWE-1223 · Race Condition for Write-Once Attributes
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-1223 · Race Condition for Write-Once Attributes
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
A write-once register in hardware design is programmable by an untrusted software component earlier than the trusted software component, resulting in a race condition issue.
CWE-1224 · Improper Restriction of Write-Once Bit Fields
Improper Restriction of Write-Once Bit Fields
Technical detail
CWE-1224 · Improper Restriction of Write-Once Bit Fields
Improper Restriction of Write-Once Bit Fields
In plain English
Improper Restriction of Write-Once Bit Fields
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The hardware design control register "sticky bits" or write-once bit fields are improperly implemented, such that they can be reprogrammed by software.
CWE-1229 · Creation of Emergent Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1229 · Creation of Emergent Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product manages resources or behaves in a way that indirectly creates a new, distinct resource that can be used by attackers in violation of the intended policy.
CWE-1230 · Exposure of Sensitive Information Through Metadata
The product can expose information beyond the audience that should receive it.
Important
CWE-1230 · Exposure of Sensitive Information Through Metadata
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from the original, sensitive information.
CWE-1231 · Improper Prevention of Lock Bit Modification
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1231 · Improper Prevention of Lock Bit Modification
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product uses a trusted lock bit for restricting access to registers, address regions, or other resources, but the product does not prevent the value of the lock bit from being modified after it has been set.
CWE-1232 · Improper Lock Behavior After Power State Transition
Improper Lock Behavior After Power State Transition
Technical detail
CWE-1232 · Improper Lock Behavior After Power State Transition
Improper Lock Behavior After Power State Transition
In plain English
Improper Lock Behavior After Power State Transition
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Register lock bit protection disables changes to system configuration once the bit is set. Some of the protected registers or lock bits become programmable after power state transitions (e.g., Entry and wake from low power sleep modes) causing the system configuration to be changeable.
CWE-1233 · Security-Sensitive Hardware Controls with Missing Lock Bit Protection
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
Technical detail
CWE-1233 · Security-Sensitive Hardware Controls with Missing Lock Bit Protection
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
In plain English
Security-Sensitive Hardware Controls with Missing Lock Bit Protection
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a register lock bit protection mechanism, but it does not ensure that the lock bit prevents modification of system registers or controls that perform changes to important hardware system configuration.
CWE-1234 · Hardware Internal or Debug Modes Allow Override of Locks
Hardware Internal or Debug Modes Allow Override of Locks
Technical detail
CWE-1234 · Hardware Internal or Debug Modes Allow Override of Locks
Hardware Internal or Debug Modes Allow Override of Locks
In plain English
Hardware Internal or Debug Modes Allow Override of Locks
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
System configuration protection may be bypassed during debug mode.
CWE-1235 · Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations
Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations
Technical detail
CWE-1235 · Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations
Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations
In plain English
Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The code uses boxed primitives, which may introduce inefficiencies into performance-critical operations.
CWE-1236 · Improper Neutralization of Formula Elements in a CSV File
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-1236 · Improper Neutralization of Formula Elements in a CSV File
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product.
CWE-1239 · Improper Zeroization of Hardware Register
The product can expose information beyond the audience that should receive it.
Important
CWE-1239 · Improper Zeroization of Hardware Register
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes.
CWE-1240 · Use of a Cryptographic Primitive with a Risky Implementation
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-1240 · Use of a Cryptographic Primitive with a Risky Implementation
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptographic implementation.
CWE-1241 · Use of Predictable Algorithm in Random Number Generator
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-1241 · Use of Predictable Algorithm in Random Number Generator
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The device uses an algorithm that is predictable and generates a pseudo-random number.
CWE-1242 · Inclusion of Undocumented Features or Chicken Bits
Inclusion of Undocumented Features or Chicken Bits
Technical detail
CWE-1242 · Inclusion of Undocumented Features or Chicken Bits
Inclusion of Undocumented Features or Chicken Bits
In plain English
Inclusion of Undocumented Features or Chicken Bits
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The device includes chicken bits or undocumented features that can create entry points for unauthorized actors.
CWE-1243 · Sensitive Non-Volatile Information Not Protected During Debug
The product can expose information beyond the audience that should receive it.
Important
CWE-1243 · Sensitive Non-Volatile Information Not Protected During Debug
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
Access to security-sensitive information stored in fuses is not limited during debug.
CWE-1244 · Internal Asset Exposed to Unsafe Debug Access Level or State
Internal Asset Exposed to Unsafe Debug Access Level or State
Technical detail
CWE-1244 · Internal Asset Exposed to Unsafe Debug Access Level or State
Internal Asset Exposed to Unsafe Debug Access Level or State
In plain English
Internal Asset Exposed to Unsafe Debug Access Level or State
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses physical debug or test interfaces with support for multiple access levels, but it assigns the wrong debug access level to an internal asset, providing unintended access to the asset from untrusted debug agents.
CWE-1245 · Improper Finite State Machines (FSMs) in Hardware Logic
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1245 · Improper Finite State Machines (FSMs) in Hardware Logic
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
Faulty finite state machines (FSMs) in the hardware logic allow an attacker to put the system in an undefined state, to cause a denial of service (DoS) or gain privileges on the victim's system.
CWE-1246 · Improper Write Handling in Limited-write Non-Volatile Memories
Improper Write Handling in Limited-write Non-Volatile Memories
Technical detail
CWE-1246 · Improper Write Handling in Limited-write Non-Volatile Memories
Improper Write Handling in Limited-write Non-Volatile Memories
In plain English
Improper Write Handling in Limited-write Non-Volatile Memories
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not implement or incorrectly implements wear leveling operations in limited-write non-volatile memories.
CWE-1247 · Improper Protection Against Voltage and Clock Glitches
The product can expose information beyond the audience that should receive it.
Important
CWE-1247 · Improper Protection Against Voltage and Clock Glitches
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The device does not contain or contains incorrectly implemented circuitry or sensors to detect and mitigate voltage and clock glitches and protect sensitive information or software contained on the device.
CWE-1248 · Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
Technical detail
CWE-1248 · Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
In plain English
Semiconductor Defects in Hardware Logic with Security-Sensitive Implications
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The security-sensitive hardware module contains semiconductor defects.
CWE-1249 · Application-Level Admin Tool with Inconsistent View of Underlying Operating System
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1249 · Application-Level Admin Tool with Inconsistent View of Underlying Operating System
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product provides an application for administrators to manage parts of the underlying operating system, but the application does not accurately identify all of the relevant entities or resources that exist in the OS; that is, the application's model of the OS's state is inconsistent with the OS's actual state.
CWE-1250 · Improper Preservation of Consistency Between Independent Representations of Shared State
Improper Preservation of Consistency Between Independent Representations of Shared State
Technical detail
CWE-1250 · Improper Preservation of Consistency Between Independent Representations of Shared State
Improper Preservation of Consistency Between Independent Representations of Shared State
In plain English
Improper Preservation of Consistency Between Independent Representations of Shared State
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has or supports multiple distributed components or sub-systems that are each required to keep their own local copy of shared data - such as state or cache - but the product does not ensure that all local copies remain consistent with each other.
CWE-1251 · Mirrored Regions with Different Values
Mirrored Regions with Different Values
Technical detail
CWE-1251 · Mirrored Regions with Different Values
Mirrored Regions with Different Values
In plain English
Mirrored Regions with Different Values
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product's architecture mirrors regions without ensuring that their contents always stay in sync.
CWE-1252 · CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-1252 · CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The CPU is not configured to provide hardware support for exclusivity of write and execute operations on memory. This allows an attacker to execute data from all of memory.
CWE-1253 · Incorrect Selection of Fuse Values
Incorrect Selection of Fuse Values
Technical detail
CWE-1253 · Incorrect Selection of Fuse Values
Incorrect Selection of Fuse Values
In plain English
Incorrect Selection of Fuse Values
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The logic level used to set a system to a secure state relies on a fuse being unblown.
CWE-1254 · Incorrect Comparison Logic Granularity
Incorrect Comparison Logic Granularity
Technical detail
CWE-1254 · Incorrect Comparison Logic Granularity
Incorrect Comparison Logic Granularity
In plain English
Incorrect Comparison Logic Granularity
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product's comparison logic is performed over a series of steps rather than across the entire string in one operation. If there is a comparison logic failure on one of these steps, the operation may be vulnerable to a timing attack that can result in the interception of the process for nefarious purposes.
CWE-1255 · Comparison Logic is Vulnerable to Power Side-Channel Attacks
Comparison Logic is Vulnerable to Power Side-Channel Attacks
Technical detail
CWE-1255 · Comparison Logic is Vulnerable to Power Side-Channel Attacks
Comparison Logic is Vulnerable to Power Side-Channel Attacks
In plain English
Comparison Logic is Vulnerable to Power Side-Channel Attacks
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A device's real time power consumption may be monitored during security token evaluation and the information gleaned may be used to determine the value of the reference token.
CWE-1256 · Improper Restriction of Software Interfaces to Hardware Features
The product handles memory in an unsafe way.
Important
CWE-1256 · Improper Restriction of Software Interfaces to Hardware Features
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product provides software-controllable device functionality for capabilities such as power and clock management, but it does not properly limit functionality that can lead to modification of hardware memory or register bits, or the ability to observe physical side channels.
CWE-1257 · Improper Access Control Applied to Mirrored or Aliased Memory Regions
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1257 · Improper Access Control Applied to Mirrored or Aliased Memory Regions
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
Aliased or mirrored memory regions in hardware designs may have inconsistent read/write permissions enforced by the hardware. A possible result is that an untrusted agent is blocked from accessing a memory region but is not blocked from accessing the corresponding aliased memory region.
CWE-1258 · Exposure of Sensitive System Information Due to Uncleared Debug Information
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-1258 · Exposure of Sensitive System Information Due to Uncleared Debug Information
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The hardware does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations, when debug mode is entered.
CWE-1259 · Improper Restriction of Security Token Assignment
Improper Restriction of Security Token Assignment
Technical detail
CWE-1259 · Improper Restriction of Security Token Assignment
Improper Restriction of Security Token Assignment
In plain English
Improper Restriction of Security Token Assignment
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The System-On-A-Chip (SoC) implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens are improperly protected.
CWE-1260 · Improper Handling of Overlap Between Protected Memory Ranges
The product handles memory in an unsafe way.
Important
CWE-1260 · Improper Handling of Overlap Between Protected Memory Ranges
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product allows address regions to overlap, which can result in the bypassing of intended memory protection.
CWE-1261 · Improper Handling of Single Event Upsets
Improper Handling of Single Event Upsets
Technical detail
CWE-1261 · Improper Handling of Single Event Upsets
Improper Handling of Single Event Upsets
In plain English
Improper Handling of Single Event Upsets
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The hardware logic does not effectively handle when single-event upsets (SEUs) occur.
CWE-1262 · Improper Access Control for Register Interface
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1262 · Improper Access Control for Register Interface
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses memory-mapped I/O registers that act as an interface to hardware functionality from software, but there is improper access control to those registers.
CWE-1263 · Improper Physical Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1263 · Improper Physical Access Control
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product is designed with access restricted to certain information, but it does not sufficiently protect against an unauthorized actor with physical access to these areas.
CWE-1264 · Hardware Logic with Insecure De-Synchronization between Control and Data Channels
Hardware Logic with Insecure De-Synchronization between Control and Data Channels
Technical detail
CWE-1264 · Hardware Logic with Insecure De-Synchronization between Control and Data Channels
Hardware Logic with Insecure De-Synchronization between Control and Data Channels
In plain English
Hardware Logic with Insecure De-Synchronization between Control and Data Channels
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The hardware logic for error handling and security checks can incorrectly forward data before the security check is complete.
CWE-1265 · Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls
Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls
Technical detail
CWE-1265 · Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls
Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls
In plain English
Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product invokes code that is believed to be reentrant, but the code performs a call that unintentionally produces a nested invocation of the non-reentrant code.
CWE-1266 · Improper Scrubbing of Sensitive Data from Decommissioned Device
Improper Scrubbing of Sensitive Data from Decommissioned Device
Technical detail
CWE-1266 · Improper Scrubbing of Sensitive Data from Decommissioned Device
Improper Scrubbing of Sensitive Data from Decommissioned Device
In plain English
Improper Scrubbing of Sensitive Data from Decommissioned Device
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly provide a capability for the product administrator to remove sensitive data at the time the product is decommissioned. A scrubbing capability could be missing, insufficient, or incorrect.
CWE-1267 · Policy Uses Obsolete Encoding
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1267 · Policy Uses Obsolete Encoding
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses an obsolete encoding mechanism to implement access controls.
CWE-1268 · Policy Privileges are not Assigned Consistently Between Control and Data Agents
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1268 · Policy Privileges are not Assigned Consistently Between Control and Data Agents
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product's hardware-enforced access control for a particular resource improperly accounts for privilege discrepancies between control and write policies.
CWE-1269 · Product Released in Non-Release Configuration
Product Released in Non-Release Configuration
Technical detail
CWE-1269 · Product Released in Non-Release Configuration
Product Released in Non-Release Configuration
In plain English
Product Released in Non-Release Configuration
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product released to market is released in pre-production or manufacturing configuration.
CWE-1270 · Generation of Incorrect Security Tokens
Generation of Incorrect Security Tokens
Technical detail
CWE-1270 · Generation of Incorrect Security Tokens
Generation of Incorrect Security Tokens
In plain English
Generation of Incorrect Security Tokens
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Tokens generated in the system are incorrect.
CWE-1271 · Uninitialized Value on Reset for Registers Holding Security Settings
Uninitialized Value on Reset for Registers Holding Security Settings
Technical detail
CWE-1271 · Uninitialized Value on Reset for Registers Holding Security Settings
Uninitialized Value on Reset for Registers Holding Security Settings
In plain English
Uninitialized Value on Reset for Registers Holding Security Settings
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Security-critical logic is not set to a known value on reset.
CWE-1272 · Sensitive Information Uncleared Before Debug/Power State Transition
The product can expose information beyond the audience that should receive it.
Important
CWE-1272 · Sensitive Information Uncleared Before Debug/Power State Transition
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product performs a power or debug state transition, but it does not clear sensitive information that should no longer be accessible due to changes to information access restrictions.
CWE-1273 · Device Unlock Credential Sharing
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1273 · Device Unlock Credential Sharing
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The credentials necessary for unlocking a device are shared across multiple parties and may expose sensitive information.
CWE-1274 · Improper Access Control for Volatile Memory Containing Boot Code
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1274 · Improper Access Control for Volatile Memory Containing Boot Code
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product conducts a secure-boot process that transfers bootloader code from Non-Volatile Memory (NVM) into Volatile Memory (VM), but it does not have sufficient access control or other protections for the Volatile Memory.
CWE-1275 · Sensitive Cookie with Improper SameSite Attribute
Sensitive Cookie with Improper SameSite Attribute
Technical detail
CWE-1275 · Sensitive Cookie with Improper SameSite Attribute
Sensitive Cookie with Improper SameSite Attribute
In plain English
Sensitive Cookie with Improper SameSite Attribute
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The SameSite attribute for sensitive cookies is not set, or an insecure value is used.
CWE-1276 · Hardware Child Block Incorrectly Connected to Parent System
Hardware Child Block Incorrectly Connected to Parent System
Technical detail
CWE-1276 · Hardware Child Block Incorrectly Connected to Parent System
Hardware Child Block Incorrectly Connected to Parent System
In plain English
Hardware Child Block Incorrectly Connected to Parent System
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Signals between a hardware IP and the parent system design are incorrectly connected causing security risks.
CWE-1277 · Firmware Not Updateable
The device cannot safely receive fixes after deployment.
Important
CWE-1277 · Firmware Not Updateable
The device cannot safely receive fixes after deployment.
In plain English
The device cannot safely receive fixes after deployment.
What this can look like
A serious vulnerability is discovered but affected devices cannot receive a secure firmware update, leaving replacement or isolation as the only practical remediation.
A deployed appliance has a known security flaw but no trustworthy update path, so administrators must isolate or replace it instead of applying a fix.
The update mechanism cannot reliably verify or install a security update, leaving vulnerable devices exposed after a fix exists upstream.
MITRE description from the synchronized CWE record
The product does not provide its users with the ability to update or patch its firmware to address any vulnerabilities or weaknesses that may be present.
CWE-1278 · Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
Technical detail
CWE-1278 · Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
In plain English
Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Information stored in hardware may be recovered by an attacker with the capability to capture and analyze images of the integrated circuit using techniques such as scanning electron microscopy.
CWE-1279 · Cryptographic Operations are run Before Supporting Units are Ready
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-1279 · Cryptographic Operations are run Before Supporting Units are Ready
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
Performing cryptographic operations without ensuring that the supporting inputs are ready to supply valid data may compromise the cryptographic result.
CWE-1280 · Access Control Check Implemented After Asset is Accessed
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1280 · Access Control Check Implemented After Asset is Accessed
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
A product's hardware-based access control check occurs after the asset has been accessed.
CWE-1281 · Sequence of Processor Instructions Leads to Unexpected Behavior
Sequence of Processor Instructions Leads to Unexpected Behavior
Technical detail
CWE-1281 · Sequence of Processor Instructions Leads to Unexpected Behavior
Sequence of Processor Instructions Leads to Unexpected Behavior
In plain English
Sequence of Processor Instructions Leads to Unexpected Behavior
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Specific combinations of processor instructions lead to undesirable behavior such as locking the processor until a hard reset performed.
CWE-1282 · Assumed-Immutable Data is Stored in Writable Memory
The product handles memory in an unsafe way.
Important
CWE-1282 · Assumed-Immutable Data is Stored in Writable Memory
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
Immutable data, such as a first-stage bootloader, device identifiers, and "write-once" configuration settings are stored in writable memory that can be re-programmed or updated in the field.
CWE-1283 · Mutable Attestation or Measurement Reporting Data
Mutable Attestation or Measurement Reporting Data
Technical detail
CWE-1283 · Mutable Attestation or Measurement Reporting Data
Mutable Attestation or Measurement Reporting Data
In plain English
Mutable Attestation or Measurement Reporting Data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The register contents used for attestation or measurement reporting data to verify boot flow are modifiable by an adversary.
CWE-1284 · Improper Validation of Specified Quantity in Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1284 · Improper Validation of Specified Quantity in Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.
CWE-1285 · Improper Validation of Specified Index, Position, or Offset in Input
The product handles memory in an unsafe way.
Important
CWE-1285 · Improper Validation of Specified Index, Position, or Offset in Input
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A request intended to access one application file is manipulated so it reaches a configuration, key, or system file outside the permitted folder.
An archive, download, import, or file-management feature accepts a path that escapes the directory the application meant to restrict it to.
MITRE description from the synchronized CWE record
The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties.
CWE-1286 · Improper Validation of Syntactic Correctness of Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1286 · Improper Validation of Syntactic Correctness of Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
CWE-1287 · Improper Validation of Specified Type of Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1287 · Improper Validation of Specified Type of Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
CWE-1288 · Improper Validation of Consistency within Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1288 · Improper Validation of Consistency within Input
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent.
CWE-1289 · Improper Validation of Unsafe Equivalence in Input
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1289 · Improper Validation of Unsafe Equivalence in Input
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value.
CWE-1290 · Incorrect Decoding of Security Identifiers
Incorrect Decoding of Security Identifiers
Technical detail
CWE-1290 · Incorrect Decoding of Security Identifiers
Incorrect Decoding of Security Identifiers
In plain English
Incorrect Decoding of Security Identifiers
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product implements a decoding mechanism to decode certain bus-transaction signals to security identifiers. If the decoding is implemented incorrectly, then untrusted agents can now gain unauthorized access to the asset.
CWE-1291 · Public Key Re-Use for Signing both Debug and Production Code
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-1291 · Public Key Re-Use for Signing both Debug and Production Code
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The same public key is used for signing both debug and production code.
CWE-1292 · Incorrect Conversion of Security Identifiers
Incorrect Conversion of Security Identifiers
Technical detail
CWE-1292 · Incorrect Conversion of Security Identifiers
Incorrect Conversion of Security Identifiers
In plain English
Incorrect Conversion of Security Identifiers
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product implements a conversion mechanism to map certain bus-transaction signals to security identifiers. However, if the conversion is incorrectly implemented, untrusted agents can gain unauthorized access to the asset.
CWE-1293 · Missing Source Correlation of Multiple Independent Data
Missing Source Correlation of Multiple Independent Data
Technical detail
CWE-1293 · Missing Source Correlation of Multiple Independent Data
Missing Source Correlation of Multiple Independent Data
In plain English
Missing Source Correlation of Multiple Independent Data
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product relies on one source of data, preventing the ability to detect if an adversary has compromised a data source.
CWE-1294 · Insecure Security Identifier Mechanism
Insecure Security Identifier Mechanism
Technical detail
CWE-1294 · Insecure Security Identifier Mechanism
Insecure Security Identifier Mechanism
In plain English
Insecure Security Identifier Mechanism
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The System-on-Chip (SoC) implements a Security Identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Security Identifiers are not correctly implemented.
CWE-1295 · Debug Messages Revealing Unnecessary Information
Debug Messages Revealing Unnecessary Information
Technical detail
CWE-1295 · Debug Messages Revealing Unnecessary Information
Debug Messages Revealing Unnecessary Information
In plain English
Debug Messages Revealing Unnecessary Information
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
CWE-1296 · Incorrect Chaining or Granularity of Debug Components
Incorrect Chaining or Granularity of Debug Components
Technical detail
CWE-1296 · Incorrect Chaining or Granularity of Debug Components
Incorrect Chaining or Granularity of Debug Components
In plain English
Incorrect Chaining or Granularity of Debug Components
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product's debug components contain incorrect chaining or granularity of debug components.
CWE-1297 · Unprotected Confidential Information on Device is Accessible by OSAT Vendors
Unprotected Confidential Information on Device is Accessible by OSAT Vendors
Technical detail
CWE-1297 · Unprotected Confidential Information on Device is Accessible by OSAT Vendors
Unprotected Confidential Information on Device is Accessible by OSAT Vendors
In plain English
Unprotected Confidential Information on Device is Accessible by OSAT Vendors
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not adequately protect confidential information on the device from being accessed by Outsourced Semiconductor Assembly and Test (OSAT) vendors.
CWE-1298 · Hardware Logic Contains Race Conditions
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-1298 · Hardware Logic Contains Race Conditions
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
A race condition in the hardware logic results in undermining security guarantees of the system.
CWE-1299 · Missing Protection Mechanism for Alternate Hardware Interface
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1299 · Missing Protection Mechanism for Alternate Hardware Interface
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The lack of protections on alternate paths to access control-protected assets (such as unprotected shadow registers and other external facing unguarded interfaces) allows an attacker to bypass existing protections to the asset that are only performed against the primary path.
CWE-1300 · Improper Protection of Physical Side Channels
The product can expose information beyond the audience that should receive it.
Important
CWE-1300 · Improper Protection of Physical Side Channels
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The device does not contain sufficient protection mechanisms to prevent physical side channels from exposing sensitive information due to patterns in physically observable phenomena such as variations in power consumption, electromagnetic emissions (EME), or acoustic emissions.
CWE-1301 · Insufficient or Incomplete Data Removal within Hardware Component
The product can expose information beyond the audience that should receive it.
Important
CWE-1301 · Insufficient or Incomplete Data Removal within Hardware Component
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product's data removal process does not completely delete all data and potentially sensitive information within hardware components.
CWE-1302 · Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
Technical detail
CWE-1302 · Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
In plain English
Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product implements a security identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. A transaction is sent without a security identifier.
CWE-1303 · Non-Transparent Sharing of Microarchitectural Resources
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1303 · Non-Transparent Sharing of Microarchitectural Resources
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
Hardware structures shared across execution contexts (e.g., caches and branch predictors) can violate the expected architecture isolation between contexts.
CWE-1304 · Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
Technical detail
CWE-1304 · Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
In plain English
Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product performs a power save/restore operation, but it does not ensure that the integrity of the configuration state is maintained and/or verified between the beginning and ending of the operation.
CWE-1310 · Missing Ability to Patch ROM Code
Missing Ability to Patch ROM Code
Technical detail
CWE-1310 · Missing Ability to Patch ROM Code
Missing Ability to Patch ROM Code
In plain English
Missing Ability to Patch ROM Code
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.
CWE-1311 · Improper Translation of Security Attributes by Fabric Bridge
Improper Translation of Security Attributes by Fabric Bridge
Technical detail
CWE-1311 · Improper Translation of Security Attributes by Fabric Bridge
Improper Translation of Security Attributes by Fabric Bridge
In plain English
Improper Translation of Security Attributes by Fabric Bridge
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The bridge incorrectly translates security attributes from either trusted to untrusted or from untrusted to trusted when converting from one fabric protocol to another.
CWE-1312 · Missing Protection for Mirrored Regions in On-Chip Fabric Firewall
The product handles memory in an unsafe way.
Important
CWE-1312 · Missing Protection for Mirrored Regions in On-Chip Fabric Firewall
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The firewall in an on-chip fabric protects the main addressed region, but it does not protect any mirrored memory or memory-mapped-IO (MMIO) regions.
CWE-1313 · Hardware Allows Activation of Test or Debug Logic at Runtime
Hardware Allows Activation of Test or Debug Logic at Runtime
Technical detail
CWE-1313 · Hardware Allows Activation of Test or Debug Logic at Runtime
Hardware Allows Activation of Test or Debug Logic at Runtime
In plain English
Hardware Allows Activation of Test or Debug Logic at Runtime
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
During runtime, the hardware allows for test or debug logic (feature) to be activated, which allows for changing the state of the hardware. This feature can alter the intended behavior of the system and allow for alteration and leakage of sensitive data by an adversary.
CWE-1314 · Missing Write Protection for Parametric Data Values
Missing Write Protection for Parametric Data Values
Technical detail
CWE-1314 · Missing Write Protection for Parametric Data Values
Missing Write Protection for Parametric Data Values
In plain English
Missing Write Protection for Parametric Data Values
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The device does not write-protect the parametric data values for sensors that scale the sensor value, allowing untrusted software to manipulate the apparent result and potentially damage hardware or cause operational failure.
CWE-1315 · Improper Setting of Bus Controlling Capability in Fabric End-point
Improper Setting of Bus Controlling Capability in Fabric End-point
Technical detail
CWE-1315 · Improper Setting of Bus Controlling Capability in Fabric End-point
Improper Setting of Bus Controlling Capability in Fabric End-point
In plain English
Improper Setting of Bus Controlling Capability in Fabric End-point
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The bus controller enables bits in the fabric end-point to allow responder devices to control transactions on the fabric.
CWE-1316 · Fabric-Address Map Allows Programming of Unwarranted Overlaps of Protected and Unprotected Ranges
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1316 · Fabric-Address Map Allows Programming of Unwarranted Overlaps of Protected and Unprotected Ranges
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The address map of the on-chip fabric has protected and unprotected regions overlapping, allowing an attacker to bypass access control to the overlapping portion of the protected region.
CWE-1317 · Improper Access Control in Fabric Bridge
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1317 · Improper Access Control in Fabric Bridge
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses a fabric bridge for transactions between two Intellectual Property (IP) blocks, but the bridge does not properly perform the expected privilege, identity, or other access control checks between those IP blocks.
CWE-1318 · Missing Support for Security Features in On-chip Fabrics or Buses
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1318 · Missing Support for Security Features in On-chip Fabrics or Buses
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
On-chip fabrics or buses either do not support or are not configured to support privilege separation or other security features, such as access control.
CWE-1319 · Improper Protection against Electromagnetic Fault Injection (EM-FI)
Improper Protection against Electromagnetic Fault Injection (EM-FI)
Technical detail
CWE-1319 · Improper Protection against Electromagnetic Fault Injection (EM-FI)
Improper Protection against Electromagnetic Fault Injection (EM-FI)
In plain English
Improper Protection against Electromagnetic Fault Injection (EM-FI)
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed.
CWE-1320 · Improper Protection for Outbound Error Messages and Alert Signals
Improper Protection for Outbound Error Messages and Alert Signals
Technical detail
CWE-1320 · Improper Protection for Outbound Error Messages and Alert Signals
Improper Protection for Outbound Error Messages and Alert Signals
In plain English
Improper Protection for Outbound Error Messages and Alert Signals
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
Untrusted agents can disable alerts about signal conditions exceeding limits or the response mechanism that handles such alerts.
CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1321 · Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
CWE-1322 · Use of Blocking Code in Single-threaded, Non-blocking Context
Use of Blocking Code in Single-threaded, Non-blocking Context
Technical detail
CWE-1322 · Use of Blocking Code in Single-threaded, Non-blocking Context
Use of Blocking Code in Single-threaded, Non-blocking Context
In plain English
Use of Blocking Code in Single-threaded, Non-blocking Context
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a non-blocking model that relies on a single threaded process for features such as scalability, but it contains code that can block when it is invoked.
CWE-1323 · Improper Management of Sensitive Trace Data
The product assumes an operation or security decision cannot change during a small timing window.
Technical detail
CWE-1323 · Improper Management of Sensitive Trace Data
The product assumes an operation or security decision cannot change during a small timing window.
In plain English
The product assumes an operation or security decision cannot change during a small timing window.
What this can look like
An attacker manipulates timing so that a resource changes between validation and use, producing a result the original security check did not intend.
A file, permission, or object changes after the product checks it but before it uses it, so the later operation acts on something different from what was approved.
Two operations happen in an unexpected order and a security decision made by the first is no longer valid when the second runs.
MITRE description from the synchronized CWE record
Trace data collected from several sources on the System-on-Chip (SoC) is stored in unprotected locations or transported to untrusted agents.
CWE-1324 · DEPRECATED: Sensitive Information Accessible by Physical Probing of JTAG Interface
The product can expose information beyond the audience that should receive it.
Important
CWE-1324 · DEPRECATED: Sensitive Information Accessible by Physical Probing of JTAG Interface
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
This entry has been deprecated because it was at a lower level of abstraction than supported by CWE. All relevant content has been integrated into CWE-319.
CWE-1325 · Improperly Controlled Sequential Memory Allocation
The product handles memory in an unsafe way.
Important
CWE-1325 · Improperly Controlled Sequential Memory Allocation
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
CWE-1326 · Missing Immutable Root of Trust in Hardware
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-1326 · Missing Immutable Root of Trust in Hardware
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
A missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code.
CWE-1327 · Binding to an Unrestricted IP Address
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1327 · Binding to an Unrestricted IP Address
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.
CWE-1328 · Security Version Number Mutable to Older Versions
Security Version Number Mutable to Older Versions
Technical detail
CWE-1328 · Security Version Number Mutable to Older Versions
Security Version Number Mutable to Older Versions
In plain English
Security Version Number Mutable to Older Versions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A deployed appliance has a known security flaw but no trustworthy update path, so administrators must isolate or replace it instead of applying a fix.
The update mechanism cannot reliably verify or install a security update, leaving vulnerable devices exposed after a fix exists upstream.
MITRE description from the synchronized CWE record
Security-version number in hardware is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions.
CWE-1329 · Reliance on Component That is Not Updateable
Reliance on Component That is Not Updateable
Technical detail
CWE-1329 · Reliance on Component That is Not Updateable
Reliance on Component That is Not Updateable
In plain English
Reliance on Component That is Not Updateable
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A deployed appliance has a known security flaw but no trustworthy update path, so administrators must isolate or replace it instead of applying a fix.
The update mechanism cannot reliably verify or install a security update, leaving vulnerable devices exposed after a fix exists upstream.
MITRE description from the synchronized CWE record
The product contains a component that cannot be updated or patched in order to remove vulnerabilities or significant bugs.
CWE-1330 · Remanent Data Readable after Memory Erase
The product handles memory in an unsafe way.
Important
CWE-1330 · Remanent Data Readable after Memory Erase
The product handles memory in an unsafe way.
In plain English
The product handles memory in an unsafe way.
What this can look like
Specially crafted input corrupts or misuses memory, which may cause a crash and can sometimes lead to code execution depending on the affected component.
A malformed file or network packet makes the program read or write memory outside the region it safely owns, causing a crash or corrupted behavior.
A parser handles an unusual size or object state incorrectly and damages memory that is later used for program control or sensitive data.
MITRE description from the synchronized CWE record
Confidential information stored in memory circuits is readable or recoverable after being cleared or erased.
CWE-1331 · Improper Isolation of Shared Resources in Network On Chip (NoC)
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1331 · Improper Isolation of Shared Resources in Network On Chip (NoC)
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The Network On Chip (NoC) does not isolate or incorrectly isolates its on-chip-fabric and internal resources such that they are shared between trusted and untrusted agents, creating timing channels.
CWE-1332 · Improper Handling of Faults that Lead to Instruction Skips
Improper Handling of Faults that Lead to Instruction Skips
Technical detail
CWE-1332 · Improper Handling of Faults that Lead to Instruction Skips
Improper Handling of Faults that Lead to Instruction Skips
In plain English
Improper Handling of Faults that Lead to Instruction Skips
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur.
CWE-1333 · Inefficient Regular Expression Complexity
Inefficient Regular Expression Complexity
Technical detail
CWE-1333 · Inefficient Regular Expression Complexity
Inefficient Regular Expression Complexity
In plain English
Inefficient Regular Expression Complexity
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product uses a regular expression with a worst-case computational complexity that is inefficient and possibly exponential.
CWE-1334 · Unauthorized Error Injection Can Degrade Hardware Redundancy
Unauthorized Error Injection Can Degrade Hardware Redundancy
Technical detail
CWE-1334 · Unauthorized Error Injection Can Degrade Hardware Redundancy
Unauthorized Error Injection Can Degrade Hardware Redundancy
In plain English
Unauthorized Error Injection Can Degrade Hardware Redundancy
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An unauthorized agent can inject errors into a redundant block to deprive the system of redundancy or put the system in a degraded operating mode.
CWE-1335 · Incorrect Bitwise Shift of Integer
Incorrect Bitwise Shift of Integer
Technical detail
CWE-1335 · Incorrect Bitwise Shift of Integer
Incorrect Bitwise Shift of Integer
In plain English
Incorrect Bitwise Shift of Integer
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
An integer value is specified to be shifted by a negative amount or an amount greater than or equal to the number of bits contained in the value causing an unexpected or indeterminate result.
CWE-1336 · Improper Neutralization of Special Elements Used in a Template Engine
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1336 · Improper Neutralization of Special Elements Used in a Template Engine
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses a template engine to insert or process externally-influenced input, but it does not neutralize or incorrectly neutralizes special elements or syntax that can be interpreted as template expressions or other code directives when processed by the engine.
CWE-1338 · Improper Protections Against Hardware Overheating
Improper Protections Against Hardware Overheating
Technical detail
CWE-1338 · Improper Protections Against Hardware Overheating
Improper Protections Against Hardware Overheating
In plain English
Improper Protections Against Hardware Overheating
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
A hardware device is missing or has inadequate protection features to prevent overheating.
CWE-1339 · Insufficient Precision or Accuracy of a Real Number
Insufficient Precision or Accuracy of a Real Number
Technical detail
CWE-1339 · Insufficient Precision or Accuracy of a Real Number
Insufficient Precision or Accuracy of a Real Number
In plain English
Insufficient Precision or Accuracy of a Real Number
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product processes a real number with an implementation in which the number's representation does not preserve required accuracy and precision in its fractional part, causing an incorrect result.
CWE-1341 · Multiple Releases of Same Resource or Handle
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1341 · Multiple Releases of Same Resource or Handle
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product attempts to close or release a resource or handle more than once, without any successful open between the close operations.
CWE-1342 · Information Exposure through Microarchitectural State after Transient Execution
The product can expose information beyond the audience that should receive it.
Important
CWE-1342 · Information Exposure through Microarchitectural State after Transient Execution
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The processor does not properly clear microarchitectural state after incorrect microcode assists or speculative execution, resulting in transient execution.
CWE-1351 · Improper Handling of Hardware Behavior in Exceptionally Cold Environments
Improper Handling of Hardware Behavior in Exceptionally Cold Environments
Technical detail
CWE-1351 · Improper Handling of Hardware Behavior in Exceptionally Cold Environments
Improper Handling of Hardware Behavior in Exceptionally Cold Environments
In plain English
Improper Handling of Hardware Behavior in Exceptionally Cold Environments
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A deployed appliance has a known security flaw but no trustworthy update path, so administrators must isolate or replace it instead of applying a fix.
The update mechanism cannot reliably verify or install a security update, leaving vulnerable devices exposed after a fix exists upstream.
MITRE description from the synchronized CWE record
A hardware device, or the firmware running on it, is missing or has incorrect protection features to maintain goals of security primitives when the device is cooled below standard operating temperatures.
CWE-1357 · Reliance on Insufficiently Trustworthy Component
Reliance on Insufficiently Trustworthy Component
Technical detail
CWE-1357 · Reliance on Insufficiently Trustworthy Component
Reliance on Insufficiently Trustworthy Component
In plain English
Reliance on Insufficiently Trustworthy Component
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A deployed appliance has a known security flaw but no trustworthy update path, so administrators must isolate or replace it instead of applying a fix.
The update mechanism cannot reliably verify or install a security update, leaving vulnerable devices exposed after a fix exists upstream.
MITRE description from the synchronized CWE record
The product is built from multiple separate components, but it uses a component that is not sufficiently trusted to meet expectations for security, reliability, updateability, and maintainability.
CWE-1384 · Improper Handling of Physical or Environmental Conditions
Improper Handling of Physical or Environmental Conditions
Technical detail
CWE-1384 · Improper Handling of Physical or Environmental Conditions
Improper Handling of Physical or Environmental Conditions
In plain English
Improper Handling of Physical or Environmental Conditions
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product does not properly handle unexpected physical or environmental conditions that occur naturally or are artificially induced.
CWE-1385 · Missing Origin Validation in WebSockets
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1385 · Missing Origin Validation in WebSockets
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.
CWE-1386 · Insecure Operation on Windows Junction / Mount Point
The product does not sufficiently constrain access to files, paths, or resource permissions.
Important
CWE-1386 · Insecure Operation on Windows Junction / Mount Point
The product does not sufficiently constrain access to files, paths, or resource permissions.
In plain English
The product does not sufficiently constrain access to files, paths, or resource permissions.
What this can look like
Crafted input or overly broad permissions allow access to a file or resource outside the scope the application intended.
A normal user changes a request or calls an endpoint directly and reaches data or actions reserved for an administrator.
A file, service, API, or device function is accessible to a broader set of users than the product intended.
MITRE description from the synchronized CWE record
The product opens a file or directory, but it does not properly prevent the name from being associated with a junction or mount point to a destination that is outside of the intended control sphere.
CWE-1389 · Incorrect Parsing of Numbers with Different Radices
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1389 · Incorrect Parsing of Numbers with Different Radices
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product parses numeric input assuming base 10 (decimal) values, but it does not account for inputs that use a different base number (radix).
CWE-1390 · Weak Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
Important
CWE-1390 · Weak Authentication
The product does not protect identity, credentials, or access decisions as strongly as intended.
In plain English
The product does not protect identity, credentials, or access decisions as strongly as intended.
What this can look like
An attacker abuses the weakness to authenticate improperly, obtain credentials, or reach an operation that should require stronger access checks.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.
CWE-1391 · Use of Weak Credentials
Authentication relies on credentials that are inherently weak or easily guessed.
Headline signal
CWE-1391 · Use of Weak Credentials
Authentication relies on credentials that are inherently weak or easily guessed.
In plain English
Authentication relies on credentials that are inherently weak or easily guessed.
What this can look like
A device or service uses predictable or low-entropy credentials that can be guessed with very little effort.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker.
CWE-1392 · Use of Default Credentials
The product ships with credentials that remain valid unless the user changes them.
Headline signal
CWE-1392 · Use of Default Credentials
The product ships with credentials that remain valid unless the user changes them.
In plain English
The product ships with credentials that remain valid unless the user changes them.
What this can look like
An internet-facing device still accepts the manufacturer’s documented factory username and password.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
CWE-1393 · Use of Default Password
The product ships with a predefined password.
Headline signal
CWE-1393 · Use of Default Password
The product ships with a predefined password.
In plain English
The product ships with a predefined password.
What this can look like
A device is deployed without changing its factory password, allowing anyone who knows the default to authenticate.
A device management page exposes or accepts credentials in a way that lets someone who should not have them sign in.
A backup, log, configuration file, or firmware image reveals an authentication secret that can be reused elsewhere.
MITRE description from the synchronized CWE record
The product uses default passwords for potentially critical functionality.
CWE-1394 · Use of Default Cryptographic Key
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
Important
CWE-1394 · Use of Default Cryptographic Key
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
In plain English
A security property that depends on cryptography is weakened by the way the product uses keys, algorithms, randomness, or validation.
What this can look like
An attacker takes advantage of the weak cryptographic handling to bypass trust, recover protected information, or impersonate a trusted party.
A product relies on a predictable key, weak validation, or unsuitable cryptography, so data or identities that appear protected can no longer be trusted.
The same embedded key or weak cryptographic choice is reused across installations, allowing compromise of one instance to weaken others.
MITRE description from the synchronized CWE record
The product uses a default cryptographic key for potentially critical functionality.
CWE-1395 · Dependency on Vulnerable Third-Party Component
Dependency on Vulnerable Third-Party Component
Technical detail
CWE-1395 · Dependency on Vulnerable Third-Party Component
Dependency on Vulnerable Third-Party Component
In plain English
Dependency on Vulnerable Third-Party Component
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has a dependency on a third-party component that contains one or more known vulnerabilities.
CWE-1419 · Incorrect Initialization of Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
Technical detail
CWE-1419 · Incorrect Initialization of Resource
The product can consume or manage resources in a way that is not sufficiently bounded.
In plain English
The product can consume or manage resources in a way that is not sufficiently bounded.
What this can look like
Repeated or specially formed requests consume excessive CPU, memory, handles, or other resources until normal service is degraded or unavailable.
A small number of specially formed requests cause disproportionate CPU, memory, storage, connection, or worker consumption until legitimate work slows or stops.
The service accepts work without a practical limit, allowing one client to exhaust a resource needed by everyone else.
MITRE description from the synchronized CWE record
The product attempts to initialize a resource but does not correctly do so, which might leave the resource in an unexpected, incorrect, or insecure state when it is accessed.
CWE-1420 · Exposure of Sensitive Information during Transient Execution
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-1420 · Exposure of Sensitive Information during Transient Execution
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
A processor event or prediction may allow incorrect operations (or correct operations with incorrect data) to execute transiently, potentially exposing data over a covert channel.
CWE-1421 · Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution
The product can expose information beyond the audience that should receive it.
Important
CWE-1421 · Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
A processor event may allow transient operations to access architecturally restricted data (for example, in another address space) in a shared microarchitectural structure (for example, a CPU cache), potentially exposing the data over a covert channel.
CWE-1422 · Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution
The product can expose information beyond the audience that should receive it.
Important
CWE-1422 · Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
A processor event or prediction may allow incorrect or stale data to be forwarded to transient operations, potentially exposing data over a covert channel.
CWE-1423 · Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution
The product can expose information beyond the audience that should receive it.
Important
CWE-1423 · Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
Shared microarchitectural predictor state may allow code to influence transient execution across a hardware boundary, potentially exposing data that is accessible beyond the boundary over a covert channel.
CWE-1426 · Improper Validation of Generative AI Output
The product can expose information beyond the audience that should receive it.
Important
CWE-1426 · Improper Validation of Generative AI Output
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product invokes a generative AI/ML component whose behaviors and outputs cannot be directly controlled, but the product does not validate or insufficiently validates the outputs to ensure that they align with the intended security, content, or privacy policy.
CWE-1427 · Improper Neutralization of Input Used for LLM Prompting
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
Technical detail
CWE-1427 · Improper Neutralization of Input Used for LLM Prompting
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
In plain English
Input is not validated, normalized, or neutralized correctly before it reaches a sensitive operation.
What this can look like
Crafted input uses characters or structure the application did not anticipate, changing how a downstream component interprets the request.
A value that looks harmless to one component is interpreted differently by the next component because it was not normalized or validated consistently.
Unexpected characters, length, encoding, or structure get past an input check and alter how a downstream parser or service handles the request.
MITRE description from the synchronized CWE record
The product uses externally-provided data to build prompts provided to large language models (LLMs), but the way these prompts are constructed causes the LLM to fail to distinguish between user-supplied inputs and developer provided system directives.
CWE-1428 · Reliance on HTTP instead of HTTPS
Reliance on HTTP instead of HTTPS
Technical detail
CWE-1428 · Reliance on HTTP instead of HTTPS
Reliance on HTTP instead of HTTPS
In plain English
Reliance on HTTP instead of HTTPS
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product provides or relies on use of HTTP communications when HTTPS is available.
CWE-1429 · Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
Untrusted data can influence instructions that the product executes.
Headline signal
CWE-1429 · Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface
Untrusted data can influence instructions that the product executes.
In plain English
Untrusted data can influence instructions that the product executes.
What this can look like
Crafted input crosses from data into executable instructions, causing the application or device to perform unintended operations.
A field that should contain ordinary data is interpreted as instructions, causing the application or device to run an unintended operation.
A network-facing feature passes attacker-controlled content into an interpreter or executable component instead of treating it only as data.
MITRE description from the synchronized CWE record
The product has a hardware interface that silently discards operations in situations for which feedback would be security-relevant, such as the timely detection of failures or attacks.
CWE-1431 · Driving Intermediate Cryptographic State/Results to Hardware Module Outputs
The product can expose information beyond the audience that should receive it.
Important
CWE-1431 · Driving Intermediate Cryptographic State/Results to Hardware Module Outputs
The product can expose information beyond the audience that should receive it.
In plain English
The product can expose information beyond the audience that should receive it.
What this can look like
An attacker obtains information that should have remained protected and uses it directly or as supporting intelligence for another attack.
An error page, API response, diagnostic endpoint, or log reveals internal details that were meant to stay private.
Someone without the required access can retrieve configuration data, usernames, tokens, internal addresses, or other useful security information.
MITRE description from the synchronized CWE record
The product uses a hardware module implementing a cryptographic algorithm that writes sensitive information about the intermediate state or results of its cryptographic operations via one of its output wires (typically the output port containing the final result).
CWE-1434 · Insecure Setting of Generative AI/ML Model Inference Parameters
Insecure Setting of Generative AI/ML Model Inference Parameters
Technical detail
CWE-1434 · Insecure Setting of Generative AI/ML Model Inference Parameters
Insecure Setting of Generative AI/ML Model Inference Parameters
In plain English
Insecure Setting of Generative AI/ML Model Inference Parameters
What this can look like
An attacker reaches the vulnerable behavior with specially chosen input or system state, causing the product to behave outside its intended security rules.
A feature behaves safely with normal input but an unusual value, sequence, or system state makes it cross a security boundary the developer did not intend.
The weakness may not be exploitable in every product, but when reachable it can turn an ordinary function into unintended access, disclosure, corruption, or service disruption.
MITRE description from the synchronized CWE record
The product has a component that relies on a generative AI/ML model configured with inference parameters that produce an unacceptably high rate of erroneous or unexpected outputs.
Examples are intentionally conceptual. They explain the security consequence without providing exploit payloads or step-by-step attack instructions. MITRE remains the authoritative source for the CWE definition and mapping guidance.