Weaknesses in the 2021 CWE Top 25 Most Dangerous Software Weaknesses
A view in the Common Weakness Enumeration published by The MITRE Corporation.
Views in the Common Weakness Enumeration (CWE) represent one perspective with which to consider a set of weaknesses.
CWE entries in this view are listed in the 2021 CWE Top 25 Most Dangerous Software Weaknesses.
Educators can use this view to focus curriculum and teachings on the most dangerous weaknesses.
Customers can use the weaknesses in this view in order to formulate independent evidence of a claim by a product vendor to have eliminated / mitigated the most dangerous weaknesses.
By following the CWE Top 25, developers are able to significantly reduce the number of weaknesses that occur in their software.
The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the...
The application deserializes untrusted data without sufficiently verifying that the resulting data will be valid.
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
When an actor claims to have a given identity, the software does not prove or insufficiently proves that the claim is correct.
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 th...
The software uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but...
The software does not 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 us...
The software constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes sp...
The software constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralize...
The software constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutraliz...
The software performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer.
The software processes an XML document that can contain XML entities with URIs that resolve to documents outside of the intended sphere of control, causing the product...
During installation, installed file permissions are set to allow anyone to modify those files.
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.
The software performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the ...
The software does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
The software does not perform an authorization check when an actor attempts to access a resource or perform an action.
A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit.
The software reads data past the end, or before the beginning, of the intended buffer.
The software writes data past the end, or before the beginning, of the intended buffer.
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 reques...
The software allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.
Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.
The software contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to exte...