Weakness Base Elements

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 ...

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.

A product's hardware-based access control check occurs after the asset has been accessed.

The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.

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.

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 incompa...

The product accesses or uses a pointer that has not been initialized.

The product defines a public method that reads or modifies a private variable.

The product is deployed to unauthorized actors with debugging code still enabled or active, which can create unintended entry points or expose sensitive information.

The accidental addition of a data-structure sentinel can cause serious programming logic problems.

The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be ...

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 ...

The product's architecture contains too many - or too few - horizontal layers.

The variable's value is assigned but never used, making it a dead store.

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 o...

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 ...

The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.

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 t...

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.

This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

A product requires authentication, but the product has an alternate path or channel that does not require authentication.

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.

A's behavior or functionality changes with a new version of A, or a new environment, which is not known (or manageable) by B.

The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.

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 ...

The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buf...

The product writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.

The code contains a function or method whose signature and/or associated inline documentation does not sufficiently describe the callable's inputs, outputs, ...

The code contains a class instance that calls the method or function to delete or destroy itself.

A class contains an unnecessarily large number of children.

A class has an inheritance level that is too high, i.e., it has a large number of parent classes.

A class contains a virtual method, but the method does not have an associated virtual destructor.

The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

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.

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...

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 resu...

The code is compiled without sufficient warnings enabled, which may prevent the detection of subtle bugs or quality issues.

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.

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...

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 t...

Covert timing channels convey information by modulating some aspect of system behavior over time, so that the program receiving the information can observe system beha...

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 me...

A static code block creates an instance of a class.

The product creates an immutable text string using string concatenation operations.

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.

Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.

The product declares a critical variable, field, or member to be public when intended security policy requires it to be private.

Performing cryptographic operations without ensuring that the supporting inputs are ready to supply valid data may compromise the cryptographic result.

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...

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 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 ...

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...

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.

The code contains a data element with a pointer that does not have an associated copy or constructor method.

The product accesses a data resource through a database without using a connection pooling capability.

The product contains dead code, which can never be executed.

The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.

The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.

Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.

Throwing overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.

The source code declares a variable in one scope, but the variable is only used within a narrower scope.

The accidental deletion of a data-structure sentinel can cause serious programming logic problems.

The wrong "handler" is assigned to process an object.

The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.

The product detects a specific error, but takes no actions to handle the error.

The credentials necessary for unlocking a device are shared across multiple parties and may expose sensitive information.

The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.

The product divides a value by zero.

The product enables a Direct Memory Access (DMA) capable device before the security configuration settings are established, which allows an attacker to extract data fr...

The product uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.

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.

The source code contains a block that does not contain any code, i.e., the block is empty.

The product has an attack surface whose quantitative measurement exceeds a desirable maximum.

The product performs a data query with a large number of joins and sub-queries on a large data table.

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 t...

The code is structured in a way that a Halstead complexity measure exceeds a desirable maximum.

The product contains an index range scan for a large data table, but the scan can cover a large number of rows.

The code contains McCabe cyclomatic complexity that exceeds a desirable maximum.

The product performs too many data queries without using efficient data processing functionality such as stored procedures.

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, l...

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 as...

The product initializes a data element using a hard-coded literal that is not a simple integer or static constant element.

The product uses too much self-modifying code.

The code uses too many unconditional branches (such as "goto").

The code contains a callable or other code grouping in which the nesting / branching is too deep.

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 inserti...

The web application sends a redirect to another location, but instead of exiting, it executes additional code.

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 ot...

A feature, API, or function does not perform according to its specification.

The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.

The product makes an explicit call to the finalize() method from outside the finalizer.

The product provides an Applications Programming Interface (API) or similar interface for interaction with external actors, but the interface includes a dangerous meth...

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.

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 descript...

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...

A processor event or prediction may allow incorrect or stale data to be forwarded to transient operations, potentially exposing data over a covert channel.

Shared microarchitectural predictor state may allow code to influence transient execution across a hardware boundary, potentially exposing data that is accessi...

The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sens...

A processor event or prediction may allow incorrect operations (or correct operations with incorrect data) to execute transiently, potentially exposing data over a cov...

A processor event may allow transient operations to access architecturally restricted data (for example, in another address space) in a shared microarchitect...

When trying to keep information confidential, an attacker can often infer some of the information by using statistics.

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 origi...

The hardware does not fully clear security-sensitive values, such as keys and intermediate values in cryptographic operations, when debug mode is entered.

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 und...

The product contains an expression that will always evaluate to false.

The product contains an expression that will always evaluate to true.

The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.

The product allows user input to control or influence paths or file names that are used in filesystem operations.

One or more system settings or configuration elements can be externally controlled by a user.

The product initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.

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 g...

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 th...

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 funct...

The product makes files or directories accessible to unauthorized actors, even though they should not be.

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.

The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses.

The product generates an error message that includes sensitive information about its environment, users, or associated data.

The product implements a Security Token mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. However, the Se...

The product uses a cryptographic primitive that uses an Initialization Vector (IV), but the product does not generate IVs that are sufficiently unpredictable or ...

The product uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor.

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 ...

Signals between a hardware IP and the parent system design are incorrectly connected causing security risks.

System configuration protection may be bypassed during debug mode.

A race condition in the hardware logic results in undermining security guarantees of the system.

The hardware logic for error handling and security checks can incorrectly forward data before the security check is complete.

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 ag...

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.

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 acc...

The product uses a fabric bridge for transactions between two Intellectual Property (IP) blocks, but the bridge does not properly perform the expected privilege, ident...

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.

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 info...

The product does not validate, or incorrectly validates, a certificate.

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.

The product attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.

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.

The product does not properly restrict reading from or writing to dynamically-identified variables.

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 neutralize...

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 enf...

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 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 no...

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 privile...

The product does not follow, or incorrectly follows, the chain of trust for a certificate back to a trusted root certificate, resulting in incorrect trust of any resou...

The product receives input from an upstream component, but it does not handle or incorrectly handles when an additional unexpected special element is provided.

The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.

The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur.

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 associa...

A hardware device, or the firmware running on it, is missing or has incorrect protection features to maintain goals of security primiti...

The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.

The product does not properly handle input in which an inconsistency exists between two or more special characters or reserved words.

The product does not handle or incorrectly handles when two or more structural elements should be consistent, but are not.

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...

The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.

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 as...

The product receives input from an upstream component, but it does not handle or incorrectly handles when an expected special element is missing.

The product allows address regions to overlap, which can result in the bypassing of intended memory protection.

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.

The hardware logic does not effectively handle when single-event upsets (SEUs) occur.

The product does not handle or incorrectly handles inputs that are related to complex structures.

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).

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.

The System-on-Chip (SoC) does not have unique, immutable identifiers for each of its components.

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 ag...

The System-On-a-Chip (SoC) does not properly isolate shared resources between trusted and untrusted agents.

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 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 uni...

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...

Trace data collected from several sources on the System-on-Chip (SoC) is stored in unprotected locations or transported to untrusted ag...

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...

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 ...

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 neut...

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 neu...

The product does not neutralize or incorrectly neutralizes delimiters.

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 ...

The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.

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 ...

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.

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 t...

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 u...

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...

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...

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 neutralize...

The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.

The product does not neutralize or incorrectly neutralizes output that is written to logs.

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 ...

The product does not preserve permissions or incorrectly preserves permissions when copying, restoring, or sharing objects, which can cause them to have less restricti...

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 bi...

The device is susceptible to electromagnetic fault injection attacks, causing device internal information to be compromised or security mechanisms to be bypassed.

The device does not contain or contains incorrectly implemented circuitry or sensors to detect and mitigate voltage and clock glitches and protect sensitive informatio...

Untrusted agents can disable alerts about signal conditions exceeding limits or the response mechanism that handles such alerts.

A hardware device is missing or has inadequate protection features to prevent overheating.

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 ...

The product is vulnerable to file system contents disclosure through path equivalence. Path equivalence involves the use of special characters in file and directory na...

The product does not lock or does not correctly lock a resource when the product must have exclusive access to the resource.

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute fo...

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.

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 am...

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...

The web application does not restrict or incorrectly restricts frame objects or UI layers that belong to another application or domain, which can lead to user confusio...

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. ...

The product provides software-controllable device functionality for capabilities such as power and clock management, but it does not properly limit functional...

The hardware design control register "sticky bits" or write-once bit fields are improperly implemented, such that they can be reprogrammed by software.

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 ...

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 capab...

The bus controller enables bits in the fabric end-point to allow responder devices to control transactions on the fabric.

The bridge incorrectly translates security attributes from either trusted to untrusted or from untrusted to trusted when converting from one fabric protocol to another.

The product uses a reference count to manage a resource, but it does not update or incorrectly updates the reference count.

The product does not use, or incorrectly uses, an input validation framework that is provided by the source language or an independent library.

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 t...

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 ...

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 i...

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...

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.

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 inpu...

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 ...

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

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 ...

The product does not implement or incorrectly implements wear leveling operations in limited-write non-volatile memories.

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...

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 memor...

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 tech...

The product performs a power save/restore operation, but it does not ensure that the integrity of the configuration state is maintained and/or ...

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.

The source code uses comment styles or formats that are inconsistent or do not follow expected standards for the product.

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...

The source code contains whitespace that is inconsistent across the code or does not follow expected standards for the product.

The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.

Source code on a web server or repository often contains sensitive information and should generally not be accessible to users.

The device includes chicken bits or undocumented features that can create entry points for unauthorized actors.

The product does not properly "clean up" and remove temporary or supporting resources after they have been used.

The product's design documentation does not adequately describe control flow, data flow, system initialization, relationships between tasks, components, rati...

The document does not fully define all mechanisms that are used to control or influence how product-specific programs are executed.

The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.

The product's documentation does not adequately define inputs, outputs, or system/software interfaces.

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 oper...

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 actio...

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, poten...

The implementation of the product is not consistent with the design as described within the relevant documentation.

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 i...

The product's code, documentation, or other artifacts do not consistently use the same naming conventions for variables, callables, groups of related callabl...

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.

The product allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place.

The product validates input before applying protection mechanisms that modify the input, which could allow an attacker to bypass the validation via dangerous inputs th...

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 ...

The code does not explicitly delimit a block that is intended to contain 2 or more statements, creating a logic error.

The product does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.

The product does not correctly calculate the length of strings that can contain wide or multi-byte characters.

The product's debug components contain incorrect chaining or granularity of debug components.

The product incorrectly checks a return value from a function, which prevents it from detecting errors or exceptional conditions.

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...

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 va...

The product implements a conversion mechanism to map certain bus-transaction signals to security identifiers. However, if the conversion is incorrectly implemented, un...

The product implements a decoding mechanism to decode certain bus-transaction signals to security identifiers. If the decoding is implemented incorrectly, then untrust...

During installation, installed file permissions are set to allow anyone to modify those files.

The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.

The product assigns an owner to a resource, but the owner is outside of the intended control sphere.

The product parses numeric input assuming base 10 (decimal) values, but it does not account for inputs that use a different base number (radix).

In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled.

A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

Hardware description language code incorrectly defines register defaults or hardware Intellectual Property (IP) parameters to insecure values.

The logic level used to set a system to a secure state relies on a fuse being unblown. An attacker can set the system to an insecure state merely by blowing the fuse.

The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.

The product uses a Pseudo-Random Number Generator (PRNG) but does not correctly manage seeds.

The code uses boxed primitives, which may introduce inefficiencies into performance-critical operations.

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 f...

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.

The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.

The processor does not properly clear microarchitectural state after incorrect microcode assists or speculative execution, resulting in transient execution.

The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.

The product initializes data using hard-coded values that act as network resource identifiers.

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 ...

The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.

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 written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.

The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.

The documentation does not sufficiently describe the techniques that are used for error handling, exception processing, or similar mechanisms.

The product or code uses machine-dependent functionality, but it does not sufficiently encapsulate or isolate this functionality from the rest of the code.

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.

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 fro...

The source code uses symbolic constants, but it does not sufficiently place the definitions of these constants into a more centralized or isolated location.

The product or code does not isolate system-dependent functionality into separate standalone modules.

When a security-critical event occurs, the product either does not record the event or omits important details about the event when logging it.

The product's data removal process does not completely delete all data and potentially sensitive information within hardware components.

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 par...

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) l...

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."

The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.

The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention.

The source code uses literal constants that may need to change or evolve over time, instead of using symbolic constants.

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 iden...

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 o...

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 co...

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 ...

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 t...

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.

The code contains a function or method that operates in a multi-threaded environment but owns an unsafe non-final static storable or member d...

A function or method contains too many operations that utilize a data manager or file resource.

A function, method, procedure, etc. contains an excessive amount of code that has been commented out within its body.

The code contains callable control elements that contain an excessively large number of references to other application objects external to the conte...

The product contains a function, subroutine, or method whose signature has an unnecessarily large number of parameters/arguments.

A named-callable or method control element has a signature that supports a variable (variadic) number of parameters or arguments.

The product performs a key exchange with an actor without verifying the identity of that actor.

The product uses a large data table that contains an excessively large number of indices.

The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.

The product logs too much information, making log files hard to process and possibly hindering recovery efforts or forensic analysis after an attack.

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 logica...

The product uses a loop with a control flow condition based on a value that is updated within the body of the loop.

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

A method for a class performs an operation that directly accesses a member element from another class.

The product's architecture mirrors regions without ensuring that their contents always stay in sync.

The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.

Missing an ability to patch ROM code may leave a System or System-on-Chip (SoC) in a vulnerable state.

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

The product implements an authentication technique, but it skips a step that weakens the technique.

The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.

The product does not return custom error pages to the user, possibly exposing sensitive information.

The code does not have a default case in an expression with multiple conditions, such as a switch statement.

The product does not have documentation that represents how it is designed.

A handler is not available or implemented.

A missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code.

A product does not check to see if a lock is present before performing sensitive operations on a resource.

The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.

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 sca...

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.

The lack of protections on alternate paths to access control-protected assets (such as unprotected shadow registers and other external ...

The product does not properly maintain a reference to a resource that has been allocated, which prevents the resource from being reclaimed.

The product does not release a resource after its effective lifetime has ended, i.e., after the resource is no longer needed.

The product encounters an error but does not provide a status code or return value to indicate that an error has occurred.

The product contains a serializable data element that does not have an associated serialization method.

The product relies on one source of data, preventing the ability to detect if an adversary has compromised a data source.

The product implements a security identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. A transact...

The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses.

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.

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.

The product utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource.

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...

The product accepts XML from an untrusted source but does not validate the XML against the proper schema.

The product does not properly protect an assumed-immutable element from being modified by an attacker.

The product contains modules in which one module has references that cycle back to itself, i.e., there are circular dependencies.

The product contains a class with inheritance from more than one concrete class.

The UI has multiple interpretations of user input but does not prompt the user when it selects the less secure interpretation.

The product locks a critical resource more times than intended, leading to an unexpected state in the system.

The product attempts to close or release a resource or handle more than once, without any successful open between the close operations.

The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.

The register contents used for attestation or measurement reporting data to verify boot flow are modifiable by an adversary.

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 e...

Non-replicating malicious code only resides on the target system or product that is attacked; it does not attempt to spread to other systems.

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 ...

Hardware structures shared across execution contexts (e.g., caches and branch predictors) can violate the expected architecture isolation between contexts.

The product does not have a mechanism in place for managing password aging.

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 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.

Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.

The product records security-relevant information according to an alternate name of the affected entity, instead of the canonical name.

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...

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security...

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...

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 a...

A UI function is obsolete and the product does not warn the user.

A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.

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.

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...

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 ...

The product receives data from an upstream component, but only accounts for special elements at a specified location, thereby missing remaining special elements that m...

The product uses an expression in which operator precedence causes incorrect logic to be used.

The product reads data past the end, or before the beginning, of the intended buffer.

The product writes data past the end, or before the beginning, of the intended buffer.

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 serv...

A regular expression is overly restrictive, which prevents dangerous values from being detected.

A parent class has a virtual destructor method, but the parent has a child class that does not have a virtual destructor.

The code has a parent class that contains references to a child class, its methods, or its members.

A parent class contains one or more child classes, but the parent class does not have a virtual destructor method.

The product sends non-cloned mutable data as an argument to a method or function.

The product supports password aging, but the expiration period is too long.

The product stores a password in a configuration file that might be accessible to actors who do not know the password.

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 as...

The product uses a regular expression that does not sufficiently restrict the set of allowed values.

The product uses a storable data element that does not have all of the associated functions or methods that are necessary to support comparison.

The product or the administrator places a user into an incorrect group.

Storing a password in plaintext may result in a system compromise.

The product's hardware-enforced access control for a particular resource improperly accounts for privilege discrepancies between control and write policies.

The product uses an obsolete encoding mechanism to implement access controls.

The product enables components that contain untrusted firmware before memory and fabric access controls have been enabled.

An exact value or random number can be precisely predicted by observing previous values.

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.

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 val...

The product releases a resource that is still intended to be used by itself or another actor.

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...

The product does not properly manage privileges while it is switching between different contexts that have different privileges or spheres of control.

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.

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 re...

The product released to market is released in pre-production or manufacturing configuration.

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 ...

The same public key is used for signing both debug and production code.

The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors.

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 acce...

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 ...

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...

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 th...

Simple authentication protocols are subject to reflection attacks if a malicious user can use the target machine to impersonate a trusted user.

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 c...

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.

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...

The product contains a component that cannot be updated or patched in order to remove vulnerabilities or significant bugs.

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 th...

The product makes invalid assumptions about how protocol data or memory is organized at a lower level, resulting in unintended program behavior.

The code uses a data representation that relies on low-level data representation or constructs that may vary across different processors, physical machines, ...

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 ...

Java packages are not inherently closed; therefore, relying on them for code security is not a good practice.

The product uses automatically-generated code that cannot be executed without a specific runtime support component.

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 ...

Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or the product.

The code has a return statement inside a finally block, which will cause any thrown exception in the try block to be discarded.

A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.

A function returns the address of a stack variable, which will cause unintended program behavior, typically in the form of a crash.

A function or operation returns an incorrect return value or status code that does not indicate an error, but causes the product to modify its behavior based on the in...

Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function.

Nonces should be used for the present occasion and only once.

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...

Security-version number in hardware is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions.

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 ...

A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mecha...

The product identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.

The security-sensitive hardware module contains semiconductor defects.

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 th...

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 a...

Access to security-sensitive information stored in fuses is not limited during debug.

Specific combinations of processor instructions lead to undesirable behavior such as locking the processor until a hard reset performed.

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.

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 product uses a signal handler that introduces a race condition.

The number of possible random values is smaller than needed by the product, making it more susceptible to brute force attacks.

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.

A source code file has too many lines of code.

The product collects personally identifiable information about a human user or the user's activities, but the product accesses this information using other resources b...

The product stores sensitive information in a file system or device that does not have built-in access control.

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 encrypte...

A constant symbolic reference to an object is used, even though the reference can resolve to a different object over time.

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.

The UI performs the wrong action with respect to the user's request.

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 ...

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 me...

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 polic...

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.

The product mixes trusted and untrusted data in the same data structure or structured message.

Security based on event locations are insecure and can be spoofed.

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.

An exception is thrown from a function, but it is not caught.

[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 in...

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 loo...

The product does not check the return value from a method or function, which can prevent it from detecting unexpected states and conditions.

The product performs unconditional control transfer (such as a "goto") in code outside of a branching structure such as a switch block.

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.

The behavior of this function is undefined unless its control parameter is set to a specific value.

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.

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...

Security-critical logic is not set to a known value on reset.

During execution of non-reentrant code, the product performs a call that unintentionally produces a nested invocation of the non-reentrant code.

The product attempts to unlock a resource that is not locked.

The product protects a primary channel, but it does not use the same level of protection for an alternate channel.

The product does not adequately protect confidential information on the device from being accessed by Outsourced Semiconductor Assembly and Test (OSAT) vendors.

The product uses a primary channel for administration or restricted functionality, but it does not properly protect the channel.

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.

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 re...

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 ...

The product allows the attacker to upload or transfer files of dangerous types that can be automatically processed within the product's environment.

The product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes.

The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.

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.

The product does not properly verify that a critical resource is owned by the proper entity.

When setting a new password for a user, the product does not require knowledge of the original password, or using another form of authentication.

A web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a Redirect. This simplifies phishing attacks.

To fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant cryptog...

The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attac...

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 t...

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 invo...

The code uses a cache that contains sensitive information, but the cache can be read by an actor outside of the intended control sphere.

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 tha...

The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong.

The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.

The product uses a default cryptographic key for potentially critical functionality.

The product uses default passwords for potentially critical functionality.

The product uses or accesses a file descriptor after it has been closed.

The product uses a function that accepts a format string as an argument, but the format string originates from an external source.

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 ...

The code uses a function that has inconsistent implementations across operating systems and versions.

The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to exter...

The product uses hard-coded constants instead of symbolic names for security-critical values, which increases the likelihood of mistakes during code maintenance or sec...

The product accidentally uses the wrong operator, which changes the logic in security-relevant ways.

The product calls a function that can never be guaranteed to work safely.

The product uses a constant value, name, or reference, but this value can (or should) vary across different environments.

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 resis...

The product uses low-level functionality that is explicitly prohibited by the framework or specification under which the product is supposed to operate.

The product uses multiple resources that can have the same identifier, in a context in which unique identifiers are required.

Catching NullPointerException should not be used as an alternative to programmatic checks to prevent dereferencing a null pointer.

The product contains a method that accesses an object but does not later invoke the element's associated finalize/destructor method.

The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.

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 result...

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.

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 at...

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.

The product relies on third-party components that do not provide equivalent functionality across all desirable platforms.

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.

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.

The device uses an algorithm that is predictable and generates a pseudo-random number.

The product has multiple functions, methods, procedures, macros, etc. that contain the same code.

The product uses the same control element across multiple architectural layers.

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 ins...

The use of single-factor authentication can lead to unnecessary risk of compromise when compared with the benefits of a dual-factor authentication scheme.

The product uses or accesses a resource that has not been initialized.

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 deve...

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...

Obscuring a password with a trivial encoding does not protect the password.

The product contains a mechanism for users to recover or change their passwords without knowing the original password, but the mechanism is weak.

The product does not require that users should have strong passwords, which makes it easier for attackers to compromise user accounts.

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.

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.

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 p...