CWE - CWE-1000: Research Concepts (4.15)

View ID: 1000

Vulnerability Mapping: PROHIBITEDThis CWE ID must not be used to map to real-world vulnerabilities
Type: Graph

Downloads: Booklet | CSV | XML

Objective

This view is intended to facilitate research into weaknesses, including their inter-dependencies, and can be leveraged to systematically identify theoretical gaps within CWE. It is mainly organized according to abstractions of behaviors instead of how they can be detected, where they appear in code, or when they are introduced in the development life cycle. By design, this view is expected to include every weakness within CWE.

Audience

Stakeholder	Description
Academic Researchers	Academic researchers can use the high-level classes that lack a significant number of children to identify potential areas for future research.
Vulnerability Analysts	Those who perform vulnerability discovery/analysis use this view to identify related weaknesses that might be leveraged by following relationships between higher-level classes and bases.
Assessment Tool Vendors	Assessment vendors often use this view to help identify additional weaknesses that a tool may be able to detect as the relationships are more aligned with a tool's technical capabilities.

Relationships

The following graph shows the tree-like relationships between weaknesses that exist at different levels of abstraction. At the highest level, categories and pillars exist to group weaknesses. Categories (which are not technically weaknesses) are special CWE entries used to group weaknesses that share a common characteristic. Pillars are weaknesses that are described in the most abstract fashion. Below these top-level entries are weaknesses are varying levels of abstraction. Classes are still very abstract, typically independent of any specific language or technology. Base level weaknesses are used to present a more specific type of weakness. A variant is a weakness that is described at a very low level of detail, typically limited to a specific language or technology. A chain is a set of weaknesses that must be reachable consecutively in order to produce an exploitable vulnerability. While a composite is a set of weaknesses that must all be present simultaneously in order to produce an exploitable vulnerability.

Show Details:

Expand All | Collapse All | Filter View

1000 - Research Concepts

Pillar - a weakness that is the most abstract type of weakness and represents a theme for all class/base/variant weaknesses related to it. A Pillar is different from a Category as a Pillar is still technically a type of weakness that describes a mistake, while a Category represents a common characteristic used to group related things.Improper Access Control - (284)

1000 (Research Concepts) > 284 (Improper Access Control)

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.Authorization

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.On-Chip Debug and Test Interface With Improper Access Control - (1191)

1000 (Research Concepts) > 284 (Improper Access Control) > 1191 (On-Chip Debug and Test Interface With Improper Access Control)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Granularity of Access Control - (1220)

1000 (Research Concepts) > 284 (Improper Access Control) > 1220 (Insufficient Granularity of Access Control)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Granularity of Address Regions Protected by Register Locks - (1222)

1000 (Research Concepts) > 284 (Improper Access Control) > 1220 (Insufficient Granularity of Access Control) > 1222 (Insufficient Granularity of Address Regions Protected by Register Locks)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Write-Once Bit Fields - (1224)

1000 (Research Concepts) > 284 (Improper Access Control) > 1224 (Improper Restriction of Write-Once Bit Fields)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Prevention of Lock Bit Modification - (1231)

1000 (Research Concepts) > 284 (Improper Access Control) > 1231 (Improper Prevention of Lock Bit Modification)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Security-Sensitive Hardware Controls with Missing Lock Bit Protection - (1233)

1000 (Research Concepts) > 284 (Improper Access Control) > 1233 (Security-Sensitive Hardware Controls with Missing Lock Bit Protection)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Inclusion of Undocumented Features or Chicken Bits - (1242)

1000 (Research Concepts) > 284 (Improper Access Control) > 1242 (Inclusion of Undocumented Features or Chicken Bits)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations - (1252)

1000 (Research Concepts) > 284 (Improper Access Control) > 1252 (CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Access Control Applied to Mirrored or Aliased Memory Regions - (1257)

1000 (Research Concepts) > 284 (Improper Access Control) > 1257 (Improper Access Control Applied to Mirrored or Aliased Memory Regions)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Security Token Assignment - (1259)

1000 (Research Concepts) > 284 (Improper Access Control) > 1259 (Improper Restriction of Security Token Assignment)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Overlap Between Protected Memory Ranges - (1260)

1000 (Research Concepts) > 284 (Improper Access Control) > 1260 (Improper Handling of Overlap Between Protected Memory Ranges)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Access Control for Register Interface - (1262)

1000 (Research Concepts) > 284 (Improper Access Control) > 1262 (Improper Access Control for Register Interface)

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.

Class - a weakness that is described in a very abstract fashion, typically independent of any specific language or technology. More specific than a Pillar Weakness, but more general than a Base Weakness. Class level weaknesses typically describe issues in terms of 1 or 2 of the following dimensions: behavior, property, and resource.Improper Physical Access Control - (1263)

1000 (Research Concepts) > 284 (Improper Access Control) > 1263 (Improper Physical Access Control)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Non-Volatile Information Not Protected During Debug - (1243)

1000 (Research Concepts) > 284 (Improper Access Control) > 1263 (Improper Physical Access Control) > 1243 (Sensitive Non-Volatile Information Not Protected During Debug)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 1267 (Policy Uses Obsolete Encoding)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Policy Privileges are not Assigned Consistently Between Control and Data Agents - (1268)

1000 (Research Concepts) > 284 (Improper Access Control) > 1268 (Policy Privileges are not Assigned Consistently Between Control and Data Agents)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 1270 (Generation of Incorrect Security Tokens)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Access Control for Volatile Memory Containing Boot Code - (1274)

1000 (Research Concepts) > 284 (Improper Access Control) > 1274 (Improper Access Control for Volatile Memory Containing Boot Code)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Hardware Child Block Incorrectly Connected to Parent System - (1276)

1000 (Research Concepts) > 284 (Improper Access Control) > 1276 (Hardware Child Block Incorrectly Connected to Parent System)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Access Control Check Implemented After Asset is Accessed - (1280)

1000 (Research Concepts) > 284 (Improper Access Control) > 1280 (Access Control Check Implemented After Asset is Accessed)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Mutable Attestation or Measurement Reporting Data - (1283)

1000 (Research Concepts) > 284 (Improper Access Control) > 1283 (Mutable Attestation or Measurement Reporting Data)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Decoding of Security Identifiers - (1290)

1000 (Research Concepts) > 284 (Improper Access Control) > 1290 (Incorrect Decoding of Security Identifiers )

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Conversion of Security Identifiers - (1292)

1000 (Research Concepts) > 284 (Improper Access Control) > 1292 (Incorrect Conversion of Security Identifiers)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 1294 (Insecure Security Identifier Mechanism)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC) - (1302)

1000 (Research Concepts) > 284 (Improper Access Control) > 1294 (Insecure Security Identifier Mechanism) > 1302 (Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC))

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Chaining or Granularity of Debug Components - (1296)

1000 (Research Concepts) > 284 (Improper Access Control) > 1296 (Incorrect Chaining or Granularity of Debug Components)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation - (1304)

1000 (Research Concepts) > 284 (Improper Access Control) > 1304 (Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Translation of Security Attributes by Fabric Bridge - (1311)

1000 (Research Concepts) > 284 (Improper Access Control) > 1311 (Improper Translation of Security Attributes by Fabric Bridge)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Protection for Mirrored Regions in On-Chip Fabric Firewall - (1312)

1000 (Research Concepts) > 284 (Improper Access Control) > 1312 (Missing Protection for Mirrored Regions in On-Chip Fabric Firewall)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Hardware Allows Activation of Test or Debug Logic at Runtime - (1313)

1000 (Research Concepts) > 284 (Improper Access Control) > 1313 (Hardware Allows Activation of Test or Debug Logic at Runtime)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Setting of Bus Controlling Capability in Fabric End-point - (1315)

1000 (Research Concepts) > 284 (Improper Access Control) > 1315 (Improper Setting of Bus Controlling Capability in Fabric End-point)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Fabric-Address Map Allows Programming of Unwarranted Overlaps of Protected and Unprotected Ranges - (1316)

1000 (Research Concepts) > 284 (Improper Access Control) > 1316 (Fabric-Address Map Allows Programming of Unwarranted Overlaps of Protected and Unprotected Ranges)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 1317 (Improper Access Control in Fabric Bridge)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Protection for Outbound Error Messages and Alert Signals - (1320)

1000 (Research Concepts) > 284 (Improper Access Control) > 1320 (Improper Protection for Outbound Error Messages and Alert Signals)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Management of Sensitive Trace Data - (1323)

1000 (Research Concepts) > 284 (Improper Access Control) > 1323 (Improper Management of Sensitive Trace Data)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Unauthorized Error Injection Can Degrade Hardware Redundancy - (1334)

1000 (Research Concepts) > 284 (Improper Access Control) > 1334 (Unauthorized Error Injection Can Degrade Hardware Redundancy)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management)

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 250 (Execution with Unnecessary Privileges)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 266 (Incorrect Privilege Assignment)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Web Link to Untrusted Target with window.opener Access - (1022)

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 266 (Incorrect Privilege Assignment) > 1022 (Use of Web Link to Untrusted Target with window.opener Access)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource..NET Misconfiguration: Use of Impersonation - (520)

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 266 (Incorrect Privilege Assignment) > 520 (.NET Misconfiguration: Use of Impersonation)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.ASP.NET Misconfiguration: Use of Identity Impersonation - (556)

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 266 (Incorrect Privilege Assignment) > 556 (ASP.NET Misconfiguration: Use of Identity Impersonation)

Configuring an ASP.NET application to run with impersonated credentials may give the application unnecessary privileges.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Misconfiguration: Weak Access Permissions for EJB Methods - (9)

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 266 (Incorrect Privilege Assignment) > 9 (J2EE Misconfiguration: Weak Access Permissions for EJB Methods)

If elevated access rights are assigned to EJB methods, then an attacker can take advantage of the permissions to exploit the product.

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 267 (Privilege Defined With Unsafe Actions)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Unsafe ActiveX Control Marked Safe For Scripting - (623)

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 267 (Privilege Defined With Unsafe Actions) > 623 (Unsafe ActiveX Control Marked Safe For Scripting)

An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 268 (Privilege Chaining)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 270 (Privilege Context Switching Error)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 271 (Privilege Dropping / Lowering Errors)

The product does not drop privileges before passing control of a resource to an actor that does not have those privileges.

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 271 (Privilege Dropping / Lowering Errors) > 272 (Least Privilege Violation)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 271 (Privilege Dropping / Lowering Errors) > 273 (Improper Check for Dropped Privileges)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Insufficient Privileges - (274)

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 274 (Improper Handling of Insufficient Privileges)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 269 (Improper Privilege Management) > 648 (Incorrect Use of Privileged APIs)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 282 (Improper Ownership Management)

The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.

1000 (Research Concepts) > 284 (Improper Access Control) > 282 (Improper Ownership Management) > 283 (Unverified Ownership)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 282 (Improper Ownership Management) > 708 (Incorrect Ownership Assignment)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization)

The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.AuthZ

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive Information Through Metadata - (1230)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 1230 (Exposure of Sensitive Information Through Metadata)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive Information Through Data Queries - (202)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 1230 (Exposure of Sensitive Information Through Metadata) > 202 (Exposure of Sensitive Information Through Data Queries)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Authorization of Index Containing Sensitive Information - (612)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 1230 (Exposure of Sensitive Information Through Metadata) > 612 (Improper Authorization of Index Containing Sensitive Information)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Software Interfaces to Hardware Features - (1256)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 1256 (Improper Restriction of Software Interfaces to Hardware Features)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Unprotected Confidential Information on Device is Accessible by OSAT Vendors - (1297)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 1297 (Unprotected Confidential Information on Device is Accessible by OSAT Vendors)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Security Version Number Mutable to Older Versions - (1328)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 1328 (Security Version Number Mutable to Older Versions)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Files or Directories Accessible to External Parties - (552)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Storage of File with Sensitive Data Under Web Root - (219)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 219 (Storage of File with Sensitive Data Under Web Root)

The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.

The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Storage of File With Sensitive Data Under FTP Root - (220)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 220 (Storage of File With Sensitive Data Under FTP Root)

The product stores sensitive data under the FTP server root with insufficient access control, which might make it accessible to untrusted parties.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Version-Control Repository to an Unauthorized Control Sphere - (527)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 527 (Exposure of Version-Control Repository to an Unauthorized Control Sphere)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Core Dump File to an Unauthorized Control Sphere - (528)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 528 (Exposure of Core Dump File to an Unauthorized Control Sphere)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Access Control List Files to an Unauthorized Control Sphere - (529)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 529 (Exposure of Access Control List Files to an Unauthorized Control Sphere)

The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Backup File to an Unauthorized Control Sphere - (530)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 530 (Exposure of Backup File to an Unauthorized Control Sphere)

A backup file is stored in a directory or archive that is made accessible to unauthorized actors.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Persistent Cookies Containing Sensitive Information - (539)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 539 (Use of Persistent Cookies Containing Sensitive Information)

The web application uses persistent cookies, but the cookies contain sensitive information.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Command Shell in Externally Accessible Directory - (553)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 552 (Files or Directories Accessible to External Parties) > 553 (Command Shell in Externally Accessible Directory)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource)

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource) > 1004 (Sensitive Cookie Without 'HttpOnly' Flag)

The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource) > 276 (Incorrect Default Permissions)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource) > 277 (Insecure Inherited Permissions)

A product defines a set of insecure permissions that are inherited by objects that are created by the program.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource) > 278 (Insecure Preserved Inherited Permissions)

A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource) > 279 (Incorrect Execution-Assigned Permissions)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource) > 281 (Improper Preservation of Permissions)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 732 (Incorrect Permission Assignment for Critical Resource) > 766 (Critical Data Element Declared Public)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 862 (Missing Authorization)

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.AuthZ

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Write Protection for Parametric Data Values - (1314)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 862 (Missing Authorization) > 1314 (Missing Write Protection for Parametric Data Values)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 862 (Missing Authorization) > 425 (Direct Request ('Forced Browsing'))

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

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 862 (Missing Authorization) > 638 (Not Using Complete Mediation)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 862 (Missing Authorization) > 638 (Not Using Complete Mediation) > 424 (Improper Protection of Alternate Path)

The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources.

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Authorization in Handler for Custom URL Scheme - (939)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 862 (Missing Authorization) > 939 (Improper Authorization in Handler for Custom URL Scheme)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization)

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. This allows attackers to bypass intended access restrictions.AuthZ

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Internal Asset Exposed to Unsafe Debug Access Level or State - (1244)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization) > 1244 (Internal Asset Exposed to Unsafe Debug Access Level or State)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Authorization Before Parsing and Canonicalization - (551)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization) > 551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Authorization Bypass Through User-Controlled Key - (639)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization) > 639 (Authorization Bypass Through User-Controlled Key)

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.Insecure Direct Object Reference / IDORBroken Object Level Authorization / BOLAHorizontal Authorization

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Authorization Bypass Through User-Controlled SQL Primary Key - (566)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization) > 639 (Authorization Bypass Through User-Controlled Key) > 566 (Authorization Bypass Through User-Controlled SQL Primary Key)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Non-Canonical URL Paths for Authorization Decisions - (647)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization) > 647 (Use of Non-Canonical URL Paths for Authorization Decisions)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization) > 804 (Guessable CAPTCHA)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Permissive Cross-domain Policy with Untrusted Domains - (942)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 863 (Incorrect Authorization) > 942 (Permissive Cross-domain Policy with Untrusted Domains)

The product uses a cross-domain policy file that includes domains that should not be trusted.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Export of Android Application Components - (926)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 926 (Improper Export of Android Application Components)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Implicit Intent for Sensitive Communication - (927)

1000 (Research Concepts) > 284 (Improper Access Control) > 285 (Improper Authorization) > 927 (Use of Implicit Intent for Sensitive Communication)

The Android application uses an implicit intent for transmitting sensitive data to other applications.

1000 (Research Concepts) > 284 (Improper Access Control) > 286 (Incorrect User Management)

The product does not properly manage a user within its environment.

1000 (Research Concepts) > 284 (Improper Access Control) > 286 (Incorrect User Management) > 842 (Placement of User into Incorrect Group)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication)

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.authentificationAuthNAuthC

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 1391 (Use of Weak Credentials)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 1391 (Use of Weak Credentials) > 1392 (Use of Default Credentials)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 1391 (Use of Weak Credentials) > 1392 (Use of Default Credentials) > 1393 (Use of Default Password)

The product uses default passwords for potentially critical functionality.

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 1391 (Use of Weak Credentials) > 521 (Weak Password Requirements)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 1391 (Use of Weak Credentials) > 521 (Weak Password Requirements) > 258 (Empty Password in Configuration File)

Using an empty string as a password is insecure.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 1391 (Use of Weak Credentials) > 798 (Use of Hard-coded Credentials)

The product contains hard-coded credentials, such as a password or cryptographic key.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 1391 (Use of Weak Credentials) > 798 (Use of Hard-coded Credentials) > 259 (Use of Hard-coded Password)

The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 262 (Not Using Password Aging)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 263 (Password Aging with Long Expiration)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 289 (Authentication Bypass by Alternate Name)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 290 (Authentication Bypass by Spoofing)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 290 (Authentication Bypass by Spoofing) > 291 (Reliance on IP Address for Authentication)

The product uses an IP address for authentication.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 290 (Authentication Bypass by Spoofing) > 293 (Using Referer Field for Authentication)

The referer field in HTTP requests can be easily modified and, as such, is not a valid means of message integrity checking.referrer

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Reverse DNS Resolution for a Security-Critical Action - (350)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 290 (Authentication Bypass by Spoofing) > 350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 294 (Authentication Bypass by Capture-replay)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reflection Attack in an Authentication Protocol - (301)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 301 (Reflection Attack in an Authentication Protocol)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Authentication Bypass by Assumed-Immutable Data - (302)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 302 (Authentication Bypass by Assumed-Immutable Data)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Implementation of Authentication Algorithm - (303)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 303 (Incorrect Implementation of Authentication Algorithm)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 303 (Incorrect Implementation of Authentication Algorithm) > 304 (Missing Critical Step in Authentication)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 305 (Authentication Bypass by Primary Weakness)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Excessive Authentication Attempts - (307)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 307 (Improper Restriction of Excessive Authentication Attempts)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 308 (Use of Single-factor Authentication)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Password System for Primary Authentication - (309)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 309 (Use of Password System for Primary Authentication)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 522 (Insufficiently Protected Credentials)

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 522 (Insufficiently Protected Credentials) > 256 (Plaintext Storage of a Password)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 522 (Insufficiently Protected Credentials) > 257 (Storing Passwords in a Recoverable Format)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 522 (Insufficiently Protected Credentials) > 260 (Password in Configuration File)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.ASP.NET Misconfiguration: Password in Configuration File - (13)

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.

Using an empty string as a password is insecure.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Misconfiguration: Plaintext Password in Configuration File - (555)

The J2EE application stores a plaintext password in a configuration file.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 522 (Insufficiently Protected Credentials) > 261 (Weak Encoding for Password)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 522 (Insufficiently Protected Credentials) > 523 (Unprotected Transport of Credentials)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 522 (Insufficiently Protected Credentials) > 549 (Missing Password Field Masking)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created - (593)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 593 (Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created)

The product modifies the SSL context after connection creation has begun.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 603 (Use of Client-Side Authentication)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 620 (Unverified Password Change)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Weak Password Recovery Mechanism for Forgotten Password - (640)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 640 (Weak Password Recovery Mechanism for Forgotten Password)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 804 (Guessable CAPTCHA)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Password Hash Instead of Password for Authentication - (836)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 1390 (Weak Authentication) > 836 (Use of Password Hash Instead of Password for Authentication)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 295 (Improper Certificate Validation)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Following of a Certificate's Chain of Trust - (296)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 295 (Improper Certificate Validation) > 296 (Improper Following of a Certificate's Chain of Trust)

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 resource that is associated with that certificate.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Certificate with Host Mismatch - (297)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 295 (Improper Certificate Validation) > 297 (Improper Validation of Certificate with Host Mismatch)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Certificate Expiration - (298)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 295 (Improper Certificate Validation) > 298 (Improper Validation of Certificate Expiration)

A certificate expiration is not validated or is incorrectly validated, so trust may be assigned to certificates that have been abandoned due to age.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 295 (Improper Certificate Validation) > 299 (Improper Check for Certificate Revocation)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Missing Check for Certificate Revocation after Initial Check - (370)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 295 (Improper Certificate Validation) > 299 (Improper Check for Certificate Revocation) > 370 (Missing Check for Certificate Revocation after Initial Check)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 295 (Improper Certificate Validation) > 599 (Missing Validation of OpenSSL Certificate)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Authentication for Critical Function - (306)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 306 (Missing Authentication for Critical Function)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Authentication Bypass Using an Alternate Path or Channel - (288)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 306 (Missing Authentication for Critical Function) > 288 (Authentication Bypass Using an Alternate Path or Channel)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Protection Mechanism for Alternate Hardware Interface - (1299)

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.

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

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 306 (Missing Authentication for Critical Function) > 322 (Key Exchange without Entity Authentication)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Overly Restrictive Account Lockout Mechanism - (645)

1000 (Research Concepts) > 284 (Improper Access Control) > 287 (Improper Authentication) > 645 (Overly Restrictive Account Lockout Mechanism)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 346 (Origin Validation Error)

The product does not properly verify that the source of data or communication is valid.

1000 (Research Concepts) > 284 (Improper Access Control) > 346 (Origin Validation Error) > 1385 (Missing Origin Validation in WebSockets)

The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.Cross-Site WebSocket hijacking (CSWSH)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Verification of Source of a Communication Channel - (940)

1000 (Research Concepts) > 284 (Improper Access Control) > 346 (Origin Validation Error) > 940 (Improper Verification of Source of a Communication Channel)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Verification of Intent by Broadcast Receiver - (925)

1000 (Research Concepts) > 284 (Improper Access Control) > 346 (Origin Validation Error) > 940 (Improper Verification of Source of a Communication Channel) > 925 (Improper Verification of Intent by Broadcast Receiver)

The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.Intent Spoofing

1000 (Research Concepts) > 284 (Improper Access Control) > 749 (Exposed Dangerous Method or Function)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 749 (Exposed Dangerous Method or Function) > 618 (Exposed Unsafe ActiveX Method)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposed IOCTL with Insufficient Access Control - (782)

1000 (Research Concepts) > 284 (Improper Access Control) > 749 (Exposed Dangerous Method or Function) > 782 (Exposed IOCTL with Insufficient Access Control)

The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Cookie with Improper SameSite Attribute - (1275)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 1275 (Sensitive Cookie with Improper SameSite Attribute)

The SameSite attribute for sensitive cookies is not set, or an insecure value is used.

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 291 (Reliance on IP Address for Authentication)

The product uses an IP address for authentication.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Certificate with Host Mismatch - (297)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 297 (Improper Validation of Certificate with Host Mismatch)

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.

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 300 (Channel Accessible by Non-Endpoint)

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.Adversary-in-the-Middle / AITMMan-in-the-Middle / MITMPerson-in-the-Middle / PITMMonkey-in-the-MiddleMonster-in-the-MiddleManipulator-in-the-MiddleOn-path attackInterception attack

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 419 (Unprotected Primary Channel)

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

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 420 (Unprotected Alternate Channel)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Protection Mechanism for Alternate Hardware Interface - (1299)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 420 (Unprotected Alternate Channel) > 1299 (Missing Protection Mechanism for Alternate Hardware Interface)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Race Condition During Access to Alternate Channel - (421)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 420 (Unprotected Alternate Channel) > 421 (Race Condition During Access to Alternate Channel)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Unprotected Windows Messaging Channel ('Shatter') - (422)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 420 (Unprotected Alternate Channel) > 422 (Unprotected Windows Messaging Channel ('Shatter'))

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Verification of Source of a Communication Channel - (940)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 940 (Improper Verification of Source of a Communication Channel)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Verification of Intent by Broadcast Receiver - (925)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 940 (Improper Verification of Source of a Communication Channel) > 925 (Improper Verification of Intent by Broadcast Receiver)

The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.Intent Spoofing

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrectly Specified Destination in a Communication Channel - (941)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 941 (Incorrectly Specified Destination in a Communication Channel)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Permissive Cross-domain Policy with Untrusted Domains - (942)

1000 (Research Concepts) > 284 (Improper Access Control) > 923 (Improper Restriction of Communication Channel to Intended Endpoints) > 942 (Permissive Cross-domain Policy with Untrusted Domains)

The product uses a cross-domain policy file that includes domains that should not be trusted.

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities)

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.Interaction ErrorEmergent Fault

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 1038 (Insecure Automated Optimizations)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Processor Optimization Removal or Modification of Security-critical Code - (1037)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 1038 (Insecure Automated Optimizations) > 1037 (Processor Optimization Removal or Modification of Security-critical Code)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Compiler Optimization Removal or Modification of Security-critical Code - (733)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 1038 (Insecure Automated Optimizations) > 733 (Compiler Optimization Removal or Modification of Security-critical Code)

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.

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

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 188 (Reliance on Data/Memory Layout)

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

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 188 (Reliance on Data/Memory Layout) > 198 (Use of Incorrect Byte Ordering)

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.

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict)

Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') - (113)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict) > 113 (Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting'))

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.HTTP Request SplittingHTTP Response Splitting

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict) > 115 (Misinterpretation of Input)

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

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict) > 437 (Incomplete Model of Endpoint Features)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') - (444)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict) > 444 (Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling'))

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.HTTP Request SmugglingHTTP Response SmugglingHTTP Smuggling

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Null Byte Interaction Error (Poison Null Byte) - (626)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict) > 626 (Null Byte Interaction Error (Poison Null Byte))

The product does not properly handle null bytes or NUL characters when passing data between different representations or components.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Trusting HTTP Permission Methods on the Server Side - (650)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict) > 650 (Trusting HTTP Permission Methods on the Server Side)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Invalid Characters in Identifiers in Web Pages - (86)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 436 (Interpretation Conflict) > 86 (Improper Neutralization of Invalid Characters in Identifiers in Web Pages)

The product does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Behavioral Change in New Version or Environment - (439)

1000 (Research Concepts) > 435 (Improper Interaction Between Multiple Correctly-Behaving Entities) > 439 (Behavioral Change in New Version or Environment)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime)

The product does not maintain or incorrectly maintains control over a resource throughout its lifetime of creation, use, and release.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error'))

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.

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.Buffer Overflowbuffer overrunmemory safety

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') - (120)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 120 (Buffer Copy without Checking Size of Input ('Classic Buffer Overflow'))

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 buffer overflow.Classic Buffer OverflowUnbounded Transfer

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Path Manipulation Function without Maximum-sized Buffer - (785)

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.

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

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Return of Pointer Value Outside of Expected Range - (466)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 466 (Return of Pointer Value Outside of Expected Range)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Access of Memory Location Before Start of Buffer - (786)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 786 (Access of Memory Location Before Start of 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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 786 (Access of Memory Location Before Start of Buffer) > 124 (Buffer Underwrite ('Buffer Underflow'))

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 786 (Access of Memory Location Before Start of Buffer) > 127 (Buffer Under-read)

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer.

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 787 (Out-of-bounds Write) > 121 (Stack-based Buffer Overflow)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 787 (Out-of-bounds Write) > 122 (Heap-based Buffer Overflow)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 787 (Out-of-bounds Write) > 123 (Write-what-where Condition)

Any condition where the attacker has the ability to write an arbitrary value to an arbitrary location, often as the result of a buffer overflow.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 787 (Out-of-bounds Write) > 124 (Buffer Underwrite ('Buffer Underflow'))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Access of Memory Location After End of Buffer - (788)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 788 (Access of Memory Location After End of Buffer)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 788 (Access of Memory Location After End of Buffer) > 121 (Stack-based Buffer Overflow)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 788 (Access of Memory Location After End of Buffer) > 122 (Heap-based Buffer Overflow)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 788 (Access of Memory Location After End of Buffer) > 126 (Buffer Over-read)

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer.

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 805 (Buffer Access with Incorrect Length Value) > 806 (Buffer Access Using Size of Source Buffer)

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.

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

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.Untrusted pointer offset

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

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 825 (Expired Pointer Dereference) > 415 (Double Free)

The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.Double-free

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 118 (Incorrect Access of Indexable Resource ('Range Error')) > 119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) > 825 (Expired Pointer Dereference) > 416 (Use After Free)

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.Dangling pointerUAFUse-After-Free

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1229 (Creation of Emergent Resource)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1229 (Creation of Emergent Resource) > 514 (Covert Channel)

A covert channel is a path that can be used to transfer information in a way not intended by the system's designers.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1229 (Creation of Emergent Resource) > 514 (Covert Channel) > 385 (Covert Timing Channel)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1229 (Creation of Emergent Resource) > 514 (Covert Channel) > 515 (Covert Storage Channel)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Preservation of Consistency Between Independent Representations of Shared State - (1250)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1250 (Improper Preservation of Consistency Between Independent Representations of Shared State)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Application-Level Admin Tool with Inconsistent View of Underlying Operating System - (1249)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1250 (Improper Preservation of Consistency Between Independent Representations of Shared State) > 1249 (Application-Level Admin Tool with Inconsistent View of Underlying Operating System)

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.Ghost in the Shell

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Component That is Not Updateable - (1329)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1329 (Reliance on Component That is Not Updateable)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1329 (Reliance on Component That is Not Updateable) > 1277 (Firmware Not Updateable)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 1329 (Reliance on Component That is Not Updateable) > 1310 (Missing Ability to Patch ROM Code)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission)

The product does not record, or improperly records, security-relevant information that leads to an incorrect decision or hampers later analysis.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Truncation of Security-relevant Information - (222)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 222 (Truncation of Security-relevant Information)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 223 (Omission of Security-relevant Information)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 223 (Omission of Security-relevant Information) > 778 (Insufficient Logging)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Obscured Security-relevant Information by Alternate Name - (224)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 224 (Obscured Security-relevant Information by Alternate Name)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Product UI does not Warn User of Unsafe Actions - (356)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 356 (Product UI does not Warn User of Unsafe Actions)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 396 (Declaration of Catch for Generic Exception)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Declaration of Throws for Generic Exception - (397)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 397 (Declaration of Throws for Generic Exception)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 451 (User Interface (UI) Misrepresentation of Critical Information)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Visual Distinction of Homoglyphs Presented to User - (1007)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 451 (User Interface (UI) Misrepresentation of Critical Information) > 1007 (Insufficient Visual Distinction of Homoglyphs Presented to User)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Rendered UI Layers or Frames - (1021)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 221 (Information Loss or Omission) > 451 (User Interface (UI) Misrepresentation of Critical Information) > 1021 (Improper Restriction of Rendered UI Layers or Frames)

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 confusion about which interface the user is interacting with.ClickjackingUI Redress AttackTapjacking

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 372 (Incomplete Internal State Distinction)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption)

The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.Resource Exhaustion

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations - (1235)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 1235 (Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Write Handling in Limited-write Non-Volatile Memories - (1246)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 1246 (Improper Write Handling in Limited-write Non-Volatile Memories)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Excessive Platform Resource Consumption within a Loop - (1050)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1050 (Excessive Platform Resource Consumption within a Loop)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Data Resource Access without Use of Connection Pooling - (1072)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1072 (Data Resource Access without Use of Connection Pooling)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses - (1073)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1073 (Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invokable Control Element with Excessive File or Data Access Operations - (1084)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1084 (Invokable Control Element with Excessive File or Data Access Operations)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Large Data Table with Excessive Number of Indices - (1089)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1089 (Large Data Table with Excessive Number of Indices)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Excessive Index Range Scan for a Data Resource - (1094)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1094 (Excessive Index Range Scan for a Data Resource)

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

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Static Member Data Element outside of a Singleton Class Element - (1042)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1176 (Inefficient CPU Computation) > 1042 (Static Member Data Element outside of a Singleton Class Element)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Creation of Immutable Text Using String Concatenation - (1046)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1176 (Inefficient CPU Computation) > 1046 (Creation of Immutable Text Using String Concatenation)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Excessive Data Query Operations in a Large Data Table - (1049)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1176 (Inefficient CPU Computation) > 1049 (Excessive Data Query Operations in a Large Data Table)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Creation of Class Instance within a Static Code Block - (1063)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1176 (Inefficient CPU Computation) > 1063 (Creation of Class Instance within a Static Code Block)

A static code block creates an instance of a class.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Excessive Execution of Sequential Searches of Data Resource - (1067)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 1176 (Inefficient CPU Computation) > 1067 (Excessive Execution of Sequential Searches of Data Resource)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 406 (Insufficient Control of Network Message Volume (Network Amplification))

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.

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 407 (Inefficient Algorithmic Complexity) > 1333 (Inefficient Regular Expression Complexity)

The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.ReDoSRegular Expression Denial of ServiceCatastrophic backtracking

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Early Amplification - (408)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 408 (Incorrect Behavior Order: Early Amplification)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Highly Compressed Data (Data Amplification) - (409)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 409 (Improper Handling of Highly Compressed Data (Data Amplification))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') - (776)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 405 (Asymmetric Resource Consumption (Amplification)) > 776 (Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion'))

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.XEEBillion Laughs AttackXML Bomb

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Allocation of Resources Without Limits or Throttling - (770)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 770 (Allocation of Resources Without Limits or Throttling)

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 allocated, in violation of the intended security policy for that actor.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improperly Controlled Sequential Memory Allocation - (1325)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 770 (Allocation of Resources Without Limits or Throttling) > 1325 (Improperly Controlled Sequential Memory Allocation)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Allocation of File Descriptors or Handles Without Limits or Throttling - (774)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 770 (Allocation of Resources Without Limits or Throttling) > 774 (Allocation of File Descriptors or Handles Without Limits or Throttling)

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.File Descriptor Exhaustion

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Memory Allocation with Excessive Size Value - (789)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Reference to Active Allocated Resource - (771)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 771 (Missing Reference to Active Allocated Resource)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Missing Reference to Active File Descriptor or Handle - (773)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 771 (Missing Reference to Active Allocated Resource) > 773 (Missing Reference to Active File Descriptor or Handle)

The product does not properly maintain references to a file descriptor or handle, which prevents that file descriptor/handle from being reclaimed.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 779 (Logging of Excessive Data)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 400 (Uncontrolled Resource Consumption) > 920 (Improper Restriction of Power Consumption)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release)

The product does not release or incorrectly releases a resource before it is made available for re-use.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Scrubbing of Sensitive Data from Decommissioned Device - (1266)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 1266 (Improper Scrubbing of Sensitive Data from Decommissioned Device)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 299 (Improper Check for Certificate Revocation)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Missing Check for Certificate Revocation after Initial Check - (370)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 299 (Improper Check for Certificate Revocation) > 370 (Missing Check for Certificate Revocation after Initial Check)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 459 (Incomplete Cleanup)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Information in Resource Not Removed Before Reuse - (226)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 459 (Incomplete Cleanup) > 226 (Sensitive Information in Resource Not Removed Before Reuse) > 1239 (Improper Zeroization of Hardware Register)

The hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Information Uncleared Before Debug/Power State Transition - (1272)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient or Incomplete Data Removal within Hardware Component - (1301)

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

Confidential information stored in memory circuits is readable or recoverable after being cleared or erased.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Information Exposure through Microarchitectural State after Transient Execution - (1342)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Clearing of Heap Memory Before Release ('Heap Inspection') - (244)

Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 459 (Incomplete Cleanup) > 460 (Improper Cleanup on Thrown Exception)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 459 (Incomplete Cleanup) > 568 (finalize() Method Without super.finalize())

The product contains a finalize() method that does not call super.finalize().

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 763 (Release of Invalid Pointer or Reference)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 763 (Release of Invalid Pointer or Reference) > 761 (Free of Pointer not at Start of Buffer)

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.

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.

The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Release of Resource after Effective Lifetime - (772)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 772 (Missing Release of Resource after Effective Lifetime)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Object without Invoking Destructor Method - (1091)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 772 (Missing Release of Resource after Effective Lifetime) > 1091 (Use of Object without Invoking Destructor Method)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Missing Release of Memory after Effective Lifetime - (401)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 772 (Missing Release of Resource after Effective Lifetime) > 401 (Missing Release of Memory after Effective Lifetime)

The product does not sufficiently track and release allocated memory after it has been used, which slowly consumes remaining memory.Memory Leak

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Missing Release of File Descriptor or Handle after Effective Lifetime - (775)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 404 (Improper Resource Shutdown or Release) > 772 (Missing Release of Resource after Effective Lifetime) > 775 (Missing Release of File Descriptor or Handle after Effective Lifetime)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 410 (Insufficient Resource Pool)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Modification of Assumed-Immutable Data (MAID) - (471)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 471 (Modification of Assumed-Immutable Data (MAID))

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 471 (Modification of Assumed-Immutable Data (MAID)) > 291 (Reliance on IP Address for Authentication)

The product uses an IP address for authentication.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.External Control of Assumed-Immutable Web Parameter - (472)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 471 (Modification of Assumed-Immutable Data (MAID)) > 472 (External Control of Assumed-Immutable Web Parameter)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 471 (Modification of Assumed-Immutable Data (MAID)) > 473 (PHP External Variable Modification)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Public Static Final Field References Mutable Object - (607)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 471 (Modification of Assumed-Immutable Data (MAID)) > 607 (Public Static Final Field References Mutable Object)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 487 (Reliance on Package-level Scope)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Private Data Structure Returned From A Public Method - (495)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 495 (Private Data Structure Returned From A Public Method)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Public Data Assigned to Private Array-Typed Field - (496)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 496 (Public Data Assigned to Private Array-Typed Field)

Assigning public data to a private array is equivalent to giving public access to the array.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 501 (Trust Boundary Violation)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 580 (clone() Method Without super.clone())

The product contains a clone() method that does not call super.clone() to obtain the new object.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere)

The product uses an externally controlled name or reference that resolves to a resource that is outside of the intended control sphere.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.External Control of System or Configuration Setting - (15)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 15 (External Control of System or Configuration Setting)

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

Composite - a Compound Element that consists of two or more distinct weaknesses, in which all weaknesses must be present at the same time in order for a potential vulnerability to arise. Removing any of the weaknesses eliminates or sharply reduces the risk. One weakness, X, can be "broken down" into component weaknesses Y and Z. There can be cases in which one weakness might not be essential to a composite, but changes the nature of the composite when it becomes a vulnerability.Session Fixation - (384)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 384 (Session Fixation)

Authenticating a user, or otherwise establishing a new user session, without invalidating any existing session identifier gives an attacker the opportunity to steal authenticated sessions.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 441 (Unintended Proxy or Intermediary ('Confused Deputy'))

The 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.Confused Deputy

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Rendered UI Layers or Frames - (1021)

The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.XSPA

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') - (470)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 470 (Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection'))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.URL Redirection to Untrusted Site ('Open Redirect') - (601)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 601 (URL Redirection to Untrusted Site ('Open Redirect'))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of XML External Entity Reference - (611)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 611 (Improper Restriction of XML External Entity Reference)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 610 (Externally Controlled Reference to a Resource in Another Sphere) > 73 (External Control of File Name or Path)

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

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization)

The product utilizes multiple threads or processes to allow temporary access to a shared resource that can only be exclusive to one process at a time, but it does not properly synchronize these actions, which might cause simultaneous accesses of this resource by multiple threads or processes.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element - (1058)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 1058 (Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of a Non-reentrant Function in a Concurrent Context - (663)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 663 (Use of a Non-reentrant Function in a Concurrent Context)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Signal Handler Use of a Non-reentrant Function - (479)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 663 (Use of a Non-reentrant Function in a Concurrent Context) > 479 (Signal Handler Use of a Non-reentrant Function)

The product defines a signal handler that calls a non-reentrant function.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of getlogin() in Multithreaded Application - (558)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 663 (Use of a Non-reentrant Function in a Concurrent Context) > 558 (Use of getlogin() in Multithreaded Application)

The product uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking)

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Lock Behavior After Power State Transition - (1232)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 1232 (Improper Lock Behavior After Power State Transition)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Security-Sensitive Hardware Controls with Missing Lock Bit Protection - (1233)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 1233 (Security-Sensitive Hardware Controls with Missing Lock Bit Protection)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Hardware Internal or Debug Modes Allow Override of Locks - (1234)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 1234 (Hardware Internal or Debug Modes Allow Override of Locks)

System configuration protection may be bypassed during debug mode.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 412 (Unrestricted Externally Accessible Lock)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 413 (Improper Resource Locking)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Data Storage in Improperly Locked Memory - (591)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 413 (Improper Resource Locking) > 591 (Sensitive Data Storage in Improperly Locked Memory)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 414 (Missing Lock Check)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 609 (Double-Checked Locking)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 764 (Multiple Locks of a Critical Resource)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 765 (Multiple Unlocks of a Critical Resource)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 832 (Unlock of a Resource that is not Locked)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 667 (Improper Locking) > 833 (Deadlock)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 820 (Missing Synchronization)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Singleton Class Instance Creation without Proper Locking or Synchronization - (1096)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 820 (Missing Synchronization) > 1096 (Singleton Class Instance Creation without Proper Locking or Synchronization)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Singleton Pattern Without Synchronization in a Multithreaded Context - (543)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 820 (Missing Synchronization) > 543 (Use of Singleton Pattern Without Synchronization in a Multithreaded Context)

The product uses the singleton pattern when creating a resource within a multithreaded environment.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Unsynchronized Access to Shared Data in a Multithreaded Context - (567)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 820 (Missing Synchronization) > 567 (Unsynchronized Access to Shared Data in a Multithreaded Context)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Synchronous Access of Remote Resource without Timeout - (1088)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 1088 (Synchronous Access of Remote Resource without Timeout)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Hardware Logic with Insecure De-Synchronization between Control and Data Channels - (1264)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 1264 (Hardware Logic with Insecure De-Synchronization between Control and Data Channels)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 572 (Call to Thread run() instead of start())

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.EJB Bad Practices: Use of Synchronization Primitives - (574)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 574 (EJB Bad Practices: Use of Synchronization Primitives)

The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Cryptographic Operations are run Before Supporting Units are Ready - (1279)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 1279 (Cryptographic Operations are run Before Supporting Units are Ready)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 1419 (Incorrect Initialization of Resource)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Initialization with Hard-Coded Network Resource Configuration Data - (1051)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 1419 (Incorrect Initialization of Resource) > 1051 (Initialization with Hard-Coded Network Resource Configuration Data)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Excessive Use of Hard-Coded Literals in Initialization - (1052)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 1419 (Incorrect Initialization of Resource) > 1052 (Excessive Use of Hard-Coded Literals in Initialization)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Initialization of a Resource with an Insecure Default - (1188)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 1419 (Incorrect Initialization of Resource) > 1188 (Initialization of a Resource with an Insecure Default)

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, by default, initializes an internal variable with an insecure or less secure value than is possible.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Register Defaults or Module Parameters - (1221)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 1419 (Incorrect Initialization of Resource) > 1221 (Incorrect Register Defaults or Module Parameters)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.External Initialization of Trusted Variables or Data Stores - (454)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 1419 (Incorrect Initialization of Resource) > 454 (External Initialization of Trusted Variables or Data Stores)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 455 (Non-exit on Failed Initialization)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Allocation of Resources Without Limits or Throttling - (770)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 770 (Allocation of Resources Without Limits or Throttling)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improperly Controlled Sequential Memory Allocation - (1325)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 770 (Allocation of Resources Without Limits or Throttling) > 1325 (Improperly Controlled Sequential Memory Allocation)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Allocation of File Descriptors or Handles Without Limits or Throttling - (774)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 770 (Allocation of Resources Without Limits or Throttling) > 774 (Allocation of File Descriptors or Handles Without Limits or Throttling)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Memory Allocation with Excessive Size Value - (789)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 908 (Use of Uninitialized Resource)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 908 (Use of Uninitialized Resource) > 457 (Use of Uninitialized Variable)

The code uses a variable that has not been initialized, leading to unpredictable or unintended results.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 909 (Missing Initialization of Resource)

The product does not initialize a critical resource.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Uninitialized Value on Reset for Registers Holding Security Settings - (1271)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 909 (Missing Initialization of Resource) > 1271 (Uninitialized Value on Reset for Registers Holding Security Settings)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 665 (Improper Initialization) > 909 (Missing Initialization of Resource) > 456 (Missing Initialization of a Variable)

The product does not initialize critical variables, which causes the execution environment to use unexpected values.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 666 (Operation on Resource in Wrong Phase of Lifetime)

The product performs an operation on a resource at the wrong phase of the resource's lifecycle, which can lead to unexpected behaviors.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 666 (Operation on Resource in Wrong Phase of Lifetime) > 415 (Double Free)

The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.Double-free

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created - (593)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 666 (Operation on Resource in Wrong Phase of Lifetime) > 593 (Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created)

The product modifies the SSL context after connection creation has begun.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 666 (Operation on Resource in Wrong Phase of Lifetime) > 605 (Multiple Binds to the Same Port)

When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 666 (Operation on Resource in Wrong Phase of Lifetime) > 672 (Operation on a Resource after Expiration or Release)

The product uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Certificate Expiration - (298)

A certificate expiration is not validated or is incorrectly validated, so trust may be assigned to certificates that have been abandoned due to age.

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.

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 dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.Dangling pointer

The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.Double-free

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Premature Release of Resource During Expected Lifetime - (826)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 666 (Operation on Resource in Wrong Phase of Lifetime) > 826 (Premature Release of Resource During Expected Lifetime)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere)

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Isolation of Shared Resources on System-on-a-Chip (SoC) - (1189)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 1189 (Improper Isolation of Shared Resources on System-on-a-Chip (SoC))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Non-Transparent Sharing of Microarchitectural Resources - (1303)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Assumed-Immutable Data is Stored in Writable Memory - (1282)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 1282 (Assumed-Immutable Data is Stored in Writable Memory)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 1327 (Binding to an Unrestricted IP Address)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Isolation of Shared Resources in Network On Chip (NoC) - (1331)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 1331 (Improper Isolation of Shared Resources in Network On Chip (NoC))

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 134 (Use of Externally-Controlled Format String)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor)

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.Information DisclosureInformation Leak

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive System Information Due to Uncleared Debug Information - (1258)

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

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Debug Messages Revealing Unnecessary Information - (1295)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insertion of Sensitive Information Into Sent Data - (201)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of GET Request Method With Sensitive Query Strings - (598)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 201 (Insertion of Sensitive Information Into Sent Data) > 598 (Use of GET Request Method With Sensitive Query Strings)

The web application uses the HTTP GET method to process a request and includes sensitive information in the query string of that request.

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.Side Channel Attack

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Protection of Physical Side Channels - (1300)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Comparison Logic is Vulnerable to Power Side-Channel Attacks - (1255)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 203 (Observable Discrepancy) > 1300 (Improper Protection of Physical Side Channels) > 1255 (Comparison Logic is Vulnerable to Power Side-Channel Attacks)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Non-Transparent Sharing of Microarchitectural Resources - (1303)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 203 (Observable Discrepancy) > 1303 (Non-Transparent Sharing of Microarchitectural Resources)

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

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.

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 203 (Observable Discrepancy) > 205 (Observable Behavioral Discrepancy) > 206 (Observable Internal Behavioral Discrepancy)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Observable Behavioral Discrepancy With Equivalent Products - (207)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 203 (Observable Discrepancy) > 205 (Observable Behavioral Discrepancy) > 207 (Observable Behavioral Discrepancy With Equivalent Products)

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.

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 203 (Observable Discrepancy) > 208 (Observable Timing Discrepancy) > 1254 (Incorrect Comparison Logic Granularity)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Generation of Error Message Containing Sensitive Information - (209)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Self-generated Error Message Containing Sensitive Information - (210)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 209 (Generation of Error Message Containing Sensitive Information) > 210 (Self-generated Error Message Containing Sensitive Information)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Externally-Generated Error Message Containing Sensitive Information - (211)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Information Through Shell Error Message - (535)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information) > 535 (Exposure of Information Through Shell Error Message)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Servlet Runtime Error Message Containing Sensitive Information - (536)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information) > 536 (Servlet Runtime Error Message Containing Sensitive Information)

A servlet error message indicates that there exists an unhandled exception in your web application code and may provide useful information to an attacker.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Java Runtime Error Message Containing Sensitive Information - (537)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information) > 537 (Java Runtime Error Message Containing Sensitive Information)

In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Server-generated Error Message Containing Sensitive Information - (550)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 209 (Generation of Error Message Containing Sensitive Information) > 550 (Server-generated Error Message Containing Sensitive Information)

Certain conditions, such as network failure, will cause a server error message to be displayed.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive Information Due to Incompatible Policies - (213)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insertion of Sensitive Information Into Debugging Code - (215)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Private Personal Information to an Unauthorized Actor - (359)

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.Privacy violationPrivacy leakPrivacy leakage

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive System Information to an Unauthorized Control Sphere - (497)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invocation of Process Using Visible Sensitive Information - (214)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere) > 214 (Invocation of Process Using Visible Sensitive Information)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Information Through Directory Listing - (548)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere) > 548 (Exposure of Information Through Directory Listing)

A directory listing is inappropriately exposed, yielding potentially sensitive information to attackers.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insertion of Sensitive Information into Externally-Accessible File or Directory - (538)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insertion of Sensitive Information into Log File - (532)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 538 (Insertion of Sensitive Information into Externally-Accessible File or Directory) > 532 (Insertion of Sensitive Information into Log File)

Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Inclusion of Sensitive Information in Source Code - (540)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 538 (Insertion of Sensitive Information into Externally-Accessible File or Directory) > 540 (Inclusion of Sensitive Information in Source Code)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Inclusion of Sensitive Information in Test Code - (531)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 538 (Insertion of Sensitive Information into Externally-Accessible File or Directory) > 540 (Inclusion of Sensitive Information in Source Code) > 531 (Inclusion of Sensitive Information in Test Code)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Inclusion of Sensitive Information in an Include File - (541)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 538 (Insertion of Sensitive Information into Externally-Accessible File or Directory) > 540 (Inclusion of Sensitive Information in Source Code) > 541 (Inclusion of Sensitive Information in an Include File)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Inclusion of Sensitive Information in Source Code Comments - (615)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 538 (Insertion of Sensitive Information into Externally-Accessible File or Directory) > 540 (Inclusion of Sensitive Information in Source Code) > 615 (Inclusion of Sensitive Information in Source Code Comments)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of WSDL File Containing Sensitive Information - (651)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 200 (Exposure of Sensitive Information to an Unauthorized Actor) > 538 (Insertion of Sensitive Information into Externally-Accessible File or Directory) > 651 (Exposure of WSDL File Containing Sensitive Information)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') - (22)

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.Directory traversalPath traversal

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 22 (Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')) > 23 (Relative Path Traversal)

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

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Traversal: '\\UNC\share\name\' (Windows UNC Share) - (40)

The product accepts input that identifies a Windows UNC share ('\\UNC\share\name') that potentially redirects access to an unintended location or arbitrary file.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Passing Mutable Objects to an Untrusted Method - (374)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 374 (Passing Mutable Objects to an Untrusted Method)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Returning a Mutable Object to an Untrusted Caller - (375)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 375 (Returning a Mutable Object to an Untrusted Caller)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 377 (Insecure Temporary File)

Creating and using insecure temporary files can leave application and system data vulnerable to attack.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Creation of Temporary File With Insecure Permissions - (378)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 377 (Insecure Temporary File) > 378 (Creation of Temporary File With Insecure Permissions)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Creation of Temporary File in Directory with Insecure Permissions - (379)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 377 (Insecure Temporary File) > 379 (Creation of Temporary File in Directory with Insecure Permissions)

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.

The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product.Resource Leak

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak') - (403)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 402 (Transmission of Private Resources into a New Sphere ('Resource Leak')) > 403 (Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak'))

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.File descriptor leak

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Dangling Database Cursor ('Cursor Injection') - (619)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 402 (Transmission of Private Resources into a New Sphere ('Resource Leak')) > 619 (Dangling Database Cursor ('Cursor Injection'))

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 427 (Uncontrolled Search Path Element)

The product uses a fixed or controlled search path to find resources, but one or more locations in that path can be under the control of unintended actors.DLL preloadingBinary plantingInsecure library loadingDependency confusion

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 428 (Unquoted Search Path or Element)

The product uses a search path that contains an unquoted element, in which the element contains whitespace or other separators. This can cause the product to access resources in a parent path.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 488 (Exposure of Data Element to Wrong Session)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Public cloneable() Method Without Final ('Object Hijack') - (491)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 491 (Public cloneable() Method Without Final ('Object Hijack'))

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Inner Class Containing Sensitive Data - (492)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 492 (Use of Inner Class Containing Sensitive Data)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Critical Public Variable Without Final Modifier - (493)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 493 (Critical Public Variable Without Final Modifier)

The product has a critical public variable that is not final, which allows the variable to be modified to contain unexpected values.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 493 (Critical Public Variable Without Final Modifier) > 500 (Public Static Field Not Marked Final)

An object contains a public static field that is not marked final, which might allow it to be modified in unexpected ways.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cloneable Class Containing Sensitive Information - (498)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 498 (Cloneable Class Containing Sensitive Information)

The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Serializable Class Containing Sensitive Data - (499)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 499 (Serializable Class Containing Sensitive Data)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 522 (Insufficiently Protected Credentials)

The product transmits or stores authentication credentials, but it uses an insecure method that is susceptible to unauthorized interception and/or retrieval.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 522 (Insufficiently Protected Credentials) > 256 (Plaintext Storage of a Password)

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

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.ASP.NET Misconfiguration: Password in Configuration File - (13)

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.

Using an empty string as a password is insecure.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Misconfiguration: Plaintext Password in Configuration File - (555)

The J2EE application stores a plaintext password in a configuration file.

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

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 does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Cache Containing Sensitive Information - (524)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 524 (Use of Cache Containing Sensitive Information)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Web Browser Cache Containing Sensitive Information - (525)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 524 (Use of Cache Containing Sensitive Information) > 525 (Use of Web Browser Cache Containing Sensitive Information)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Files or Directories Accessible to External Parties - (552)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Storage of File with Sensitive Data Under Web Root - (219)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 219 (Storage of File with Sensitive Data Under Web Root)

The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.

The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Storage of File With Sensitive Data Under FTP Root - (220)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 220 (Storage of File With Sensitive Data Under FTP Root)

The product stores sensitive data under the FTP server root with insufficient access control, which might make it accessible to untrusted parties.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Version-Control Repository to an Unauthorized Control Sphere - (527)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 527 (Exposure of Version-Control Repository to an Unauthorized Control Sphere)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Core Dump File to an Unauthorized Control Sphere - (528)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 528 (Exposure of Core Dump File to an Unauthorized Control Sphere)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Access Control List Files to an Unauthorized Control Sphere - (529)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 529 (Exposure of Access Control List Files to an Unauthorized Control Sphere)

The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Backup File to an Unauthorized Control Sphere - (530)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 530 (Exposure of Backup File to an Unauthorized Control Sphere)

A backup file is stored in a directory or archive that is made accessible to unauthorized actors.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Persistent Cookies Containing Sensitive Information - (539)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 539 (Use of Persistent Cookies Containing Sensitive Information)

The web application uses persistent cookies, but the cookies contain sensitive information.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Command Shell in Externally Accessible Directory - (553)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 552 (Files or Directories Accessible to External Parties) > 553 (Command Shell in Externally Accessible Directory)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 582 (Array Declared Public, Final, and Static)

The product declares an array public, final, and static, which is not sufficient to prevent the array's contents from being modified.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 583 (finalize() Method Declared Public)

The product violates secure coding principles for mobile code by declaring a finalize() method public.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Struts: Non-private Field in ActionForm Class - (608)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 608 (Struts: Non-private Field in ActionForm Class)

An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 642 (External Control of Critical State Data)

The product stores security-critical state information about its users, or the product itself, in a location that is accessible to unauthorized actors.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.External Control of System or Configuration Setting - (15)

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

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.External Control of Assumed-Immutable Web Parameter - (472)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Cookies without Validation and Integrity Checking - (565)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 642 (External Control of Critical State Data) > 565 (Reliance on Cookies without Validation and Integrity Checking)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Cookies without Validation and Integrity Checking in a Security Decision - (784)

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.

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 642 (External Control of Critical State Data) > 73 (External Control of File Name or Path) > 114 (Process Control)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 732 (Incorrect Permission Assignment for Critical Resource)

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 732 (Incorrect Permission Assignment for Critical Resource) > 1004 (Sensitive Cookie Without 'HttpOnly' Flag)

The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.

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

A product defines a set of insecure permissions that are inherited by objects that are created by the program.

A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement.

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.

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.

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Access to Critical Private Variable via Public Method - (767)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 767 (Access to Critical Private Variable via Public Method)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Misconfiguration: Entity Bean Declared Remote - (8)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 8 (J2EE Misconfiguration: Entity Bean Declared Remote)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Implicit Intent for Sensitive Communication - (927)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 668 (Exposure of Resource to Wrong Sphere) > 927 (Use of Implicit Intent for Sensitive Communication)

The Android application uses an implicit intent for transmitting sensitive data to other applications.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres)

The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive Information during Transient Execution - (1420)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution - (1421)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 1420 (Exposure of Sensitive Information during Transient Execution) > 1421 (Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution - (1422)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 1420 (Exposure of Sensitive Information during Transient Execution) > 1422 (Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution - (1423)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 1420 (Exposure of Sensitive Information during Transient Execution) > 1423 (Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Removal of Sensitive Information Before Storage or Transfer - (212)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Sensitive System Information Due to Uncleared Debug Information - (1258)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 212 (Improper Removal of Sensitive Information Before Storage or Transfer) > 1258 (Exposure of Sensitive System Information Due to Uncleared Debug Information)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Information in Resource Not Removed Before Reuse - (226)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 212 (Improper Removal of Sensitive Information Before Storage or Transfer) > 226 (Sensitive Information in Resource Not Removed Before Reuse) > 1239 (Improper Zeroization of Hardware Register)

The hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Information Uncleared Before Debug/Power State Transition - (1272)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 212 (Improper Removal of Sensitive Information Before Storage or Transfer) > 226 (Sensitive Information in Resource Not Removed Before Reuse) > 1272 (Sensitive Information Uncleared Before Debug/Power State Transition)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient or Incomplete Data Removal within Hardware Component - (1301)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 212 (Improper Removal of Sensitive Information Before Storage or Transfer) > 226 (Sensitive Information in Resource Not Removed Before Reuse) > 1301 (Insufficient or Incomplete Data Removal within Hardware Component)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 212 (Improper Removal of Sensitive Information Before Storage or Transfer) > 226 (Sensitive Information in Resource Not Removed Before Reuse) > 1301 (Insufficient or Incomplete Data Removal within Hardware Component) > 1330 (Remanent Data Readable after Memory Erase)

Confidential information stored in memory circuits is readable or recoverable after being cleared or erased.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Information Exposure through Microarchitectural State after Transient Execution - (1342)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 212 (Improper Removal of Sensitive Information Before Storage or Transfer) > 226 (Sensitive Information in Resource Not Removed Before Reuse) > 1342 (Information Exposure through Microarchitectural State after Transient Execution)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Clearing of Heap Memory Before Release ('Heap Inspection') - (244)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 212 (Improper Removal of Sensitive Information Before Storage or Transfer) > 226 (Sensitive Information in Resource Not Removed Before Reuse) > 244 (Improper Clearing of Heap Memory Before Release ('Heap Inspection'))

Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Creation of chroot Jail Without Changing Working Directory - (243)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 243 (Creation of chroot Jail Without Changing Working Directory)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Unrestricted Upload of File with Dangerous Type - (434)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 434 (Unrestricted Upload of File with Dangerous Type)

The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.Unrestricted File Upload

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 494 (Download of Code Without Integrity Check)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Inclusion of Functionality from Untrusted Control Sphere - (829)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Document Type Definition - (827)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 669 (Incorrect Resource Transfer Between Spheres) > 829 (Inclusion of Functionality from Untrusted Control Sphere) > 827 (Improper Control of Document Type Definition)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Inclusion of Web Functionality from an Untrusted Source - (830)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') - (98)

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.Remote file includeRFILocal file inclusion

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 673 (External Influence of Sphere Definition)

The product does not prevent the definition of control spheres from external actors.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 673 (External Influence of Sphere Definition) > 426 (Untrusted Search Path)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 704 (Incorrect Type Conversion or Cast)

The product does not correctly convert an object, resource, or structure from one type to a different type.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Parsing of Numbers with Different Radices - (1389)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 704 (Incorrect Type Conversion or Cast) > 1389 (Incorrect Parsing of Numbers with Different Radices)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Attempt to Access Child of a Non-structure Pointer - (588)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 704 (Incorrect Type Conversion or Cast) > 588 (Attempt to Access Child of a Non-structure Pointer)

Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 704 (Incorrect Type Conversion or Cast) > 681 (Incorrect Conversion between Numeric Types)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 704 (Incorrect Type Conversion or Cast) > 681 (Incorrect Conversion between Numeric Types) > 192 (Integer Coercion Error)

Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types.

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.

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.

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.

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Access of Resource Using Incompatible Type ('Type Confusion') - (843)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 704 (Incorrect Type Conversion or Cast) > 843 (Access of Resource Using Incompatible Type ('Type Confusion'))

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.Object Type Confusion

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 178 (Improper Handling of Case Sensitivity)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') - (22)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 22 (Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal'))

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Traversal: '\\UNC\share\name\' (Windows UNC Share) - (40)

The product accepts input that identifies a Windows UNC share ('\\UNC\share\name') that potentially redirects access to an unintended location or arbitrary file.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Symbolic Name not Mapping to Correct Object - (386)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 386 (Symbolic Name not Mapping to Correct Object)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 41 (Improper Resolution of Path Equivalence)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename.' (Trailing Dot) - (42)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 41 (Improper Resolution of Path Equivalence) > 42 (Path Equivalence: 'filename.' (Trailing Dot))

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename....' (Multiple Trailing Dot) - (43)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'file.name' (Internal Dot) - (44)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'file...name' (Multiple Internal Dot) - (45)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename ' (Trailing Space) - (46)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: ' filename' (Leading Space) - (47)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'file name' (Internal Whitespace) - (48)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename/' (Trailing Slash) - (49)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '//multiple/leading/slash' - (50)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '/multiple//internal/slash' - (51)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '/multiple/trailing/slash//' - (52)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '\multiple\\internal\backslash' - (53)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filedir\' (Trailing Backslash) - (54)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '/./' (Single Dot Directory) - (55)

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.

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'fakedir/../realdir/filename' - (57)

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.

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Link Resolution Before File Access ('Link Following') - (59)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 59 (Improper Link Resolution Before File Access ('Link Following'))

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.insecure temporary fileZip Slip

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insecure Operation on Windows Junction / Mount Point - (1386)

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.

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.Symlink followingsymlink vulnerability

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.

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.Windows symbolic link followingsymlink

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of File Names that Identify Virtual Resources - (66)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 66 (Improper Handling of File Names that Identify Virtual Resources)

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.

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Windows ::DATA Alternate Data Stream - (69)

The product does not properly prevent access to, or detect usage of, alternate data streams (ADS).

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Apple HFS+ Alternate Data Stream Path - (72)

The product does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Document Type Definition - (827)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 827 (Improper Control of Document Type Definition)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') - (98)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 706 (Use of Incorrectly-Resolved Name or Reference) > 98 (Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion'))

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 911 (Improper Update of Reference Count)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') - (470)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 470 (Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection'))

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 502 (Deserialization of Untrusted Data)

The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid.Marshaling, UnmarshalingPickling, UnpicklingPHP Object Injection

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Dynamically-Identified Variables - (914)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 914 (Improper Control of Dynamically-Identified Variables)

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

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

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improperly Controlled Modification of Dynamically-Determined Object Attributes - (915)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 915 (Improperly Controlled Modification of Dynamically-Determined Object Attributes)

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.Mass AssignmentAutoBindingPHP Object Injection

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') - (1321)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Generation of Code ('Code Injection') - (94)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Special Elements Used in a Template Engine - (1336)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 94 (Improper Control of Generation of Code ('Code Injection')) > 1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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.Server-Side Template Injection / SSTIClient-Side Template Injection / CSTI

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') - (95)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 94 (Improper Control of Generation of Code ('Code Injection')) > 95 (Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection'))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') - (96)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 94 (Improper Control of Generation of Code ('Code Injection')) > 96 (Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'))

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Server-Side Includes (SSI) Within a Web Page - (97)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 913 (Improper Control of Dynamically-Managed Code Resources) > 94 (Improper Control of Generation of Code ('Code Injection')) > 96 (Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')) > 97 (Improper Neutralization of Server-Side Includes (SSI) Within a Web Page)

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.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 922 (Insecure Storage of Sensitive Information)

The product stores sensitive information without properly limiting read or write access by unauthorized actors.

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 922 (Insecure Storage of Sensitive Information) > 312 (Cleartext Storage of Sensitive Information)

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

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 922 (Insecure Storage of Sensitive Information) > 312 (Cleartext Storage of Sensitive Information) > 313 (Cleartext Storage in a File or on Disk)

The product stores sensitive information in cleartext in a file, or on disk.

The product stores sensitive information in cleartext in the registry.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in a Cookie - (315)

The product stores sensitive information in cleartext in a cookie.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in Memory - (316)

The product stores sensitive information in cleartext in memory.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in GUI - (317)

The product stores sensitive information in cleartext within the GUI.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in Executable - (318)

The product stores sensitive information in cleartext in an executable.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in an Environment Variable - (526)

The product uses an environment variable to store unencrypted sensitive information.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Storage of Sensitive Data in a Mechanism without Access Control - (921)

1000 (Research Concepts) > 664 (Improper Control of a Resource Through its Lifetime) > 922 (Insecure Storage of Sensitive Information) > 921 (Storage of Sensitive Data in a Mechanism without Access Control)

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

1000 (Research Concepts) > 682 (Incorrect Calculation)

The product performs a calculation that generates incorrect or unintended results that are later used in security-critical decisions or resource management.

1000 (Research Concepts) > 682 (Incorrect Calculation) > 128 (Wrap-around Error)

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.

1000 (Research Concepts) > 682 (Incorrect Calculation) > 131 (Incorrect Calculation of Buffer Size)

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

1000 (Research Concepts) > 682 (Incorrect Calculation) > 131 (Incorrect Calculation of Buffer Size) > 467 (Use of sizeof() on a Pointer Type)

The code calls sizeof() on a malloced pointer type, which always returns the wordsize/8. This can produce an unexpected result if the programmer intended to determine how much memory has been allocated.

1000 (Research Concepts) > 682 (Incorrect Calculation) > 1335 (Incorrect Bitwise Shift of Integer)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Precision or Accuracy of a Real Number - (1339)

1000 (Research Concepts) > 682 (Incorrect Calculation) > 1339 (Insufficient Precision or Accuracy of a Real Number)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Calculation of Multi-Byte String Length - (135)

1000 (Research Concepts) > 682 (Incorrect Calculation) > 135 (Incorrect Calculation of Multi-Byte String Length)

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

1000 (Research Concepts) > 682 (Incorrect Calculation) > 190 (Integer Overflow or Wraparound)

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.OverflowWraparoundwrap, wrap-around, wrap around

Chain - a Compound Element that is a sequence of two or more separate weaknesses that can be closely linked together within software. One weakness, X, can directly create the conditions that are necessary to cause another weakness, Y, to enter a vulnerable condition. When this happens, CWE refers to X as "primary" to Y, and Y is "resultant" from X. Chains can involve more than two weaknesses, and in some cases, they might have a tree-like structure.Integer Overflow to Buffer Overflow - (680)

1000 (Research Concepts) > 682 (Incorrect Calculation) > 190 (Integer Overflow or Wraparound) > 680 (Integer Overflow to Buffer Overflow)

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.

1000 (Research Concepts) > 682 (Incorrect Calculation) > 191 (Integer Underflow (Wrap or Wraparound))

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

1000 (Research Concepts) > 682 (Incorrect Calculation) > 193 (Off-by-one Error)

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

1000 (Research Concepts) > 682 (Incorrect Calculation) > 369 (Divide By Zero)

The product divides a value by zero.

1000 (Research Concepts) > 682 (Incorrect Calculation) > 468 (Incorrect Pointer Scaling)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Pointer Subtraction to Determine Size - (469)

1000 (Research Concepts) > 682 (Incorrect Calculation) > 469 (Use of Pointer Subtraction to Determine Size)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management)

The code does not sufficiently manage its control flow during execution, creating conditions in which the control flow can be modified in unexpected ways.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls - (1265)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 1265 (Unintended Reentrant Invocation of Non-reentrant Code Via Nested Calls)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Cryptographic Operations are run Before Supporting Units are Ready - (1279)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 1279 (Cryptographic Operations are run Before Supporting Units are Ready)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Sequence of Processor Instructions Leads to Unexpected Behavior - (1281)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 1281 (Sequence of Processor Instructions Leads to Unexpected Behavior)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'))

The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.

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.

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

The product uses a signal handler that introduces a race condition.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Dangerous Signal Handler not Disabled During Sensitive Operations - (432)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) > 364 (Signal Handler Race Condition) > 432 (Dangerous Signal Handler not Disabled During Sensitive Operations)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Signal Handler with Functionality that is not Asynchronous-Safe - (828)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) > 364 (Signal Handler Race Condition) > 828 (Signal Handler with Functionality that is not Asynchronous-Safe)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Signal Handler Use of a Non-reentrant Function - (479)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) > 364 (Signal Handler Race Condition) > 828 (Signal Handler with Functionality that is not Asynchronous-Safe) > 479 (Signal Handler Use of a Non-reentrant Function)

The product defines a signal handler that calls a non-reentrant function.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Signal Handler Function Associated with Multiple Signals - (831)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) > 364 (Signal Handler Race Condition) > 831 (Signal Handler Function Associated with Multiple Signals)

The product defines a function that is used as a handler for more than one signal.

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Time-of-check Time-of-use (TOCTOU) Race Condition - (367)

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. This can cause the product to perform invalid actions when the resource is in an unexpected state.TOCTTOUTOCCTOU

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 362 (Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) > 367 (Time-of-check Time-of-use (TOCTOU) Race Condition) > 363 (Race Condition Enabling Link Following)

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.

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Race Condition During Access to Alternate Channel - (421)

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

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 430 (Deployment of Wrong Handler)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 431 (Missing Handler)

A handler is not available or implemented.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element - (1058)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 1058 (Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of a Non-reentrant Function in a Concurrent Context - (663)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 663 (Use of a Non-reentrant Function in a Concurrent Context)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Signal Handler Use of a Non-reentrant Function - (479)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 663 (Use of a Non-reentrant Function in a Concurrent Context) > 479 (Signal Handler Use of a Non-reentrant Function)

The product defines a signal handler that calls a non-reentrant function.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of getlogin() in Multithreaded Application - (558)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 663 (Use of a Non-reentrant Function in a Concurrent Context) > 558 (Use of getlogin() in Multithreaded Application)

The product uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking)

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Lock Behavior After Power State Transition - (1232)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 1232 (Improper Lock Behavior After Power State Transition)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Security-Sensitive Hardware Controls with Missing Lock Bit Protection - (1233)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 1233 (Security-Sensitive Hardware Controls with Missing Lock Bit Protection)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Hardware Internal or Debug Modes Allow Override of Locks - (1234)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 1234 (Hardware Internal or Debug Modes Allow Override of Locks)

System configuration protection may be bypassed during debug mode.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 412 (Unrestricted Externally Accessible Lock)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 413 (Improper Resource Locking)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Data Storage in Improperly Locked Memory - (591)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 413 (Improper Resource Locking) > 591 (Sensitive Data Storage in Improperly Locked Memory)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 414 (Missing Lock Check)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 609 (Double-Checked Locking)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 764 (Multiple Locks of a Critical Resource)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 765 (Multiple Unlocks of a Critical Resource)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 832 (Unlock of a Resource that is not Locked)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 667 (Improper Locking) > 833 (Deadlock)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 820 (Missing Synchronization)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Singleton Class Instance Creation without Proper Locking or Synchronization - (1096)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 820 (Missing Synchronization) > 1096 (Singleton Class Instance Creation without Proper Locking or Synchronization)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Singleton Pattern Without Synchronization in a Multithreaded Context - (543)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 820 (Missing Synchronization) > 543 (Use of Singleton Pattern Without Synchronization in a Multithreaded Context)

The product uses the singleton pattern when creating a resource within a multithreaded environment.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Unsynchronized Access to Shared Data in a Multithreaded Context - (567)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 820 (Missing Synchronization) > 567 (Unsynchronized Access to Shared Data in a Multithreaded Context)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Synchronous Access of Remote Resource without Timeout - (1088)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 1088 (Synchronous Access of Remote Resource without Timeout)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Hardware Logic with Insecure De-Synchronization between Control and Data Channels - (1264)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 1264 (Hardware Logic with Insecure De-Synchronization between Control and Data Channels)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 572 (Call to Thread run() instead of start())

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.EJB Bad Practices: Use of Synchronization Primitives - (574)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 662 (Improper Synchronization) > 821 (Incorrect Synchronization) > 574 (EJB Bad Practices: Use of Synchronization Primitives)

The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 480 (Use of Incorrect Operator)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 480 (Use of Incorrect Operator) > 481 (Assigning instead of Comparing)

The code uses an operator for assignment when the intention was to perform a comparison.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 480 (Use of Incorrect Operator) > 482 (Comparing instead of Assigning)

The code uses an operator for comparison when the intention was to perform an assignment.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 480 (Use of Incorrect Operator) > 597 (Use of Wrong Operator in String Comparison)

The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 483 (Incorrect Block Delimitation)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 484 (Omitted Break Statement in Switch)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 617 (Reachable Assertion)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 698 (Execution After Redirect (EAR))

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 670 (Always-Incorrect Control Flow Implementation) > 783 (Operator Precedence Logic Error)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order)

The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.DMA Device Enabled Too Early in Boot Phase - (1190)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 1190 (DMA Device Enabled Too Early in Boot Phase)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Power-On of Untrusted Execution Core Before Enabling Fabric Access Control - (1193)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 1193 (Power-On of Untrusted Execution Core Before Enabling Fabric Access Control)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Access Control Check Implemented After Asset is Accessed - (1280)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 1280 (Access Control Check Implemented After Asset is Accessed)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 179 (Incorrect Behavior Order: Early Validation)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Validate Before Canonicalize - (180)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 179 (Incorrect Behavior Order: Early Validation) > 180 (Incorrect Behavior Order: Validate Before Canonicalize)

The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Validate Before Filter - (181)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 179 (Incorrect Behavior Order: Early Validation) > 181 (Incorrect Behavior Order: Validate Before Filter)

The product validates data before it has been filtered, which prevents the product from detecting data that becomes invalid after the filtering step.Validate-before-cleanse

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Early Amplification - (408)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 408 (Incorrect Behavior Order: Early Amplification)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Authorization Before Parsing and Canonicalization - (551)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 696 (Incorrect Behavior Order) > 551 (Incorrect Behavior Order: Authorization Before Parsing and Canonicalization)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping)

The product does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 248 (Uncaught Exception)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 248 (Uncaught Exception) > 600 (Uncaught Exception in Servlet )

The Servlet does not catch all exceptions, which may reveal sensitive debugging information.Missing Catch Block

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 382 (J2EE Bad Practices: Use of System.exit())

A J2EE application uses System.exit(), which also shuts down its container.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of NullPointerException Catch to Detect NULL Pointer Dereference - (395)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 395 (Use of NullPointerException Catch to Detect NULL Pointer Dereference)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 396 (Declaration of Catch for Generic Exception)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Declaration of Throws for Generic Exception - (397)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 397 (Declaration of Throws for Generic Exception)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 455 (Non-exit on Failed Initialization)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 584 (Return Inside Finally Block)

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 705 (Incorrect Control Flow Scoping) > 698 (Execution After Redirect (EAR))

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

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 768 (Incorrect Short Circuit Evaluation)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 799 (Improper Control of Interaction Frequency)

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.Insufficient anti-automationBrute force

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Excessive Authentication Attempts - (307)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 799 (Improper Control of Interaction Frequency) > 307 (Improper Restriction of Excessive Authentication Attempts)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Enforcement of a Single, Unique Action - (837)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 799 (Improper Control of Interaction Frequency) > 837 (Improper Enforcement of a Single, Unique Action)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 834 (Excessive Iteration)

The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Blocking Code in Single-threaded, Non-blocking Context - (1322)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 834 (Excessive Iteration) > 1322 (Use of Blocking Code in Single-threaded, Non-blocking Context)

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.

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 834 (Excessive Iteration) > 674 (Uncontrolled Recursion)

The product does not properly control the amount of recursion that takes place, consuming excessive resources, such as allocated memory or the program stack.Stack Exhaustion

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion') - (776)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 834 (Excessive Iteration) > 674 (Uncontrolled Recursion) > 776 (Improper Restriction of Recursive Entity References in DTDs ('XML Entity Expansion'))

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Loop with Unreachable Exit Condition ('Infinite Loop') - (835)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 834 (Excessive Iteration) > 835 (Loop with Unreachable Exit Condition ('Infinite Loop'))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Enforcement of Behavioral Workflow - (841)

1000 (Research Concepts) > 691 (Insufficient Control Flow Management) > 841 (Improper Enforcement of Behavioral Workflow)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure)

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1039 (Automated Recognition Mechanism with Inadequate Detection or Handling of Adversarial Input Perturbations)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Semiconductor Defects in Hardware Logic with Security-Sensitive Implications - (1248)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1248 (Semiconductor Defects in Hardware Logic with Security-Sensitive Implications)

The security-sensitive hardware module contains semiconductor defects.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1253 (Incorrect Selection of Fuse 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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Product Released in Non-Release Configuration - (1269)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1269 (Product Released in Non-Release Configuration)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques - (1278)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1278 (Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Public Key Re-Use for Signing both Debug and Production Code - (1291)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1291 (Public Key Re-Use for Signing both Debug and Production Code)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Support for Security Features in On-chip Fabrics or Buses - (1318)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1318 (Missing Support for Security Features in On-chip Fabrics or Buses)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Protection against Electromagnetic Fault Injection (EM-FI) - (1319)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1319 (Improper Protection against Electromagnetic Fault Injection (EM-FI))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Immutable Root of Trust in Hardware - (1326)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1326 (Missing Immutable Root of Trust in Hardware)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Protections Against Hardware Overheating - (1338)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 1338 (Improper Protections Against Hardware Overheating)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 182 (Collapse of Data into Unsafe Value)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 184 (Incomplete List of Disallowed Inputs)

The product implements a protection mechanism that relies on a list of inputs (or properties of inputs) that are not allowed by policy or otherwise require other action to neutralize before additional processing takes place, but the list is incomplete, leading to resultant weaknesses.Denylist / Deny ListBlocklist / Block ListBlacklist / Black List

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 184 (Incomplete List of Disallowed Inputs) > 692 (Incomplete Denylist to Cross-Site Scripting)

The product uses a denylist-based protection mechanism to defend against XSS attacks, but the denylist is incomplete, allowing XSS variants to succeed.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data)

The product does not encrypt sensitive or critical information before storage or transmission.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information) > 313 (Cleartext Storage in a File or on Disk)

The product stores sensitive information in cleartext in a file, or on disk.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information) > 314 (Cleartext Storage in the Registry)

The product stores sensitive information in cleartext in the registry.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in a Cookie - (315)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information) > 315 (Cleartext Storage of Sensitive Information in a Cookie)

The product stores sensitive information in cleartext in a cookie.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in Memory - (316)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information) > 316 (Cleartext Storage of Sensitive Information in Memory)

The product stores sensitive information in cleartext in memory.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in GUI - (317)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information) > 317 (Cleartext Storage of Sensitive Information in GUI)

The product stores sensitive information in cleartext within the GUI.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in Executable - (318)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information) > 318 (Cleartext Storage of Sensitive Information in Executable)

The product stores sensitive information in cleartext in an executable.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Storage of Sensitive Information in an Environment Variable - (526)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 312 (Cleartext Storage of Sensitive Information) > 526 (Cleartext Storage of Sensitive Information in an Environment Variable)

The product uses an environment variable to store unencrypted sensitive information.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Cleartext Transmission of Sensitive Information - (319)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 319 (Cleartext Transmission of Sensitive Information)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Misconfiguration: Data Transmission Without Encryption - (5)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 319 (Cleartext Transmission of Sensitive Information) > 5 (J2EE Misconfiguration: Data Transmission Without Encryption)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Sensitive Cookie in HTTPS Session Without 'Secure' Attribute - (614)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 311 (Missing Encryption of Sensitive Data) > 319 (Cleartext Transmission of Sensitive Information) > 614 (Sensitive Cookie in HTTPS Session Without 'Secure' Attribute)

The Secure attribute for sensitive cookies in HTTPS sessions is not set, which could cause the user agent to send those cookies in plaintext over an HTTP session.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 326 (Inadequate Encryption Strength)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 326 (Inadequate Encryption Strength) > 328 (Use of Weak Hash)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Password Hash With Insufficient Computational Effort - (916)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 326 (Inadequate Encryption Strength) > 328 (Use of Weak Hash) > 916 (Use of Password Hash With Insufficient Computational Effort)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 326 (Inadequate Encryption Strength) > 328 (Use of Weak Hash) > 916 (Use of Password Hash With Insufficient Computational Effort) > 759 (Use of a One-Way Hash without a Salt)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of a One-Way Hash with a Predictable Salt - (760)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 327 (Use of a Broken or Risky Cryptographic Algorithm)

The product uses a broken or risky cryptographic algorithm or protocol.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of a Cryptographic Primitive with a Risky Implementation - (1240)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 327 (Use of a Broken or Risky Cryptographic Algorithm) > 1240 (Use of a Cryptographic Primitive with a Risky Implementation)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 327 (Use of a Broken or Risky Cryptographic Algorithm) > 328 (Use of Weak Hash)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Password Hash With Insufficient Computational Effort - (916)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 327 (Use of a Broken or Risky Cryptographic Algorithm) > 328 (Use of Weak Hash) > 916 (Use of Password Hash With Insufficient Computational Effort)

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.

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of a One-Way Hash with a Predictable Salt - (760)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 327 (Use of a Broken or Risky Cryptographic Algorithm) > 780 (Use of RSA Algorithm without OAEP)

The product uses the RSA algorithm but does not incorporate Optimal Asymmetric Encryption Padding (OAEP), which might weaken the encryption.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values)

The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Generation of Weak Initialization Vector (IV) - (1204)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 1204 (Generation of Weak Initialization Vector (IV))

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 1204 (Generation of Weak Initialization Vector (IV)) > 329 (Generation of Predictable IV with CBC Mode)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Predictable Algorithm in Random Number Generator - (1241)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 1241 (Use of Predictable Algorithm in Random Number Generator)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 331 (Insufficient Entropy)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 331 (Insufficient Entropy) > 332 (Insufficient Entropy in PRNG)

The lack of entropy available for, or used by, a Pseudo-Random Number Generator (PRNG) can be a stability and security threat.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Insufficient Entropy in TRNG - (333)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 331 (Insufficient Entropy) > 333 (Improper Handling of Insufficient Entropy in TRNG)

True random number generators (TRNG) generally have a limited source of entropy and therefore can fail or block.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 334 (Small Space of Random Values)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Misconfiguration: Insufficient Session-ID Length - (6)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 334 (Small Space of Random Values) > 6 (J2EE Misconfiguration: Insufficient Session-ID Length)

The J2EE application is configured to use an insufficient session ID length.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG) - (335)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG))

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Same Seed in Pseudo-Random Number Generator (PRNG) - (336)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)) > 336 (Same Seed in Pseudo-Random Number Generator (PRNG))

A Pseudo-Random Number Generator (PRNG) uses the same seed each time the product is initialized.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Predictable Seed in Pseudo-Random Number Generator (PRNG) - (337)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 335 (Incorrect Usage of Seeds in Pseudo-Random Number Generator (PRNG)) > 337 (Predictable Seed in Pseudo-Random Number Generator (PRNG))

A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.

A Pseudo-Random Number Generator (PRNG) uses a relatively small seed space, which makes it more susceptible to brute force attacks.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG) - (338)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 340 (Generation of Predictable Numbers or Identifiers)

The product uses a scheme that generates numbers or identifiers that are more predictable than required.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 340 (Generation of Predictable Numbers or Identifiers) > 341 (Predictable from Observable State)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Predictable Exact Value from Previous Values - (342)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 340 (Generation of Predictable Numbers or Identifiers) > 342 (Predictable Exact Value from Previous Values)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Predictable Value Range from Previous Values - (343)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 340 (Generation of Predictable Numbers or Identifiers) > 343 (Predictable Value Range from Previous Values)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Invariant Value in Dynamically Changing Context - (344)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 344 (Use of Invariant Value in Dynamically Changing Context)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 344 (Use of Invariant Value in Dynamically Changing Context) > 323 (Reusing a Nonce, Key Pair in Encryption)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 344 (Use of Invariant Value in Dynamically Changing Context) > 587 (Assignment of a Fixed Address to a Pointer)

The product sets a pointer to a specific address other than NULL or 0.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 330 (Use of Insufficiently Random Values) > 344 (Use of Invariant Value in Dynamically Changing Context) > 798 (Use of Hard-coded Credentials)

The product contains hard-coded credentials, such as a password or cryptographic key.

The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity)

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Source Correlation of Multiple Independent Data - (1293)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 1293 (Missing Source Correlation of Multiple Independent Data)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 346 (Origin Validation Error)

The product does not properly verify that the source of data or communication is valid.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 346 (Origin Validation Error) > 1385 (Missing Origin Validation in WebSockets)

The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.Cross-Site WebSocket hijacking (CSWSH)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Verification of Source of a Communication Channel - (940)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 346 (Origin Validation Error) > 940 (Improper Verification of Source of a Communication Channel)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Verification of Intent by Broadcast Receiver - (925)

The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.Intent Spoofing

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Verification of Cryptographic Signature - (347)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 347 (Improper Verification of Cryptographic Signature)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 348 (Use of Less Trusted Source)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Acceptance of Extraneous Untrusted Data With Trusted Data - (349)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 349 (Acceptance of Extraneous Untrusted Data With Trusted Data)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 351 (Insufficient Type Distinction)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 352 (Cross-Site Request Forgery (CSRF))

The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request.Session RidingCross Site Reference ForgeryXSRF

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 353 (Missing Support for Integrity Check)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Integrity Check Value - (354)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 354 (Improper Validation of Integrity Check Value)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 360 (Trust of System Event Data)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Unprotected Windows Messaging Channel ('Shatter') - (422)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 360 (Trust of System Event Data) > 422 (Unprotected Windows Messaging Channel ('Shatter'))

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 494 (Download of Code Without Integrity Check)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Incomplete Identification of Uploaded File Variables (PHP) - (616)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 616 (Incomplete Identification of Uploaded File Variables (PHP))

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Reliance on File Name or Extension of Externally-Supplied File - (646)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 646 (Reliance on File Name or Extension of Externally-Supplied File)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking - (649)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 649 (Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Enforcement of Message Integrity During Transmission in a Communication Channel - (924)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 345 (Insufficient Verification of Data Authenticity) > 924 (Improper Enforcement of Message Integrity During Transmission in a Communication Channel)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient UI Warning of Dangerous Operations - (357)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 357 (Insufficient UI Warning of Dangerous Operations)

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 357 (Insufficient UI Warning of Dangerous Operations) > 450 (Multiple Interpretations of UI Input)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improperly Implemented Security Check for Standard - (358)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 358 (Improperly Implemented Security Check for Standard)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 424 (Improper Protection of Alternate Path)

The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 424 (Improper Protection of Alternate Path) > 425 (Direct Request ('Forced Browsing'))

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

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 602 (Client-Side Enforcement of Server-Side Security)

The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Cookies without Validation and Integrity Checking - (565)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 602 (Client-Side Enforcement of Server-Side Security) > 565 (Reliance on Cookies without Validation and Integrity Checking)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Cookies without Validation and Integrity Checking in a Security Decision - (784)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 602 (Client-Side Enforcement of Server-Side Security) > 565 (Reliance on Cookies without Validation and Integrity Checking) > 784 (Reliance on Cookies without Validation and Integrity Checking in a Security Decision)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 602 (Client-Side Enforcement of Server-Side Security) > 603 (Use of Client-Side Authentication)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 653 (Improper Isolation or Compartmentalization)

The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.Separation of Privilege

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Isolation of Shared Resources on System-on-a-Chip (SoC) - (1189)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 653 (Improper Isolation or Compartmentalization) > 1189 (Improper Isolation of Shared Resources on System-on-a-Chip (SoC))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Non-Transparent Sharing of Microarchitectural Resources - (1303)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 653 (Improper Isolation or Compartmentalization) > 1189 (Improper Isolation of Shared Resources on System-on-a-Chip (SoC)) > 1303 (Non-Transparent Sharing of Microarchitectural Resources)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Isolation of Shared Resources in Network On Chip (NoC) - (1331)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 653 (Improper Isolation or Compartmentalization) > 1331 (Improper Isolation of Shared Resources in Network On Chip (NoC))

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on a Single Factor in a Security Decision - (654)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 654 (Reliance on a Single Factor in a Security Decision)

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.Separation of Privilege

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 654 (Reliance on a Single Factor in a Security Decision) > 308 (Use of Single-factor Authentication)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Password System for Primary Authentication - (309)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 654 (Reliance on a Single Factor in a Security Decision) > 309 (Use of Password System for Primary Authentication)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 655 (Insufficient Psychological Acceptability)

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 656 (Reliance on Security Through Obscurity)

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.Never Assuming your secrets are safe

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade') - (757)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 757 (Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade'))

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.

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 778 (Insufficient Logging)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Untrusted Inputs in a Security Decision - (807)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 807 (Reliance on Untrusted Inputs in a Security Decision)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Authentication Bypass by Assumed-Immutable Data - (302)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 807 (Reliance on Untrusted Inputs in a Security Decision) > 302 (Authentication Bypass by Assumed-Immutable Data)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Reverse DNS Resolution for a Security-Critical Action - (350)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 807 (Reliance on Untrusted Inputs in a Security Decision) > 350 (Reliance on Reverse DNS Resolution for a Security-Critical Action)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Cookies without Validation and Integrity Checking in a Security Decision - (784)

1000 (Research Concepts) > 693 (Protection Mechanism Failure) > 807 (Reliance on Untrusted Inputs in a Security Decision) > 784 (Reliance on Cookies without Validation and Integrity Checking in a Security Decision)

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.

1000 (Research Concepts) > 697 (Incorrect Comparison)

The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1023 (Incomplete Comparison with Missing Factors)

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.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1023 (Incomplete Comparison with Missing Factors) > 184 (Incomplete List of Disallowed Inputs)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1023 (Incomplete Comparison with Missing Factors) > 184 (Incomplete List of Disallowed Inputs) > 692 (Incomplete Denylist to Cross-Site Scripting)

The product uses a denylist-based protection mechanism to defend against XSS attacks, but the denylist is incomplete, allowing XSS variants to succeed.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1023 (Incomplete Comparison with Missing Factors) > 187 (Partial String Comparison)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Default Case in Multiple Condition Expression - (478)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1023 (Incomplete Comparison with Missing Factors) > 478 (Missing Default Case in Multiple Condition Expression)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Numeric Range Comparison Without Minimum Check - (839)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1023 (Incomplete Comparison with Missing Factors) > 839 (Numeric Range Comparison Without Minimum Check)

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

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1024 (Comparison of Incompatible Types)

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.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1025 (Comparison Using Wrong Factors)

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.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1025 (Comparison Using Wrong Factors) > 486 (Comparison of Classes by Name)

The product compares classes by name, which can cause it to use the wrong class when multiple classes can have the same name.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Comparison of Object References Instead of Object Contents - (595)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1025 (Comparison Using Wrong Factors) > 595 (Comparison of Object References Instead of Object Contents)

The product compares object references instead of the contents of the objects themselves, preventing it from detecting equivalent objects.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1025 (Comparison Using Wrong Factors) > 595 (Comparison of Object References Instead of Object Contents) > 597 (Use of Wrong Operator in String Comparison)

The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1039 (Automated Recognition Mechanism with Inadequate Detection or Handling of Adversarial Input Perturbations)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Floating Point Comparison with Incorrect Operator - (1077)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1077 (Floating Point Comparison with Incorrect Operator)

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.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 1254 (Incorrect Comparison Logic Granularity)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 183 (Permissive List of Allowed Inputs)

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.Allowlist / Allow ListSafelist / Safe ListWhitelist / White List

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Permissive Cross-domain Policy with Untrusted Domains - (942)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 183 (Permissive List of Allowed Inputs) > 942 (Permissive Cross-domain Policy with Untrusted Domains)

The product uses a cross-domain policy file that includes domains that should not be trusted.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 185 (Incorrect Regular Expression)

The product specifies a regular expression in a way that causes data to be improperly matched or compared.

1000 (Research Concepts) > 697 (Incorrect Comparison) > 185 (Incorrect Regular Expression) > 186 (Overly Restrictive Regular Expression)

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

1000 (Research Concepts) > 697 (Incorrect Comparison) > 185 (Incorrect Regular Expression) > 625 (Permissive Regular Expression)

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

1000 (Research Concepts) > 697 (Incorrect Comparison) > 185 (Incorrect Regular Expression) > 625 (Permissive Regular Expression) > 777 (Regular Expression without Anchors)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Object Model Violation: Just One of Equals and Hashcode Defined - (581)

1000 (Research Concepts) > 697 (Incorrect Comparison) > 581 (Object Model Violation: Just One of Equals and Hashcode Defined)

The product does not maintain equal hashcodes for equal objects.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions)

The product does not properly anticipate or handle exceptional conditions that rarely occur during normal operation of the product.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 1384 (Improper Handling of Physical or Environmental Conditions)

The product does not properly handle unexpected physical or environmental conditions that occur naturally or are artificially induced.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Protection Against Voltage and Clock Glitches - (1247)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 1384 (Improper Handling of Physical or Environmental Conditions) > 1247 (Improper Protection Against Voltage and Clock Glitches)

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.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 1384 (Improper Handling of Physical or Environmental Conditions) > 1261 (Improper Handling of Single Event Upsets)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Faults that Lead to Instruction Skips - (1332)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 1384 (Improper Handling of Physical or Environmental Conditions) > 1332 (Improper Handling of Faults that Lead to Instruction Skips)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Hardware Behavior in Exceptionally Cold Environments - (1351)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 1384 (Improper Handling of Physical or Environmental Conditions) > 1351 (Improper Handling of Hardware Behavior in Exceptionally Cold Environments)

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.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure)

The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Missing Special Element - (166)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 166 (Improper Handling of Missing Special Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Additional Special Element - (167)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 167 (Improper Handling of Additional Special Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Inconsistent Special Elements - (168)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 168 (Improper Handling of Inconsistent Special Elements)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 229 (Improper Handling of Values)

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.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 229 (Improper Handling of Values) > 230 (Improper Handling of Missing Values)

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.

The product does not handle or incorrectly handles when more values are provided than expected.

The product does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 233 (Improper Handling of Parameters)

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.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 233 (Improper Handling of Parameters) > 234 (Failure to Handle Missing Parameter)

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.

The product does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount.

The product does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Incomplete Structural Elements - (238)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements) > 238 (Improper Handling of Incomplete Structural Elements)

The product does not handle or incorrectly handles when a particular structural element is not completely specified.

The product does not properly handle when a particular element is not completely specified.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Inconsistent Structural Elements - (240)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements) > 240 (Improper Handling of Inconsistent Structural Elements)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Length Parameter Inconsistency - (130)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements) > 240 (Improper Handling of Inconsistent Structural Elements) > 130 (Improper Handling of Length Parameter Inconsistency)

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.length manipulationlength tampering

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 228 (Improper Handling of Syntactically Invalid Structure) > 241 (Improper Handling of Unexpected Data Type)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 393 (Return of Wrong Status Code)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Declaration of Throws for Generic Exception - (397)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 397 (Declaration of Throws for Generic Exception)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions)

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.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 252 (Unchecked Return Value)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 252 (Unchecked Return Value) > 690 (Unchecked Return Value to NULL Pointer Dereference)

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.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 253 (Incorrect Check of Function Return Value)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 273 (Improper Check for Dropped Privileges)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Integrity Check Value - (354)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 354 (Improper Validation of Integrity Check Value)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 391 (Unchecked Error Condition)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 394 (Unexpected Status Code or Return 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.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 754 (Improper Check for Unusual or Exceptional Conditions) > 476 (NULL Pointer Dereference)

The product dereferences a pointer that it expects to be valid but is NULL.NPDnull derefNPEnil pointer dereference

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions)

The product does not handle or incorrectly handles an exceptional condition.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Generation of Error Message Containing Sensitive Information - (209)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Self-generated Error Message Containing Sensitive Information - (210)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 209 (Generation of Error Message Containing Sensitive Information) > 210 (Self-generated Error Message Containing Sensitive Information)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Externally-Generated Error Message Containing Sensitive Information - (211)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Exposure of Information Through Shell Error Message - (535)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information) > 535 (Exposure of Information Through Shell Error Message)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Servlet Runtime Error Message Containing Sensitive Information - (536)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information) > 536 (Servlet Runtime Error Message Containing Sensitive Information)

A servlet error message indicates that there exists an unhandled exception in your web application code and may provide useful information to an attacker.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Java Runtime Error Message Containing Sensitive Information - (537)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 209 (Generation of Error Message Containing Sensitive Information) > 211 (Externally-Generated Error Message Containing Sensitive Information) > 537 (Java Runtime Error Message Containing Sensitive Information)

In many cases, an attacker can leverage the conditions that cause unhandled exception errors in order to gain unauthorized access to the system.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Server-generated Error Message Containing Sensitive Information - (550)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 209 (Generation of Error Message Containing Sensitive Information) > 550 (Server-generated Error Message Containing Sensitive Information)

Certain conditions, such as network failure, will cause a server error message to be displayed.

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 248 (Uncaught Exception)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 248 (Uncaught Exception) > 600 (Uncaught Exception in Servlet )

The Servlet does not catch all exceptions, which may reveal sensitive debugging information.Missing Catch Block

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Insufficient Privileges - (274)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 274 (Improper Handling of Insufficient Privileges)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Insufficient Permissions or Privileges - (280)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 280 (Improper Handling of Insufficient Permissions or Privileges )

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Insufficient Entropy in TRNG - (333)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 333 (Improper Handling of Insufficient Entropy in TRNG)

True random number generators (TRNG) generally have a limited source of entropy and therefore can fail or block.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Detection of Error Condition Without Action - (390)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 390 (Detection of Error Condition Without Action)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 392 (Missing Report of Error Condition)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of NullPointerException Catch to Detect NULL Pointer Dereference - (395)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 395 (Use of NullPointerException Catch to Detect NULL Pointer Dereference)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 396 (Declaration of Catch for Generic Exception)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 460 (Improper Cleanup on Thrown Exception)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Missing Standardized Error Handling Mechanism - (544)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 544 (Missing Standardized Error Handling Mechanism)

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 636 (Not Failing Securely ('Failing Open'))

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

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 636 (Not Failing Securely ('Failing Open')) > 455 (Non-exit on Failed Initialization)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 756 (Missing Custom Error Page)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.ASP.NET Misconfiguration: Missing Custom Error Page - (12)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 756 (Missing Custom Error Page) > 12 (ASP.NET Misconfiguration: Missing Custom Error Page)

An ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Misconfiguration: Missing Custom Error Page - (7)

1000 (Research Concepts) > 703 (Improper Check or Handling of Exceptional Conditions) > 755 (Improper Handling of Exceptional Conditions) > 756 (Missing Custom Error Page) > 7 (J2EE Misconfiguration: Missing Custom Error Page)

The default error page of a web application should not display sensitive information about the product.

1000 (Research Concepts) > 707 (Improper Neutralization)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 116 (Improper Encoding or Escaping of Output)

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.Output SanitizationOutput ValidationOutput Encoding

1000 (Research Concepts) > 707 (Improper Neutralization) > 116 (Improper Encoding or Escaping of Output) > 117 (Improper Output Neutralization for Logs)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of HTTP Headers for Scripting Syntax - (644)

1000 (Research Concepts) > 707 (Improper Neutralization) > 116 (Improper Encoding or Escaping of Output) > 644 (Improper Neutralization of HTTP Headers for Scripting Syntax)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 116 (Improper Encoding or Escaping of Output) > 838 (Inappropriate Encoding for Output Context)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 140 (Improper Neutralization of Delimiters)

The product does not neutralize or incorrectly neutralizes delimiters.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Parameter/Argument Delimiters - (141)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 140 (Improper Neutralization of Delimiters) > 141 (Improper Neutralization of Parameter/Argument Delimiters)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 140 (Improper Neutralization of Delimiters) > 142 (Improper Neutralization of Value Delimiters)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Record Delimiters - (143)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 140 (Improper Neutralization of Delimiters) > 143 (Improper Neutralization of Record Delimiters)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 140 (Improper Neutralization of Delimiters) > 144 (Improper Neutralization of Line Delimiters)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Section Delimiters - (145)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 140 (Improper Neutralization of Delimiters) > 145 (Improper Neutralization of Section Delimiters)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Expression/Command Delimiters - (146)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 140 (Improper Neutralization of Delimiters) > 146 (Improper Neutralization of Expression/Command Delimiters)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Input Terminators - (147)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 147 (Improper Neutralization of Input Terminators)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Null Byte Interaction Error (Poison Null Byte) - (626)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 147 (Improper Neutralization of Input Terminators) > 626 (Null Byte Interaction Error (Poison Null Byte))

The product does not properly handle null bytes or NUL characters when passing data between different representations or components.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 148 (Improper Neutralization of Input Leaders)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 149 (Improper Neutralization of Quoting Syntax)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Escape, Meta, or Control Sequences - (150)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 150 (Improper Neutralization of Escape, Meta, or Control Sequences)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Comment Delimiters - (151)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 151 (Improper Neutralization of Comment Delimiters)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 152 (Improper Neutralization of Macro Symbols)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Substitution Characters - (153)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 153 (Improper Neutralization of Substitution Characters)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Variable Name Delimiters - (154)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 154 (Improper Neutralization of Variable Name Delimiters)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Wildcards or Matching Symbols - (155)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 155 (Improper Neutralization of Wildcards or Matching Symbols)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 155 (Improper Neutralization of Wildcards or Matching Symbols) > 56 (Path Equivalence: 'filedir*' (Wildcard))

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 156 (Improper Neutralization of Whitespace)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 157 (Failure to Sanitize Paired Delimiters)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Null Byte or NUL Character - (158)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 158 (Improper Neutralization of Null Byte or NUL Character)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 159 (Improper Handling of Invalid Use of Special Elements)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Missing Special Element - (166)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 159 (Improper Handling of Invalid Use of Special Elements) > 166 (Improper Handling of Missing Special Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Additional Special Element - (167)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 159 (Improper Handling of Invalid Use of Special Elements) > 167 (Improper Handling of Additional Special Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Inconsistent Special Elements - (168)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 159 (Improper Handling of Invalid Use of Special Elements) > 168 (Improper Handling of Inconsistent Special Elements)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Leading Special Elements - (160)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 160 (Improper Neutralization of Leading Special Elements)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Multiple Leading Special Elements - (161)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 160 (Improper Neutralization of Leading Special Elements) > 161 (Improper Neutralization of Multiple Leading Special Elements)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '//multiple/leading/slash' - (50)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 160 (Improper Neutralization of Leading Special Elements) > 37 (Path Traversal: '/absolute/pathname/here')

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Trailing Special Elements - (162)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 162 (Improper Neutralization of Trailing Special Elements)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Multiple Trailing Special Elements - (163)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 162 (Improper Neutralization of Trailing Special Elements) > 163 (Improper Neutralization of Multiple Trailing Special Elements)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename....' (Multiple Trailing Dot) - (43)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '/multiple/trailing/slash//' - (52)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename.' (Trailing Dot) - (42)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 162 (Improper Neutralization of Trailing Special Elements) > 42 (Path Equivalence: 'filename.' (Trailing Dot))

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename....' (Multiple Trailing Dot) - (43)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename ' (Trailing Space) - (46)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filename/' (Trailing Slash) - (49)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'filedir\' (Trailing Backslash) - (54)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 162 (Improper Neutralization of Trailing Special Elements) > 54 (Path Equivalence: 'filedir\' (Trailing Backslash))

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Internal Special Elements - (164)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 164 (Improper Neutralization of Internal Special Elements)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Multiple Internal Special Elements - (165)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 164 (Improper Neutralization of Internal Special Elements) > 165 (Improper Neutralization of Multiple Internal Special Elements)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: 'file...name' (Multiple Internal Dot) - (45)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Path Equivalence: '\multiple\\internal\backslash' - (53)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 464 (Addition of Data Structure Sentinel)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 790 (Improper Filtering of Special Elements)

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

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Incomplete Filtering of One or More Instances of Special Elements - (792)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 790 (Improper Filtering of Special Elements) > 791 (Incomplete Filtering of Special Elements) > 792 (Incomplete Filtering of One or More Instances of Special Elements)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Only Filtering One Instance of a Special Element - (793)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Incomplete Filtering of Multiple Instances of Special Elements - (794)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Only Filtering Special Elements at a Specified Location - (795)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 790 (Improper Filtering of Special Elements) > 791 (Incomplete Filtering of Special Elements) > 795 (Only Filtering Special Elements at a Specified Location)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Only Filtering Special Elements Relative to a Marker - (796)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 790 (Improper Filtering of Special Elements) > 791 (Incomplete Filtering of Special Elements) > 795 (Only Filtering Special Elements at a Specified Location) > 796 (Only Filtering Special Elements Relative to a Marker)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Only Filtering Special Elements at an Absolute Position - (797)

1000 (Research Concepts) > 707 (Improper Neutralization) > 138 (Improper Neutralization of Special Elements) > 790 (Improper Filtering of Special Elements) > 791 (Incomplete Filtering of Special Elements) > 795 (Only Filtering Special Elements at a Specified Location) > 797 (Only Filtering Special Elements at an Absolute Position)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Generative AI Output - (1426)

1000 (Research Concepts) > 707 (Improper Neutralization) > 1426 (Improper Validation of Generative AI Output)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 170 (Improper Null Termination)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 172 (Encoding Error)

The product does not properly encode or decode the data, resulting in unexpected values.

1000 (Research Concepts) > 707 (Improper Neutralization) > 172 (Encoding Error) > 173 (Improper Handling of Alternate Encoding)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 172 (Encoding Error) > 174 (Double Decoding of the Same Data)

The product decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations.

1000 (Research Concepts) > 707 (Improper Neutralization) > 172 (Encoding Error) > 175 (Improper Handling of Mixed Encoding)

The product does not properly handle when the same input uses several different (mixed) encodings.

1000 (Research Concepts) > 707 (Improper Neutralization) > 172 (Encoding Error) > 176 (Improper Handling of Unicode Encoding)

The product does not properly handle when an input contains Unicode encoding.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of URL Encoding (Hex Encoding) - (177)

1000 (Research Concepts) > 707 (Improper Neutralization) > 172 (Encoding Error) > 177 (Improper Handling of URL Encoding (Hex Encoding))

The product does not properly handle when all or part of an input has been URL encoded.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework) > 102 (Struts: Duplicate Validation Forms)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework) > 105 (Struts: Form Field Without Validator)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework) > 106 (Struts: Plug-in Framework not in Use)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework) > 108 (Struts: Unvalidated Action Form)

Every Action Form must have a corresponding validation form.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework) > 109 (Struts: Validator Turned Off)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.ASP.NET Misconfiguration: Improper Model Validation - (1174)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework) > 1174 (ASP.NET Misconfiguration: Improper Model Validation)

The ASP.NET application does not use, or incorrectly uses, the model validation framework.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.ASP.NET Misconfiguration: Not Using Input Validation Framework - (554)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1173 (Improper Use of Validation Framework) > 554 (ASP.NET Misconfiguration: Not Using Input Validation Framework)

The ASP.NET application does not use an input validation framework.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Specified Quantity in Input - (1284)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1284 (Improper Validation of Specified Quantity in Input)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1284 (Improper Validation of Specified Quantity in Input) > 606 (Unchecked Input for Loop Condition)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Specified Index, Position, or Offset in Input - (1285)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1285 (Improper Validation of Specified Index, Position, or Offset in Input)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1285 (Improper Validation of Specified Index, Position, or Offset in Input) > 129 (Improper Validation of Array Index)

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.out-of-bounds array indexindex-out-of-rangearray index underflow

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code - (781)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1285 (Improper Validation of Specified Index, Position, or Offset in Input) > 781 (Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Syntactic Correctness of Input - (1286)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1286 (Improper Validation of Syntactic Correctness of Input)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1286 (Improper Validation of Syntactic Correctness of Input) > 112 (Missing XML Validation)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Specified Type of Input - (1287)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1287 (Improper Validation of Specified Type of Input)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Consistency within Input - (1288)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1288 (Improper Validation of Consistency within Input)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Unsafe Equivalence in Input - (1289)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 1289 (Improper Validation of Unsafe Equivalence in Input)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 179 (Incorrect Behavior Order: Early Validation)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Validate Before Canonicalize - (180)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 179 (Incorrect Behavior Order: Early Validation) > 180 (Incorrect Behavior Order: Validate Before Canonicalize)

The product validates input before it is canonicalized, which prevents the product from detecting data that becomes invalid after the canonicalization step.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Incorrect Behavior Order: Validate Before Filter - (181)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 179 (Incorrect Behavior Order: Early Validation) > 181 (Incorrect Behavior Order: Validate Before Filter)

The product validates data before it has been filtered, which prevents the product from detecting data that becomes invalid after the filtering step.Validate-before-cleanse

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Validation of Function Hook Arguments - (622)

1000 (Research Concepts) > 707 (Improper Neutralization) > 20 (Improper Input Validation) > 622 (Improper Validation of Function Hook Arguments)

The product adds hooks to user-accessible API functions, but it does not properly validate the arguments. This could lead to resultant vulnerabilities.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure)

The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Missing Special Element - (166)

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 166 (Improper Handling of Missing Special Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Additional Special Element - (167)

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 167 (Improper Handling of Additional Special Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Inconsistent Special Elements - (168)

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 168 (Improper Handling of Inconsistent Special Elements)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 229 (Improper Handling of Values)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 229 (Improper Handling of Values) > 230 (Improper Handling of Missing Values)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 229 (Improper Handling of Values) > 231 (Improper Handling of Extra Values)

The product does not handle or incorrectly handles when more values are provided than expected.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 229 (Improper Handling of Values) > 232 (Improper Handling of Undefined Values)

The product does not handle or incorrectly handles when a value is not defined or supported for the associated parameter, field, or argument name.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 233 (Improper Handling of Parameters)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 233 (Improper Handling of Parameters) > 234 (Failure to Handle Missing Parameter)

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 233 (Improper Handling of Parameters) > 235 (Improper Handling of Extra Parameters)

The product does not handle or incorrectly handles when the number of parameters, fields, or arguments with the same name exceeds the expected amount.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 233 (Improper Handling of Parameters) > 236 (Improper Handling of Undefined Parameters)

The product does not handle or incorrectly handles when a particular parameter, field, or argument name is not defined or supported by the product.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Incomplete Structural Elements - (238)

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements) > 238 (Improper Handling of Incomplete Structural Elements)

The product does not handle or incorrectly handles when a particular structural element is not completely specified.

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements) > 239 (Failure to Handle Incomplete Element)

The product does not properly handle when a particular element is not completely specified.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Inconsistent Structural Elements - (240)

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 237 (Improper Handling of Structural Elements) > 240 (Improper Handling of Inconsistent Structural Elements)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Length Parameter Inconsistency - (130)

1000 (Research Concepts) > 707 (Improper Neutralization) > 228 (Improper Handling of Syntactically Invalid Structure) > 241 (Improper Handling of Unexpected Data Type)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Inconsistent Structural Elements - (240)

1000 (Research Concepts) > 707 (Improper Neutralization) > 240 (Improper Handling of Inconsistent Structural Elements)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Handling of Length Parameter Inconsistency - (130)

1000 (Research Concepts) > 707 (Improper Neutralization) > 240 (Improper Handling of Inconsistent Structural Elements) > 130 (Improper Handling of Length Parameter Inconsistency)

1000 (Research Concepts) > 707 (Improper Neutralization) > 463 (Deletion of Data Structure Sentinel)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'))

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Formula Elements in a CSV File - (1236)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 1236 (Improper Neutralization of Formula Elements in a CSV File)

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.CSV InjectionFormula InjectionExcel Macro Injection

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 75 (Failure to Sanitize Special Elements into a Different Plane (Special Element Injection))

The product does not adequately filter user-controlled input for special elements with control implications.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Equivalent Special Elements - (76)

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

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 77 (Improper Neutralization of Special Elements used in a Command ('Command Injection')) > 624 (Executable Regular Expression Error)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') - (78)

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.Shell injectionShell metacharactersOS Command Injection

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Argument Delimiters in a Command ('Argument Injection') - (88)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection') - (917)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') - (79)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS) - (80)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) > 80 (Improper Neutralization of Script-Related HTML Tags in a Web Page (Basic XSS))

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Script in an Error Message Web Page - (81)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) > 81 (Improper Neutralization of Script in an Error Message Web Page)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Script in Attributes in a Web Page - (83)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) > 83 (Improper Neutralization of Script in Attributes in a Web Page)

The product does not neutralize or incorrectly neutralizes "javascript:" or other URIs from dangerous attributes within tags, such as onmouseover, onload, onerror, or style.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Script in Attributes of IMG Tags in a Web Page - (82)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) > 83 (Improper Neutralization of Script in Attributes in a Web Page) > 82 (Improper Neutralization of Script in Attributes of IMG Tags in a Web Page)

The web application does not neutralize or incorrectly neutralizes scripting elements within attributes of HTML IMG tags, such as the src attribute.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Encoded URI Schemes in a Web Page - (84)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) > 84 (Improper Neutralization of Encoded URI Schemes in a Web Page)

The web application improperly neutralizes user-controlled input for executable script disguised with URI encodings.

The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Invalid Characters in Identifiers in Web Pages - (86)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) > 86 (Improper Neutralization of Invalid Characters in Identifiers in Web Pages)

The product does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Alternate XSS Syntax - (87)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 79 (Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')) > 87 (Improper Neutralization of Alternate XSS Syntax)

The product does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax.

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 91 (XML Injection (aka Blind XPath Injection))

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Data within XPath Expressions ('XPath Injection') - (643)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Data within XQuery Expressions ('XQuery Injection') - (652)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of CRLF Sequences ('CRLF Injection') - (93)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting') - (113)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 93 (Improper Neutralization of CRLF Sequences ('CRLF Injection')) > 113 (Improper Neutralization of CRLF Sequences in HTTP Headers ('HTTP Request/Response Splitting'))

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Generation of Code ('Code Injection') - (94)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Special Elements Used in a Template Engine - (1336)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 94 (Improper Control of Generation of Code ('Code Injection')) > 1336 (Improper Neutralization of Special Elements Used in a Template Engine)

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection') - (95)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 94 (Improper Control of Generation of Code ('Code Injection')) > 95 (Improper Neutralization of Directives in Dynamically Evaluated Code ('Eval Injection'))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection') - (96)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 94 (Improper Control of Generation of Code ('Code Injection')) > 96 (Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection'))

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Server-Side Includes (SSI) Within a Web Page - (97)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 94 (Improper Control of Generation of Code ('Code Injection')) > 96 (Improper Neutralization of Directives in Statically Saved Code ('Static Code Injection')) > 97 (Improper Neutralization of Server-Side Includes (SSI) Within a Web Page)

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.

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Data within XPath Expressions ('XPath Injection') - (643)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic) > 643 (Improper Neutralization of Data within XPath Expressions ('XPath Injection'))

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Data within XQuery Expressions ('XQuery Injection') - (652)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic) > 652 (Improper Neutralization of Data within XQuery Expressions ('XQuery Injection'))

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') - (89)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic) > 89 (Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection'))

The 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.SQL injectionSQLi

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic) > 89 (Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')) > 564 (SQL Injection: Hibernate)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection') - (90)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 943 (Improper Neutralization of Special Elements in Data Query Logic) > 90 (Improper Neutralization of Special Elements used in an LDAP Query ('LDAP Injection'))

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

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.Insecure Direct Object Reference

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Names for Files and Other Resources - (641)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 641 (Improper Restriction of Names for Files and Other Resources)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Multiple Resources with Duplicate Identifier - (694)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 694 (Use of Multiple Resources with Duplicate Identifier)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 694 (Use of Multiple Resources with Duplicate Identifier) > 102 (Struts: Duplicate Validation Forms)

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.

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 694 (Use of Multiple Resources with Duplicate Identifier) > 462 (Duplicate Key in Associative List (Alist))

Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Control of Dynamically-Identified Variables - (914)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 914 (Improper Control of Dynamically-Identified Variables)

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

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 914 (Improper Control of Dynamically-Identified Variables) > 621 (Variable Extraction Error)

1000 (Research Concepts) > 707 (Improper Neutralization) > 74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')) > 99 (Improper Control of Resource Identifiers ('Resource Injection')) > 914 (Improper Control of Dynamically-Identified Variables) > 627 (Dynamic Variable Evaluation)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards)

The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1041 (Use of Redundant Code)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Architecture with Number of Horizontal Layers Outside of Expected Range - (1044)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1044 (Architecture with Number of Horizontal Layers Outside of Expected Range)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invokable Control Element with Large Number of Outward Calls - (1048)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1048 (Invokable Control Element with Large Number of Outward Calls)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1059 (Insufficient Technical Documentation)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1059 (Insufficient Technical Documentation) > 1053 (Missing Documentation for Design)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1059 (Insufficient Technical Documentation) > 1110 (Incomplete Design Documentation)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1059 (Insufficient Technical Documentation) > 1111 (Incomplete I/O Documentation)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Incomplete Documentation of Program Execution - (1112)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1059 (Insufficient Technical Documentation) > 1112 (Incomplete Documentation of Program Execution)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Documentation of Error Handling Techniques - (1118)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1059 (Insufficient Technical Documentation) > 1118 (Insufficient Documentation of Error Handling Techniques)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer - (1054)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1054 (Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Data Access Operations Outside of Expected Data Manager Component - (1057)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1057 (Data Access Operations Outside of Expected Data Manager Component)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Parent Class with References to Child Class - (1062)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1062 (Parent Class with References to Child Class)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Data Access from Outside Expected Data Manager Component - (1083)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1083 (Data Access from Outside Expected Data Manager Component)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Method Containing Access of a Member Element from Another Class - (1090)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1090 (Method Containing Access of a Member Element from Another Class)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Isolation of System-Dependent Functions - (1100)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1100 (Insufficient Isolation of System-Dependent Functions)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Encapsulation of Machine-Dependent Functionality - (1105)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1105 (Insufficient Encapsulation of Machine-Dependent Functionality)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 1105 (Insufficient Encapsulation of Machine-Dependent Functionality) > 188 (Reliance on Data/Memory Layout)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1061 (Insufficient Encapsulation) > 766 (Critical Data Element Declared Public)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Runtime Resource Management Control Element in a Component Built to Run on Application Servers - (1065)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1065 (Runtime Resource Management Control Element in a Component Built to Run on Application Servers)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1066 (Missing Serialization Control Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Inconsistency Between Implementation and Documented Design - (1068)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1068 (Inconsistency Between Implementation and Documented Design)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions)

The product's architecture, source code, design, documentation, or other artifact does not follow required conventions.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor - (1045)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1045 (Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Serializable Data Element Containing non-Serializable Item Elements - (1070)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1070 (Serializable Data Element Containing non-Serializable Item Elements)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1078 (Inappropriate Source Code Style or Formatting)

The source code does not follow desired style or formatting for indentation, white space, comments, etc.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invokable Control Element with Excessive Volume of Commented-out Code - (1085)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1078 (Inappropriate Source Code Style or Formatting) > 1085 (Invokable Control Element with Excessive Volume of Commented-out Code)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Inconsistent Naming Conventions for Identifiers - (1099)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1078 (Inappropriate Source Code Style or Formatting) > 1099 (Inconsistent Naming Conventions for Identifiers)

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.

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Isolation of Symbolic Constant Definitions - (1107)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1078 (Inappropriate Source Code Style or Formatting) > 1107 (Insufficient Isolation of Symbolic Constant Definitions)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Same Variable for Multiple Purposes - (1109)

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.

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

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Source Code Element without Standard Prologue - (1115)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1078 (Inappropriate Source Code Style or Formatting) > 1115 (Source Code Element without Standard Prologue)

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.

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Callable with Insufficient Behavioral Summary - (1117)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1078 (Inappropriate Source Code Style or Formatting) > 1117 (Callable with Insufficient Behavioral Summary)

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.

The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Hard-coded, Security-relevant Constants - (547)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1078 (Inappropriate Source Code Style or Formatting) > 547 (Use of Hard-coded, Security-relevant Constants)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Parent Class without Virtual Destructor Method - (1079)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1079 (Parent Class without Virtual Destructor Method)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Class Instance Self Destruction Control Element - (1082)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1082 (Class Instance Self Destruction Control Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Class with Virtual Method without a Virtual Destructor - (1087)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1087 (Class with Virtual Method without a Virtual Destructor)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Object without Invoking Destructor Method - (1091)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1091 (Use of Object without Invoking Destructor Method)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Persistent Storable Data Element without Associated Comparison Control Element - (1097)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1097 (Persistent Storable Data Element without Associated Comparison Control Element)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Data Element containing Pointer Item without Proper Copy Control Element - (1098)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1098 (Data Element containing Pointer Item without Proper Copy Control Element)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 1108 (Excessive Reliance on Global Variables)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 586 (Explicit Call to Finalize())

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Framework: Saving Unserializable Objects to Disk - (594)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1076 (Insufficient Adherence to Expected Conventions) > 594 (J2EE Framework: Saving Unserializable Objects to Disk)

When the J2EE container attempts to write unserializable objects to disk there is no guarantee that the process will complete successfully.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Same Invokable Control Element in Multiple Architectural Layers - (1092)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1092 (Use of Same Invokable Control Element in Multiple Architectural Layers)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1093 (Excessively Complex Data Representation)

The product uses an unnecessarily complex internal representation for its data structures or interrelationships between those structures.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Data Element Aggregating an Excessively Large Number of Non-Primitive Elements - (1043)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1093 (Excessively Complex Data Representation) > 1043 (Data Element Aggregating an Excessively Large Number of Non-Primitive Elements)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Multiple Inheritance from Concrete Classes - (1055)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1093 (Excessively Complex Data Representation) > 1055 (Multiple Inheritance from Concrete Classes)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1093 (Excessively Complex Data Representation) > 1074 (Class with Excessively Deep Inheritance)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Class with Excessive Number of Child Classes - (1086)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1093 (Excessively Complex Data Representation) > 1086 (Class with Excessive Number of Child Classes)

A class contains an unnecessarily large number of children.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Runtime Component in Generated Code - (1101)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1101 (Reliance on Runtime Component in Generated Code)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity)

The code is too complex, as calculated using a well-defined, quantitative measure.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1047 (Modules with Circular Dependencies)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invokable Control Element with Variadic Parameters - (1056)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1056 (Invokable Control Element with Variadic Parameters)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Excessive Number of Inefficient Server-Side Data Accesses - (1060)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1060 (Excessive Number of Inefficient Server-Side Data Accesses)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Invokable Control Element with Signature Containing an Excessive Number of Parameters - (1064)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1064 (Invokable Control Element with Signature Containing an Excessive Number of Parameters)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Unconditional Control Flow Transfer outside of Switch Block - (1075)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1075 (Unconditional Control Flow Transfer outside of Switch Block)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Source Code File with Excessive Number of Lines of Code - (1080)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1080 (Source Code File with Excessive Number of Lines of Code)

A source code file has too many lines of code.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Loop Condition Value Update within the Loop - (1095)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1095 (Loop Condition Value Update within the Loop)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1119 (Excessive Use of Unconditional Branching)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1121 (Excessive McCabe Cyclomatic Complexity)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1122 (Excessive Halstead Complexity)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1123 (Excessive Use of Self-Modifying Code)

The product uses too much self-modifying code.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1124 (Excessively Deep Nesting)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1120 (Excessive Code Complexity) > 1125 (Excessive Attack Surface)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Declaration of Variable with Unnecessarily Wide Scope - (1126)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1126 (Declaration of Variable with Unnecessarily Wide Scope)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Compilation with Insufficient Warnings or Errors - (1127)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1127 (Compilation with Insufficient Warnings or Errors)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code) > 107 (Struts: Unused Validation Form)

An unused validation form indicates that validation logic is not up-to-date.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code) > 1071 (Empty Code Block)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code) > 1071 (Empty Code Block) > 1069 (Empty Exception Block)

An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code) > 1071 (Empty Code Block) > 585 (Empty Synchronized Block)

The product contains an empty synchronized block.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code) > 110 (Struts: Validator Without Form Field)

Validation fields that do not appear in forms they are associated with indicate that the validation logic is out of date.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code) > 561 (Dead Code)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1164 (Irrelevant Code) > 563 (Assignment to Variable without Use)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1177 (Use of Prohibited Code)

The product uses a function, library, or third party component that has been explicitly prohibited, whether by the developer or the customer.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1177 (Use of Prohibited Code) > 242 (Use of Inherently Dangerous Function)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1177 (Use of Prohibited Code) > 676 (Use of Potentially Dangerous Function)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Use of Path Manipulation Function without Maximum-sized Buffer - (785)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1177 (Use of Prohibited Code) > 676 (Use of Potentially Dangerous Function) > 785 (Use of Path Manipulation Function without Maximum-sized Buffer)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1209 (Failure to Disable Reserved Bits)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1357 (Reliance on Insufficiently Trustworthy Component)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Unmaintained Third Party Components - (1104)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1357 (Reliance on Insufficiently Trustworthy Component) > 1104 (Use of Unmaintained Third Party Components)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Component That is Not Updateable - (1329)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1357 (Reliance on Insufficiently Trustworthy Component) > 1329 (Reliance on Component That is Not Updateable)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 1357 (Reliance on Insufficiently Trustworthy Component) > 1329 (Reliance on Component That is Not Updateable) > 1277 (Firmware Not Updateable)

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.

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 476 (NULL Pointer Dereference)

The product dereferences a pointer that it expects to be valid but is NULL.NPDnull derefNPEnil pointer dereference

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 477 (Use of Obsolete Function)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 484 (Omitted Break Statement in Switch)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 489 (Active Debug Code)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.ASP.NET Misconfiguration: Creating Debug Binary - (11)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 489 (Active Debug Code) > 11 (ASP.NET Misconfiguration: Creating Debug Binary)

Debugging messages help attackers learn about the system and plan a form of attack.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 570 (Expression is Always False)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 571 (Expression is Always True)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller)

The product does not follow or incorrectly follows the specifications as required by the implementation language, environment, framework, protocol, or platform.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Struts: Incomplete validate() Method Definition - (103)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 103 (Struts: Incomplete validate() Method Definition)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Struts: Form Bean Does Not Extend Validation Class - (104)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 104 (Struts: Form Bean Does Not Extend Validation Class)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Creation of chroot Jail Without Changing Working Directory - (243)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 243 (Creation of chroot Jail Without Changing Working Directory)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 253 (Incorrect Check of Function Return Value)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Following of a Certificate's Chain of Trust - (296)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 296 (Improper Following of a Certificate's Chain of Trust)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 304 (Missing Critical Step in Authentication)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 325 (Missing Cryptographic Step)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 329 (Generation of Predictable IV with CBC Mode)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improperly Implemented Security Check for Standard - (358)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 358 (Improperly Implemented Security Check for Standard)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 475 (Undefined Behavior for Input to API)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 568 (finalize() Method Without super.finalize())

The product contains a finalize() method that does not call super.finalize().

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 577 (EJB Bad Practices: Use of Sockets)

The product violates the Enterprise JavaBeans (EJB) specification by using sockets.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 578 (EJB Bad Practices: Use of Class Loader)

The product violates the Enterprise JavaBeans (EJB) specification by using the class loader.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Bad Practices: Non-serializable Object Stored in Session - (579)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 579 (J2EE Bad Practices: Non-serializable Object Stored in Session)

The product stores a non-serializable object as an HttpSession attribute, which can hurt reliability.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 580 (clone() Method Without super.clone())

The product contains a clone() method that does not call super.clone() to obtain the new object.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Object Model Violation: Just One of Equals and Hashcode Defined - (581)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 581 (Object Model Violation: Just One of Equals and Hashcode Defined)

The product does not maintain equal hashcodes for equal objects.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Function Call with Incorrectly Specified Arguments - (628)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 628 (Function Call with Incorrectly Specified Arguments)

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

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Function Call With Incorrect Order of Arguments - (683)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 628 (Function Call with Incorrectly Specified Arguments) > 683 (Function Call With Incorrect Order of Arguments)

The product calls a function, procedure, or routine, but the caller specifies the arguments in an incorrect order, leading to resultant weaknesses.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Function Call With Incorrect Number of Arguments - (685)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 628 (Function Call with Incorrectly Specified Arguments) > 685 (Function Call With Incorrect Number of Arguments)

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.

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Function Call With Incorrectly Specified Argument Value - (687)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 628 (Function Call with Incorrectly Specified Arguments) > 687 (Function Call With Incorrectly Specified Argument Value)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 628 (Function Call with Incorrectly Specified Arguments) > 687 (Function Call With Incorrectly Specified Argument Value) > 560 (Use of umask() with chmod-style Argument)

The product calls umask() with an incorrect argument that is specified as if it is an argument to chmod().

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Function Call With Incorrect Variable or Reference as Argument - (688)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 628 (Function Call with Incorrectly Specified Arguments) > 688 (Function Call With Incorrect Variable or Reference as Argument)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 675 (Multiple Operations on Resource in Single-Operation Context)

The product performs the same operation on a resource two or more times, when the operation should only be applied once.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Multiple Releases of Same Resource or Handle - (1341)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 675 (Multiple Operations on Resource in Single-Operation Context) > 1341 (Multiple Releases of Same Resource or Handle)

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

The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.Double-free

The product decodes the same input twice, which can limit the effectiveness of any protection mechanism that occurs in between the decoding operations.

When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.

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

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Multiple Resources with Duplicate Identifier - (694)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 694 (Use of Multiple Resources with Duplicate Identifier)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 694 (Use of Multiple Resources with Duplicate Identifier) > 102 (Struts: Duplicate Validation Forms)

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.

Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality) > 111 (Direct Use of Unsafe JNI)

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.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.J2EE Bad Practices: Direct Management of Connections - (245)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality) > 245 (J2EE Bad Practices: Direct Management of Connections)

The J2EE application directly manages connections, instead of using the container's connection management facilities.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality) > 246 (J2EE Bad Practices: Direct Use of Sockets)

The J2EE application directly uses sockets instead of using framework method calls.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality) > 383 (J2EE Bad Practices: Direct Use of Threads)

Thread management in a Web application is forbidden in some circumstances and is always highly error prone.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.EJB Bad Practices: Use of Synchronization Primitives - (574)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality) > 574 (EJB Bad Practices: Use of Synchronization Primitives)

The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality) > 575 (EJB Bad Practices: Use of AWT Swing)

The product violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 573 (Improper Following of Specification by Caller) > 695 (Use of Low-Level Functionality) > 576 (EJB Bad Practices: Use of Java I/O)

The product violates the Enterprise JavaBeans (EJB) specification by using the java.io package.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles)

The product violates well-established principles for secure design.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Identifier for IP Block used in System-On-Chip (SOC) - (1192)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 1192 (Improper Identifier for IP Block used in System-On-Chip (SOC))

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 1395 (Dependency on Vulnerable Third-Party Component)

The product has a dependency on a third-party component that contains one or more known vulnerabilities.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 250 (Execution with Unnecessary Privileges)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 636 (Not Failing Securely ('Failing Open'))

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 636 (Not Failing Securely ('Failing Open')) > 455 (Non-exit on Failed Initialization)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 637 (Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism'))

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 638 (Not Using Complete Mediation)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 638 (Not Using Complete Mediation) > 424 (Improper Protection of Alternate Path)

The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources.

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 653 (Improper Isolation or Compartmentalization)

The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.Separation of Privilege

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Isolation of Shared Resources on System-on-a-Chip (SoC) - (1189)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 653 (Improper Isolation or Compartmentalization) > 1189 (Improper Isolation of Shared Resources on System-on-a-Chip (SoC))

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Non-Transparent Sharing of Microarchitectural Resources - (1303)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Isolation of Shared Resources in Network On Chip (NoC) - (1331)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 653 (Improper Isolation or Compartmentalization) > 1331 (Improper Isolation of Shared Resources in Network On Chip (NoC))

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on a Single Factor in a Security Decision - (654)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 654 (Reliance on a Single Factor in a Security Decision)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 654 (Reliance on a Single Factor in a Security Decision) > 308 (Use of Single-factor Authentication)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Password System for Primary Authentication - (309)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 655 (Insufficient Psychological Acceptability)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 656 (Reliance on Security Through Obscurity)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 671 (Lack of Administrator Control over Security)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 671 (Lack of Administrator Control over Security) > 447 (Unimplemented or Unsupported Feature in UI)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 657 (Violation of Secure Design Principles) > 671 (Lack of Administrator Control over Security) > 798 (Use of Hard-coded Credentials)

The product contains hard-coded credentials, such as a password or cryptographic key.

The product contains a hard-coded password, which it uses for its own inbound authentication or for outbound communication to external components.

The use of a hard-coded cryptographic key significantly increases the possibility that encrypted data may be recovered.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality)

The code does not function according to its published specifications, potentially leading to incorrect usage.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Finite State Machines (FSMs) in Hardware Logic - (1245)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 1245 (Improper Finite State Machines (FSMs) in Hardware Logic)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 392 (Missing Report of Error Condition)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 393 (Return of Wrong Status Code)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 440 (Expected Behavior Violation)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 446 (UI Discrepancy for Security Feature)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 446 (UI Discrepancy for Security Feature) > 447 (Unimplemented or Unsupported Feature in UI)

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.

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

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 451 (User Interface (UI) Misrepresentation of Critical Information)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Visual Distinction of Homoglyphs Presented to User - (1007)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 451 (User Interface (UI) Misrepresentation of Critical Information) > 1007 (Insufficient Visual Distinction of Homoglyphs Presented to User)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Improper Restriction of Rendered UI Layers or Frames - (1021)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 451 (User Interface (UI) Misrepresentation of Critical Information) > 1021 (Improper Restriction of Rendered UI Layers or Frames)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 912 (Hidden Functionality)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 912 (Hidden Functionality) > 506 (Embedded Malicious Code)

The product contains code that appears to be malicious in nature.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 684 (Incorrect Provision of Specified Functionality) > 912 (Hidden Functionality) > 506 (Embedded Malicious Code) > 507 (Trojan Horse)

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.

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

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

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.

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.

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 1038 (Insecure Automated Optimizations)

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Processor Optimization Removal or Modification of Security-critical Code - (1037)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 1038 (Insecure Automated Optimizations) > 1037 (Processor Optimization Removal or Modification of Security-critical Code)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Compiler Optimization Removal or Modification of Security-critical Code - (733)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 1038 (Insecure Automated Optimizations) > 733 (Compiler Optimization Removal or Modification of Security-critical Code)

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 1038 (Insecure Automated Optimizations) > 733 (Compiler Optimization Removal or Modification of Security-critical Code) > 14 (Compiler Removal of Code to Clear Buffers)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Reliance on Machine-Dependent Data Representation - (1102)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 1102 (Reliance on Machine-Dependent Data Representation)

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.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Platform-Dependent Third Party Components - (1103)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 1103 (Use of Platform-Dependent Third Party Components)

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

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Insufficient Encapsulation of Machine-Dependent Functionality - (1105)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 1105 (Insufficient Encapsulation of Machine-Dependent Functionality)

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 makes invalid assumptions about how protocol data or memory is organized at a lower level, resulting in unintended program behavior.

Base - a weakness that is still mostly independent of a resource or technology, but with sufficient details to provide specific methods for detection and prevention. Base level weaknesses typically describe issues in terms of 2 or 3 of the following dimensions: behavior, property, technology, language, and resource.Use of Function with Inconsistent Implementations - (474)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 474 (Use of Function with Inconsistent Implementations)

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

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.

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 562 (Return of Stack Variable Address)

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

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 587 (Assignment of a Fixed Address to a Pointer)

The product sets a pointer to a specific address other than NULL or 0.

Variant - a weakness that is linked to a certain type of product, typically involving a specific language or technology. More specific than a Base weakness. Variant level weaknesses typically describe issues in terms of 3 to 5 of the following dimensions: behavior, property, technology, language, and resource.Attempt to Access Child of a Non-structure Pointer - (588)

1000 (Research Concepts) > 710 (Improper Adherence to Coding Standards) > 758 (Reliance on Undefined, Unspecified, or Implementation-Defined Behavior) > 588 (Attempt to Access Child of a Non-structure Pointer)

Casting a non-structure type to a structure type and accessing a field can lead to memory access errors or data corruption.

Vulnerability Mapping Notes

Usage: PROHIBITED

(this CWE ID must not be used to map to real-world vulnerabilities)

Reason: View

Rationale:

This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.

Comments:

Use this View or other Views to search and navigate for the appropriate weakness.

Notes

Other

This view uses a deep hierarchical organization, with more levels of abstraction than other classification schemes. The top-level entries are called Pillars. Where possible, this view uses abstractions that do not consider particular languages, frameworks, technologies, life cycle development phases, frequency of occurrence, or types of resources. It explicitly identifies relationships that form chains and composites, which have not been a formal part of past classification efforts. Chains and composites might help explain why mutual exclusivity is difficult to achieve within security error taxonomies. This view is roughly aligned with MITRE's research into vulnerability theory, especially with respect to behaviors and resources. Ideally, this view will only cover weakness-to-weakness relationships, with minimal overlap and zero categories. It is expected to include at least one parent/child relationship for every weakness within CWE.

View Metrics

	CWEs in this view		Total CWEs
Weaknesses	939	out of	939
Categories	0	out of	374
Views	0	out of	50
Total	939	out of	1363

Content History

Submissions
Submission Date	Submitter	Organization
2008-04-11 (CWE Draft 9, 2008-04-11)	CWE Content Team	MITRE
2008-04-11 (CWE Draft 9, 2008-04-11)
Modifications
Modification Date	Modifier	Organization
2008-09-08	CWE Content Team	MITRE
2008-09-08	updated Description, Name, Relationships, View_Audience, View_Structure
2010-02-16	CWE Content Team	MITRE
2010-02-16	updated Relationships
2018-03-27	CWE Content Team	MITRE
2018-03-27	updated Description, Other_Notes, View_Audience
2020-02-24	CWE Content Team	MITRE
2020-02-24	updated Relationships, View_Audience
2021-03-15	CWE Content Team	MITRE
2021-03-15	updated Description, Other_Notes
2023-06-29	CWE Content Team	MITRE
2023-06-29	updated Mapping_Notes
Previous Entry Names
Change Date	Previous Entry Name
2008-09-09	Natural Hierarchy

Common Weakness Enumeration

CWE VIEW: Research Concepts