View: Comprehensive CWE Dictionary

Draft

Type: Implicit

Objective

This view (slice) covers all the elements in CWE.

Membership

ID	Name	Description
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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().
CWE-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.
CWE-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.
CWE-1039	Inadequate Detection or Handling of Adversarial Input Perturbations in Automated Recognition Mechanism	The product uses an automated mechanism such as machine learning to recognize complex data inputs (e.g. image or audio) as a particular concept or category, but it does not properly detect or handle inputs that have been modified or constructed in a way that causes the mechanism to detect a different, incorrect concept.
CWE-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.
CWE-1041	Use of Redundant Code	The product has multiple functions, methods, procedures, macros, etc. that contain the same code.
CWE-1042	Static Member Data Element outside of a Singleton Class Element	The code contains a member element that is declared as static (but not final), in which its parent class element is not a singleton class - that is, a class element that can be used only once in the 'to' association of a Create action.
CWE-1043	Data Element Aggregating an Excessively Large Number of Non-Primitive Elements	The product uses a data element that has an excessively large number of sub-elements with non-primitive data types such as structures or aggregated objects.
CWE-1044	Architecture with Number of Horizontal Layers Outside of Expected Range	The product's architecture contains too many - or too few - horizontal layers.
CWE-1045	Parent Class with a Virtual Destructor and a Child Class without a Virtual Destructor	A parent class has a virtual destructor method, but the parent has a child class that does not have a virtual destructor.
CWE-1046	Creation of Immutable Text Using String Concatenation	The product creates an immutable text string using string concatenation operations.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1051	Initialization with Hard-Coded Network Resource Configuration Data	The product initializes data using hard-coded values that act as network resource identifiers.
CWE-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.
CWE-1053	Missing Documentation for Design	The product does not have documentation that represents how it is designed.
CWE-1054	Invocation of a Control Element at an Unnecessarily Deep Horizontal Layer	The code at one architectural layer invokes code that resides at a deeper layer than the adjacent layer, i.e., the invocation skips at least one layer, and the invoked code is not part of a vertical utility layer that can be referenced from any horizontal layer.
CWE-1055	Multiple Inheritance from Concrete Classes	The product contains a class with inheritance from more than one concrete class.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1063	Creation of Class Instance within a Static Code Block	A static code block creates an instance of a class.
CWE-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.
CWE-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.
CWE-1066	Missing Serialization Control Element	The product contains a serializable data element that does not have an associated serialization method.
CWE-1067	Excessive Execution of Sequential Searches of Data Resource	The product contains a data query against an SQL table or view that is configured in a way that does not utilize an index and may cause sequential searches to be performed.
CWE-1068	Inconsistency Between Implementation and Documented Design	The implementation of the product is not consistent with the design as described within the relevant documentation.
CWE-1069	Empty Exception Block	An invokable code block contains an exception handling block that does not contain any code, i.e. is empty.
CWE-107	Struts: Unused Validation Form	An unused validation form indicates that validation logic is not up-to-date.
CWE-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.
CWE-1071	Empty Code Block	The source code contains a block that does not contain any code, i.e., the block is empty.
CWE-1072	Data Resource Access without Use of Connection Pooling	The product accesses a data resource through a database without using a connection pooling capability.
CWE-1073	Non-SQL Invokable Control Element with Excessive Number of Data Resource Accesses	The product contains a client with a function or method that contains a large number of data accesses/queries that are sent through a data manager, i.e., does not use efficient database capabilities.
CWE-1074	Class with Excessively Deep Inheritance	A class has an inheritance level that is too high, i.e., it has a large number of parent classes.
CWE-1075	Unconditional Control Flow Transfer outside of Switch Block	The product performs unconditional control transfer (such as a "goto") in code outside of a branching structure such as a switch block.
CWE-1076	Insufficient Adherence to Expected Conventions	The product's architecture, source code, design, documentation, or other artifact does not follow required conventions.
CWE-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.
CWE-1078	Inappropriate Source Code Style or Formatting	The source code does not follow desired style or formatting for indentation, white space, comments, etc.
CWE-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.
CWE-108	Struts: Unvalidated Action Form	Every Action Form must have a corresponding validation form.
CWE-1080	Source Code File with Excessive Number of Lines of Code	A source code file has too many lines of code.
CWE-1082	Class Instance Self Destruction Control Element	The code contains a class instance that calls the method or function to delete or destroy itself.
CWE-1083	Data Access from Outside Expected Data Manager Component	The product is intended to manage data access through a particular data manager component such as a relational or non-SQL database, but it contains code that performs data access operations without using that component.
CWE-1084	Invokable Control Element with Excessive File or Data Access Operations	A function or method contains too many operations that utilize a data manager or file resource.
CWE-1085	Invokable Control Element with Excessive Volume of Commented-out Code	A function, method, procedure, etc. contains an excessive amount of code that has been commented out within its body.
CWE-1086	Class with Excessive Number of Child Classes	A class contains an unnecessarily large number of children.
CWE-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.
CWE-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.
CWE-1089	Large Data Table with Excessive Number of Indices	The product uses a large data table that contains an excessively large number of indices.
CWE-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.
CWE-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.
CWE-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.
CWE-1092	Use of Same Invokable Control Element in Multiple Architectural Layers	The product uses the same control element across multiple architectural layers.
CWE-1093	Excessively Complex Data Representation	The product uses an unnecessarily complex internal representation for its data structures or interrelationships between those structures.
CWE-1094	Excessive Index Range Scan for a Data Resource	The product contains an index range scan for a large data table, but the scan can cover a large number of rows.
CWE-1095	Loop Condition Value Update within the Loop	The product uses a loop with a control flow condition based on a value that is updated within the body of the loop.
CWE-1096	Singleton Class Instance Creation without Proper Locking or Synchronization	The product implements a Singleton design pattern but does not use appropriate locking or other synchronization mechanism to ensure that the singleton class is only instantiated once.
CWE-1097	Persistent Storable Data Element without Associated Comparison Control Element	The product uses a storable data element that does not have all of the associated functions or methods that are necessary to support comparison.
CWE-1098	Data Element containing Pointer Item without Proper Copy Control Element	The code contains a data element with a pointer that does not have an associated copy or constructor method.
CWE-1099	Inconsistent Naming Conventions for Identifiers	The product's code, documentation, or other artifacts do not consistently use the same naming conventions for variables, callables, groups of related callables, I/O capabilities, data types, file names, or similar types of elements.
CWE-11	ASP.NET Misconfiguration: Creating Debug Binary	Debugging messages help attackers learn about the system and plan a form of attack.
CWE-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.
CWE-1100	Insufficient Isolation of System-Dependent Functions	The product or code does not isolate system-dependent functionality into separate standalone modules.
CWE-1101	Reliance on Runtime Component in Generated Code	The product uses automatically-generated code that cannot be executed without a specific runtime support component.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1106	Insufficient Use of Symbolic Constants	The source code uses literal constants that may need to change or evolve over time, instead of using symbolic constants.
CWE-1107	Insufficient Isolation of Symbolic Constant Definitions	The source code uses symbolic constants, but it does not sufficiently place the definitions of these constants into a more centralized or isolated location.
CWE-1108	Excessive Reliance on Global Variables	The code is structured in a way that relies too much on using or setting global variables throughout various points in the code, instead of preserving the associated information in a narrower, more local context.
CWE-1109	Use of Same Variable for Multiple Purposes	The code contains a callable, block, or other code element in which the same variable is used to control more than one unique task or store more than one instance of data.
CWE-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.
CWE-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.
CWE-1111	Incomplete I/O Documentation	The product's documentation does not adequately define inputs, outputs, or system/software interfaces.
CWE-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.
CWE-1113	Inappropriate Comment Style	The source code uses comment styles or formats that are inconsistent or do not follow expected standards for the product.
CWE-1114	Inappropriate Whitespace Style	The source code contains whitespace that is inconsistent across the code or does not follow expected standards for the product.
CWE-1115	Source Code Element without Standard Prologue	The source code contains elements such as source files that do not consistently provide a prologue or header that has been standardized for the project.
CWE-1116	Inaccurate Comments	The source code contains comments that do not accurately describe or explain aspects of the portion of the code with which the comment is associated.
CWE-1117	Callable with Insufficient Behavioral Summary	The code contains a function or method whose signature and/or associated inline documentation does not sufficiently describe the callable's inputs, outputs, side effects, assumptions, or return codes.
CWE-1118	Insufficient Documentation of Error Handling Techniques	The documentation does not sufficiently describe the techniques that are used for error handling, exception processing, or similar mechanisms.
CWE-1119	Excessive Use of Unconditional Branching	The code uses too many unconditional branches (such as "goto").
CWE-112	Missing XML Validation	The product accepts XML from an untrusted source but does not validate the XML against the proper schema.
CWE-1120	Excessive Code Complexity	The code is too complex, as calculated using a well-defined, quantitative measure.
CWE-1121	Excessive McCabe Cyclomatic Complexity	The code contains McCabe cyclomatic complexity that exceeds a desirable maximum.
CWE-1122	Excessive Halstead Complexity	The code is structured in a way that a Halstead complexity measure exceeds a desirable maximum.
CWE-1123	Excessive Use of Self-Modifying Code	The product uses too much self-modifying code.
CWE-1124	Excessively Deep Nesting	The code contains a callable or other code grouping in which the nesting / branching is too deep.
CWE-1125	Excessive Attack Surface	The product has an attack surface whose quantitative measurement exceeds a desirable maximum.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-115	Misinterpretation of Input	The product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.
CWE-116	Improper Encoding or Escaping of Output	The product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly. As a result, the intended structure of the message is not preserved.
CWE-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.
CWE-117	Improper Output Neutralization for Logs	The product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to a log file.
CWE-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.
CWE-1174	ASP.NET Misconfiguration: Improper Model Validation	The ASP.NET application does not use, or incorrectly uses, the model validation framework.
CWE-1176	Inefficient CPU Computation	The product performs CPU computations using algorithms that are not as efficient as they could be for the needs of the developer, i.e., the computations can be optimized further.
CWE-1177	Use of Prohibited Code	The product uses a function, library, or third party component that has been explicitly prohibited, whether by the developer or the customer.
CWE-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.
CWE-1187	DEPRECATED: Use of Uninitialized Resource	This entry has been deprecated because it was a duplicate of CWE-908. All content has been transferred to CWE-908.
CWE-1188	Initialization of a Resource with an Insecure Default	The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
CWE-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.
CWE-119	Improper Restriction of Operations within the Bounds of a Memory Buffer	The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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).
CWE-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().
CWE-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.
CWE-1221	Incorrect Register Defaults or Module Parameters	Hardware description language code incorrectly defines register defaults or hardware Intellectual Property (IP) parameters to insecure values.
CWE-1222	Insufficient Granularity of Address Regions Protected by Register Locks	The product defines a large address region protected from modification by the same register lock control bit. This results in a conflict between the functional requirement that some addresses need to be writable by software during operation and the security requirement that the system configuration lock bit must be set during the boot process.
CWE-1223	Race Condition for Write-Once Attributes	A write-once register in hardware design is programmable by an untrusted software component earlier than the trusted software component, resulting in a race condition issue.
CWE-1224	Improper Restriction of Write-Once Bit Fields	The hardware design control register "sticky bits" or write-once bit fields are improperly implemented, such that they can be reprogrammed by software.
CWE-1229	Creation of Emergent Resource	The product manages resources or behaves in a way that indirectly creates a new, distinct resource that can be used by attackers in violation of the intended policy.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1234	Hardware Internal or Debug Modes Allow Override of Locks	System configuration protection may be bypassed during debug mode.
CWE-1235	Incorrect Use of Autoboxing and Unboxing for Performance Critical Operations	The code uses boxed primitives, which may introduce inefficiencies into performance-critical operations.
CWE-1236	Improper Neutralization of Formula Elements in a CSV File	The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product.
CWE-1239	Improper Zeroization of Hardware Register	The hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes.
CWE-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.
CWE-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.
CWE-1241	Use of Predictable Algorithm in Random Number Generator	The device uses an algorithm that is predictable and generates a pseudo-random number.
CWE-1242	Inclusion of Undocumented Features or Chicken Bits	The device includes chicken bits or undocumented features that can create entry points for unauthorized actors.
CWE-1243	Sensitive Non-Volatile Information Not Protected During Debug	Access to security-sensitive information stored in fuses is not limited during debug.
CWE-1244	Internal Asset Exposed to Unsafe Debug Access Level or State	The product uses physical debug or test interfaces with support for multiple access levels, but it assigns the wrong debug access level to an internal asset, providing unintended access to the asset from untrusted debug agents.
CWE-1245	Improper Finite State Machines (FSMs) in Hardware Logic	Faulty finite state machines (FSMs) in the hardware logic allow an attacker to put the system in an undefined state, to cause a denial of service (DoS) or gain privileges on the victim's system.
CWE-1246	Improper Write Handling in Limited-write Non-Volatile Memories	The product does not implement or incorrectly implements wear leveling operations in limited-write non-volatile memories.
CWE-1247	Improper Protection Against Voltage and Clock Glitches	The device does not contain or contains incorrectly implemented circuitry or sensors to detect and mitigate voltage and clock glitches and protect sensitive information or software contained on the device.
CWE-1248	Semiconductor Defects in Hardware Logic with Security-Sensitive Implications	The security-sensitive hardware module contains semiconductor defects.
CWE-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.
CWE-125	Out-of-bounds Read	The product reads data past the end, or before the beginning, of the intended buffer.
CWE-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.
CWE-1251	Mirrored Regions with Different Values	The product's architecture mirrors regions without ensuring that their contents always stay in sync.
CWE-1252	CPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations	The CPU is not configured to provide hardware support for exclusivity of write and execute operations on memory. This allows an attacker to execute data from all of memory.
CWE-1253	Incorrect Selection of Fuse Values	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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1261	Improper Handling of Single Event Upsets	The hardware logic does not effectively handle when single-event upsets (SEUs) occur.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1267	Policy Uses Obsolete Encoding	The product uses an obsolete encoding mechanism to implement access controls.
CWE-1268	Policy Privileges are not Assigned Consistently Between Control and Data Agents	The product's hardware-enforced access control for a particular resource improperly accounts for privilege discrepancies between control and write policies.
CWE-1269	Product Released in Non-Release Configuration	The product released to market is released in pre-production or manufacturing configuration.
CWE-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.
CWE-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.
CWE-1271	Uninitialized Value on Reset for Registers Holding Security Settings	Security-critical logic is not set to a known value on reset.
CWE-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.
CWE-1273	Device Unlock Credential Sharing	The credentials necessary for unlocking a device are shared across multiple parties and may expose sensitive information.
CWE-1274	Improper Access Control for Volatile Memory Containing Boot Code	The product conducts a secure-boot process that transfers bootloader code from Non-Volatile Memory (NVM) into Volatile Memory (VM), but it does not have sufficient access control or other protections for the Volatile Memory.
CWE-1275	Sensitive Cookie with Improper SameSite Attribute	The SameSite attribute for sensitive cookies is not set, or an insecure value is used.
CWE-1276	Hardware Child Block Incorrectly Connected to Parent System	Signals between a hardware IP and the parent system design are incorrectly connected causing security risks.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1280	Access Control Check Implemented After Asset is Accessed	A product's hardware-based access control check occurs after the asset has been accessed.
CWE-1281	Sequence of Processor Instructions Leads to Unexpected Behavior	Specific combinations of processor instructions lead to undesirable behavior such as locking the processor until a hard reset performed.
CWE-1282	Assumed-Immutable Data is Stored in Writable Memory	Immutable data, such as a first-stage bootloader, device identifiers, and "write-once" configuration settings are stored in writable memory that can be re-programmed or updated in the field.
CWE-1283	Mutable Attestation or Measurement Reporting Data	The register contents used for attestation or measurement reporting data to verify boot flow are modifiable by an adversary.
CWE-1284	Improper Validation of Specified Quantity in Input	The product receives input that is expected to specify a quantity (such as size or length), but it does not validate or incorrectly validates that the quantity has the required properties.
CWE-1285	Improper Validation of Specified Index, Position, or Offset in Input	The product receives input that is expected to specify an index, position, or offset into an indexable resource such as a buffer or file, but it does not validate or incorrectly validates that the specified index/position/offset has the required properties.
CWE-1286	Improper Validation of Syntactic Correctness of Input	The product receives input that is expected to be well-formed - i.e., to comply with a certain syntax - but it does not validate or incorrectly validates that the input complies with the syntax.
CWE-1287	Improper Validation of Specified Type of Input	The product receives input that is expected to be of a certain type, but it does not validate or incorrectly validates that the input is actually of the expected type.
CWE-1288	Improper Validation of Consistency within Input	The product receives a complex input with multiple elements or fields that must be consistent with each other, but it does not validate or incorrectly validates that the input is actually consistent.
CWE-1289	Improper Validation of Unsafe Equivalence in Input	The product receives an input value that is used as a resource identifier or other type of reference, but it does not validate or incorrectly validates that the input is equivalent to a potentially-unsafe value.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1295	Debug Messages Revealing Unnecessary Information	The product fails to adequately prevent the revealing of unnecessary and potentially sensitive system information within debugging messages.
CWE-1296	Incorrect Chaining or Granularity of Debug Components	The product's debug components contain incorrect chaining or granularity of debug components.
CWE-1297	Unprotected Confidential Information on Device is Accessible by OSAT Vendors	The product does not adequately protect confidential information on the device from being accessed by Outsourced Semiconductor Assembly and Test (OSAT) vendors.
CWE-1298	Hardware Logic Contains Race Conditions	A race condition in the hardware logic results in undermining security guarantees of the system.
CWE-1299	Missing Protection Mechanism for Alternate Hardware Interface	The lack of protections on alternate paths to access control-protected assets (such as unprotected shadow registers and other external facing unguarded interfaces) allows an attacker to bypass existing protections to the asset that are only performed against the primary path.
CWE-13	ASP.NET Misconfiguration: Password in Configuration File	Storing a plaintext password in a configuration file allows anyone who can read the file access to the password-protected resource making them an easy target for attackers.
CWE-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.
CWE-1300	Improper Protection of Physical Side Channels	The device does not contain sufficient protection mechanisms to prevent physical side channels from exposing sensitive information due to patterns in physically observable phenomena such as variations in power consumption, electromagnetic emissions (EME), or acoustic emissions.
CWE-1301	Insufficient or Incomplete Data Removal within Hardware Component	The product's data removal process does not completely delete all data and potentially sensitive information within hardware components.
CWE-1302	Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)	The product implements a security identifier mechanism to differentiate what actions are allowed or disallowed when a transaction originates from an entity. A transaction is sent without a security identifier.
CWE-1303	Non-Transparent Sharing of Microarchitectural Resources	Hardware structures shared across execution contexts (e.g., caches and branch predictors) can violate the expected architecture isolation between contexts.
CWE-1304	Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation	The product performs a power save/restore operation, but it does not ensure that the integrity of the configuration state is maintained and/or verified between the beginning and ending of the operation.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-132	DEPRECATED: Miscalculated Null Termination	This entry has been deprecated because it was a duplicate of CWE-170. All content has been transferred to CWE-170.
CWE-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.
CWE-1321	Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution')	The product receives input from an upstream component that specifies attributes that are to be initialized or updated in an object, but it does not properly control modifications of attributes of the object prototype.
CWE-1322	Use of Blocking Code in Single-threaded, Non-blocking Context	The product uses a non-blocking model that relies on a single threaded process for features such as scalability, but it contains code that can block when it is invoked.
CWE-1323	Improper Management of Sensitive Trace Data	Trace data collected from several sources on the System-on-Chip (SoC) is stored in unprotected locations or transported to untrusted agents.
CWE-1324	DEPRECATED: Sensitive Information Accessible by Physical Probing of JTAG Interface	This entry has been deprecated because it was at a lower level of abstraction than supported by CWE. All relevant content has been integrated into CWE-319.
CWE-1325	Improperly Controlled Sequential Memory Allocation	The product manages a group of objects or resources and performs a separate memory allocation for each object, but it does not properly limit the total amount of memory that is consumed by all of the combined objects.
CWE-1326	Missing Immutable Root of Trust in Hardware	A missing immutable root of trust in the hardware results in the ability to bypass secure boot or execute untrusted or adversarial boot code.
CWE-1327	Binding to an Unrestricted IP Address	The product assigns the address 0.0.0.0 for a database server, a cloud service/instance, or any computing resource that communicates remotely.
CWE-1328	Security Version Number Mutable to Older Versions	Security-version number in hardware is mutable, resulting in the ability to downgrade (roll-back) the boot firmware to vulnerable code versions.
CWE-1329	Reliance on Component That is Not Updateable	The product contains a component that cannot be updated or patched in order to remove vulnerabilities or significant bugs.
CWE-1330	Remanent Data Readable after Memory Erase	Confidential information stored in memory circuits is readable or recoverable after being cleared or erased.
CWE-1331	Improper Isolation of Shared Resources in Network On Chip (NoC)	The Network On Chip (NoC) does not isolate or incorrectly isolates its on-chip-fabric and internal resources such that they are shared between trusted and untrusted agents, creating timing channels.
CWE-1332	Improper Handling of Faults that Lead to Instruction Skips	The device is missing or incorrectly implements circuitry or sensors that detect and mitigate the skipping of security-critical CPU instructions when they occur.
CWE-1333	Inefficient Regular Expression Complexity	The product uses a regular expression with an inefficient, possibly exponential worst-case computational complexity that consumes excessive CPU cycles.
CWE-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.
CWE-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.
CWE-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.
CWE-1338	Improper Protections Against Hardware Overheating	A hardware device is missing or has inadequate protection features to prevent overheating.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-1386	Insecure Operation on Windows Junction / Mount Point	The product opens a file or directory, but it does not properly prevent the name from being associated with a junction or mount point to a destination that is outside of the intended control sphere.
CWE-1389	Incorrect Parsing of Numbers with Different Radices	The product parses numeric input assuming base 10 (decimal) values, but it does not account for inputs that use a different base number (radix).
CWE-1390	Weak Authentication	The product uses an authentication mechanism to restrict access to specific users or identities, but the mechanism does not sufficiently prove that the claimed identity is correct.
CWE-1391	Use of Weak Credentials	The product uses weak credentials (such as a default key or hard-coded password) that can be calculated, derived, reused, or guessed by an attacker.
CWE-1392	Use of Default Credentials	The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality.
CWE-1393	Use of Default Password	The product uses default passwords for potentially critical functionality.
CWE-1394	Use of Default Cryptographic Key	The product uses a default cryptographic key for potentially critical functionality.
CWE-1395	Dependency on Vulnerable Third-Party Component	The product has a dependency on a third-party component that contains one or more known vulnerabilities.
CWE-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."
CWE-140	Improper Neutralization of Delimiters	The product does not neutralize or incorrectly neutralizes delimiters.
CWE-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.
CWE-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.
CWE-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.
CWE-1420	Exposure of Sensitive Information during Transient Execution	A processor event or prediction may allow incorrect operations (or correct operations with incorrect data) to execute transiently, potentially exposing data over a covert channel.
CWE-1421	Exposure of Sensitive Information in Shared Microarchitectural Structures during Transient Execution	A processor event may allow transient operations to access architecturally restricted data (for example, in another address space) in a shared microarchitectural structure (for example, a CPU cache), potentially exposing the data over a covert channel.
CWE-1422	Exposure of Sensitive Information caused by Incorrect Data Forwarding during Transient Execution	A processor event or prediction may allow incorrect or stale data to be forwarded to transient operations, potentially exposing data over a covert channel.
CWE-1423	Exposure of Sensitive Information caused by Shared Microarchitectural Predictor State that Influences Transient Execution	Shared microarchitectural predictor state may allow code to influence transient execution across a hardware boundary, potentially exposing data that is accessible beyond the boundary over a covert channel.
CWE-1426	Improper Validation of Generative AI Output	The product invokes a generative AI/ML component whose behaviors and outputs cannot be directly controlled, but the product does not validate or insufficiently validates the outputs to ensure that they align with the intended security, content, or privacy policy.
CWE-1427	Improper Neutralization of Input Used for LLM Prompting	The product uses externally-provided data to build prompts provided to large language models (LLMs), but the way these prompts are constructed causes the LLM to fail to distinguish between user-supplied inputs and developer provided system directives.
CWE-1428	Reliance on HTTP instead of HTTPS	The product provides or relies on use of HTTP communications when HTTPS is available.
CWE-1429	Missing Security-Relevant Feedback for Unexecuted Operations in Hardware Interface	The product has a hardware interface that silently discards operations in situations for which feedback would be security-relevant, such as the timely detection of failures or attacks.
CWE-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.
CWE-1431	Driving Intermediate Cryptographic State/Results to Hardware Module Outputs	The product uses a hardware module implementing a cryptographic algorithm that writes sensitive information about the intermediate state or results of its cryptographic operations via one of its output wires (typically the output port containing the final result).
CWE-1434	Insecure Setting of Generative AI/ML Model Inference Parameters	The product has a component that relies on a generative AI/ML model configured with inference parameters that produce an unacceptably high rate of erroneous or unexpected outputs.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-15	External Control of System or Configuration Setting	One or more system settings or configuration elements can be externally controlled by a user.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-170	Improper Null Termination	The product does not terminate or incorrectly terminates a string or array with a null character or equivalent terminator.
CWE-172	Encoding Error	The product does not properly encode or decode the data, resulting in unexpected values.
CWE-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.
CWE-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.
CWE-175	Improper Handling of Mixed Encoding	The product does not properly handle when the same input uses several different (mixed) encodings.
CWE-176	Improper Handling of Unicode Encoding	The product does not properly handle when an input contains Unicode encoding.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-185	Incorrect Regular Expression	The product specifies a regular expression in a way that causes data to be improperly matched or compared.
CWE-186	Overly Restrictive Regular Expression	A regular expression is overly restrictive, which prevents dangerous values from being detected.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-192	Integer Coercion Error	Integer coercion refers to a set of flaws pertaining to the type casting, extension, or truncation of primitive data types.
CWE-193	Off-by-one Error	A product calculates or uses an incorrect maximum or minimum value that is 1 more, or 1 less, than the correct value.
CWE-194	Unexpected Sign Extension	The product performs an operation on a number that causes it to be sign extended when it is transformed into a larger data type. When the original number is negative, this can produce unexpected values that lead to resultant weaknesses.
CWE-195	Signed to Unsigned Conversion Error	The product uses a signed primitive and performs a cast to an unsigned primitive, which can produce an unexpected value if the value of the signed primitive can not be represented using an unsigned primitive.
CWE-196	Unsigned to Signed Conversion Error	The product uses an unsigned primitive and performs a cast to a signed primitive, which can produce an unexpected value if the value of the unsigned primitive can not be represented using a signed primitive.
CWE-197	Numeric Truncation Error	Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.
CWE-198	Use of Incorrect Byte Ordering	The product receives input from an upstream component, but it does not account for byte ordering (e.g. big-endian and little-endian) when processing the input, causing an incorrect number or value to be used.
CWE-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.
CWE-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.
CWE-201	Insertion of Sensitive Information Into Sent Data	The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
CWE-202	Exposure of Sensitive Information Through Data Queries	When trying to keep information confidential, an attacker can often infer some of the information by using statistics.
CWE-203	Observable Discrepancy	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.
CWE-204	Observable Response Discrepancy	The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
CWE-205	Observable Behavioral Discrepancy	The product's behaviors indicate important differences that may be observed by unauthorized actors in a way that reveals (1) its internal state or decision process, or (2) differences from other products with equivalent functionality.
CWE-206	Observable Internal Behavioral Discrepancy	The product performs multiple behaviors that are combined to produce a single result, but the individual behaviors are observable separately in a way that allows attackers to reveal internal state or internal decision points.
CWE-207	Observable Behavioral Discrepancy With Equivalent Products	The product operates in an environment in which its existence or specific identity should not be known, but it behaves differently than other products with equivalent functionality, in a way that is observable to an attacker.
CWE-208	Observable Timing Discrepancy	Two separate operations in a product require different amounts of time to complete, in a way that is observable to an actor and reveals security-relevant information about the state of the product, such as whether a particular operation was successful or not.
CWE-209	Generation of Error Message Containing Sensitive Information	The product generates an error message that includes sensitive information about its environment, users, or associated data.
CWE-210	Self-generated Error Message Containing Sensitive Information	The product identifies an error condition and creates its own diagnostic or error messages that contain sensitive information.
CWE-211	Externally-Generated Error Message Containing Sensitive Information	The product performs an operation that triggers an external diagnostic or error message that is not directly generated or controlled by the product, such as an error generated by the programming language interpreter that a software application uses. The error can contain sensitive system information.
CWE-212	Improper Removal of Sensitive Information Before Storage or Transfer	The product stores, transfers, or shares a resource that contains sensitive information, but it does not properly remove that information before the product makes the resource available to unauthorized actors.
CWE-213	Exposure of Sensitive Information Due to Incompatible Policies	The product's intended functionality exposes information to certain actors in accordance with the developer's security policy, but this information is regarded as sensitive according to the intended security policies of other stakeholders such as the product's administrator, users, or others whose information is being processed.
CWE-214	Invocation of Process Using Visible Sensitive Information	A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.
CWE-215	Insertion of Sensitive Information Into Debugging Code	The product inserts sensitive information into debugging code, which could expose this information if the debugging code is not disabled in production.
CWE-216	DEPRECATED: Containment Errors (Container Errors)	This entry has been deprecated, as it was not effective as a weakness and was structured more like a category. In addition, the name is inappropriate, since the "container" term is widely understood by developers in different ways than originally intended by PLOVER, the original source for this entry.
CWE-217	DEPRECATED: Failure to Protect Stored Data from Modification	This entry has been deprecated because it incorporated and confused multiple weaknesses. The issues formerly covered in this entry can be found at CWE-766 and CWE-767.
CWE-218	DEPRECATED: Failure to provide confidentiality for stored data	This weakness has been deprecated because it was a duplicate of CWE-493. All content has been transferred to CWE-493.
CWE-219	Storage of File with Sensitive Data Under Web Root	The product stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.
CWE-22	Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')	The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-225	DEPRECATED: General Information Management Problems	This weakness can be found at CWE-199.
CWE-226	Sensitive Information in Resource Not Removed Before Reuse	The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.
CWE-228	Improper Handling of Syntactically Invalid Structure	The product does not handle or incorrectly handles input that is not syntactically well-formed with respect to the associated specification.
CWE-229	Improper Handling of Values	The product does not properly handle when the expected number of values for parameters, fields, or arguments is not provided in input, or if those values are undefined.
CWE-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.
CWE-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.
CWE-231	Improper Handling of Extra Values	The product does not handle or incorrectly handles when more values are provided than expected.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-237	Improper Handling of Structural Elements	The product does not handle or incorrectly handles inputs that are related to complex structures.
CWE-238	Improper Handling of Incomplete Structural Elements	The product does not handle or incorrectly handles when a particular structural element is not completely specified.
CWE-239	Failure to Handle Incomplete Element	The product does not properly handle when a particular element is not completely specified.
CWE-24	Path Traversal: '../filedir'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "../" sequences that can resolve to a location that is outside of that directory.
CWE-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.
CWE-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).
CWE-242	Use of Inherently Dangerous Function	The product calls a function that can never be guaranteed to work safely.
CWE-243	Creation of chroot Jail Without Changing Working Directory	The product uses the chroot() system call to create a jail, but does not change the working directory afterward. This does not prevent access to files outside of the jail.
CWE-244	Improper Clearing of Heap Memory Before Release ('Heap Inspection')	Using realloc() to resize buffers that store sensitive information can leave the sensitive information exposed to attack, because it is not removed from memory.
CWE-245	J2EE Bad Practices: Direct Management of Connections	The J2EE application directly manages connections, instead of using the container's connection management facilities.
CWE-246	J2EE Bad Practices: Direct Use of Sockets	The J2EE application directly uses sockets instead of using framework method calls.
CWE-247	DEPRECATED: Reliance on DNS Lookups in a Security Decision	This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.
CWE-248	Uncaught Exception	An exception is thrown from a function, but it is not caught.
CWE-249	DEPRECATED: Often Misused: Path Manipulation	This entry has been deprecated because of name confusion and an accidental combination of multiple weaknesses. Most of its content has been transferred to CWE-785.
CWE-25	Path Traversal: '/../filedir'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/../" sequences that can resolve to a location that is outside of that directory.
CWE-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.
CWE-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.
CWE-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.
CWE-256	Plaintext Storage of a Password	The product stores a password in plaintext within resources such as memory or files.
CWE-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.
CWE-258	Empty Password in Configuration File	Using an empty string as a password is insecure.
CWE-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.
CWE-26	Path Traversal: '/dir/../filename'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "/dir/../filename" sequences that can resolve to a location that is outside of that directory.
CWE-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.
CWE-261	Weak Encoding for Password	Obscuring a password with a trivial encoding does not protect the password.
CWE-262	Not Using Password Aging	The product does not have a mechanism in place for managing password aging.
CWE-263	Password Aging with Long Expiration	The product supports password aging, but the expiration period is too long.
CWE-266	Incorrect Privilege Assignment	A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.
CWE-267	Privilege Defined With Unsafe Actions	A particular privilege, role, capability, or right can be used to perform unsafe actions that were not intended, even when it is assigned to the correct entity.
CWE-268	Privilege Chaining	Two distinct privileges, roles, capabilities, or rights can be combined in a way that allows an entity to perform unsafe actions that would not be allowed without that combination.
CWE-269	Improper Privilege Management	The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
CWE-27	Path Traversal: 'dir/../../filename'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize multiple internal "../" sequences that can resolve to a location that is outside of that directory.
CWE-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.
CWE-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.
CWE-272	Least Privilege Violation	The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.
CWE-273	Improper Check for Dropped Privileges	The product attempts to drop privileges but does not check or incorrectly checks to see if the drop succeeded.
CWE-274	Improper Handling of Insufficient Privileges	The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.
CWE-276	Incorrect Default Permissions	During installation, installed file permissions are set to allow anyone to modify those files.
CWE-277	Insecure Inherited Permissions	A product defines a set of insecure permissions that are inherited by objects that are created by the program.
CWE-278	Insecure Preserved Inherited Permissions	A product inherits a set of insecure permissions for an object, e.g. when copying from an archive file, without user awareness or involvement.
CWE-279	Incorrect Execution-Assigned Permissions	While it is executing, the product sets the permissions of an object in a way that violates the intended permissions that have been specified by the user.
CWE-28	Path Traversal: '..\filedir'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize "..\" sequences that can resolve to a location that is outside of that directory.
CWE-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.
CWE-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.
CWE-282	Improper Ownership Management	The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.
CWE-283	Unverified Ownership	The product does not properly verify that a critical resource is owned by the proper entity.
CWE-284	Improper Access Control	The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-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.
CWE-286	Incorrect User Management	The product does not properly manage a user within its environment.
CWE-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.
CWE-288	Authentication Bypass Using an Alternate Path or Channel	The product requires authentication, but the product has an alternate path or channel that does not require authentication.
CWE-289	Authentication Bypass by Alternate Name	The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.
CWE-29	Path Traversal: '\..\filename'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
CWE-290	Authentication Bypass by Spoofing	This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
CWE-291	Reliance on IP Address for Authentication	The product uses an IP address for authentication.
CWE-292	DEPRECATED: Trusting Self-reported DNS Name	This entry has been deprecated because it was a duplicate of CWE-350. All content has been transferred to CWE-350.
CWE-293	Using Referer Field for Authentication	The referer field in HTTP requests can be easily modified and, as such, is not a valid means of message integrity checking.
CWE-294	Authentication Bypass by Capture-replay	A capture-replay flaw exists when the design of the product makes it possible for a malicious user to sniff network traffic and bypass authentication by replaying it to the server in question to the same effect as the original message (or with minor changes).
CWE-295	Improper Certificate Validation	The product does not validate, or incorrectly validates, a certificate.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-30	Path Traversal: '\dir\..\filename'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\dir\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-304	Missing Critical Step in Authentication	The product implements an authentication technique, but it skips a step that weakens the technique.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-31	Path Traversal: 'dir\..\..\filename'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize 'dir\..\..\filename' (multiple internal backslash dot dot) sequences that can resolve to a location that is outside of that directory.
CWE-311	Missing Encryption of Sensitive Data	The product does not encrypt sensitive or critical information before storage or transmission.
CWE-312	Cleartext Storage of Sensitive Information	The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.
CWE-313	Cleartext Storage in a File or on Disk	The product stores sensitive information in cleartext in a file, or on disk.
CWE-314	Cleartext Storage in the Registry	The product stores sensitive information in cleartext in the registry.
CWE-315	Cleartext Storage of Sensitive Information in a Cookie	The product stores sensitive information in cleartext in a cookie.
CWE-316	Cleartext Storage of Sensitive Information in Memory	The product stores sensitive information in cleartext in memory.
CWE-317	Cleartext Storage of Sensitive Information in GUI	The product stores sensitive information in cleartext within the GUI.
CWE-318	Cleartext Storage of Sensitive Information in Executable	The product stores sensitive information in cleartext in an executable.
CWE-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.
CWE-32	Path Traversal: '...' (Triple Dot)	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '...' (triple dot) sequences that can resolve to a location that is outside of that directory.
CWE-321	Use of Hard-coded Cryptographic Key	The product uses a hard-coded, unchangeable cryptographic key.
CWE-322	Key Exchange without Entity Authentication	The product performs a key exchange with an actor without verifying the identity of that actor.
CWE-323	Reusing a Nonce, Key Pair in Encryption	Nonces should be used for the present occasion and only once.
CWE-324	Use of a Key Past its Expiration Date	The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key.
CWE-325	Missing Cryptographic Step	The product does not implement a required step in a cryptographic algorithm, resulting in weaker encryption than advertised by the algorithm.
CWE-326	Inadequate Encryption Strength	The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.
CWE-327	Use of a Broken or Risky Cryptographic Algorithm	The product uses a broken or risky cryptographic algorithm or protocol.
CWE-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).
CWE-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.
CWE-33	Path Traversal: '....' (Multiple Dot)	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....' (multiple dot) sequences that can resolve to a location that is outside of that directory.
CWE-330	Use of Insufficiently Random Values	The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-339	Small Seed Space in PRNG	A Pseudo-Random Number Generator (PRNG) uses a relatively small seed space, which makes it more susceptible to brute force attacks.
CWE-34	Path Traversal: '....//'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '....//' (doubled dot dot slash) sequences that can resolve to a location that is outside of that directory.
CWE-340	Generation of Predictable Numbers or Identifiers	The product uses a scheme that generates numbers or identifiers that are more predictable than required.
CWE-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.
CWE-342	Predictable Exact Value from Previous Values	An exact value or random number can be precisely predicted by observing previous values.
CWE-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.
CWE-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.
CWE-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.
CWE-346	Origin Validation Error	The product does not properly verify that the source of data or communication is valid.
CWE-347	Improper Verification of Cryptographic Signature	The product does not verify, or incorrectly verifies, the cryptographic signature for data.
CWE-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.
CWE-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.
CWE-35	Path Traversal: '.../...//'	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory.
CWE-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.
CWE-351	Insufficient Type Distinction	The product does not properly distinguish between different types of elements in a way that leads to insecure behavior.
CWE-352	Cross-Site Request Forgery (CSRF)	The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
CWE-353	Missing Support for Integrity Check	The product uses a transmission protocol that does not include a mechanism for verifying the integrity of the data during transmission, such as a checksum.
CWE-354	Improper Validation of Integrity Check Value	The product does not validate or incorrectly validates the integrity check values or "checksums" of a message. This may prevent it from detecting if the data has been modified or corrupted in transmission.
CWE-356	Product UI does not Warn User of Unsafe Actions	The product's user interface does not warn the user before undertaking an unsafe action on behalf of that user. This makes it easier for attackers to trick users into inflicting damage to their system.
CWE-357	Insufficient UI Warning of Dangerous Operations	The user interface provides a warning to a user regarding dangerous or sensitive operations, but the warning is not noticeable enough to warrant attention.
CWE-358	Improperly Implemented Security Check for Standard	The product does not implement or incorrectly implements one or more security-relevant checks as specified by the design of a standardized algorithm, protocol, or technique.
CWE-359	Exposure of Private Personal Information to an Unauthorized Actor	The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.
CWE-36	Absolute Path Traversal	The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as "/abs/path" that can resolve to a location that is outside of that directory.
CWE-360	Trust of System Event Data	Security based on event locations are insecure and can be spoofed.
CWE-362	Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')	The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
CWE-363	Race Condition Enabling Link Following	The product checks the status of a file or directory before accessing it, which produces a race condition in which the file can be replaced with a link before the access is performed, causing the product to access the wrong file.
CWE-364	Signal Handler Race Condition	The product uses a signal handler that introduces a race condition.
CWE-365	DEPRECATED: Race Condition in Switch	This entry has been deprecated. There are no documented cases in which a switch's control expression is evaluated more than once.
CWE-366	Race Condition within a Thread	If two threads of execution use a resource simultaneously, there exists the possibility that resources may be used while invalid, in turn making the state of execution undefined.
CWE-367	Time-of-check Time-of-use (TOCTOU) Race Condition	The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check.
CWE-368	Context Switching Race Condition	A product performs a series of non-atomic actions to switch between contexts that cross privilege or other security boundaries, but a race condition allows an attacker to modify or misrepresent the product's behavior during the switch.
CWE-369	Divide By Zero	The product divides a value by zero.
CWE-37	Path Traversal: '/absolute/pathname/here'	The product accepts input in the form of a slash absolute path ('/absolute/pathname/here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-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.
CWE-373	DEPRECATED: State Synchronization Error	This entry was deprecated because it overlapped the same concepts as race condition (CWE-362) and Improper Synchronization (CWE-662).
CWE-374	Passing Mutable Objects to an Untrusted Method	The product sends non-cloned mutable data as an argument to a method or function.
CWE-375	Returning a Mutable Object to an Untrusted Caller	Sending non-cloned mutable data as a return value may result in that data being altered or deleted by the calling function.
CWE-377	Insecure Temporary File	Creating and using insecure temporary files can leave application and system data vulnerable to attack.
CWE-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.
CWE-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.
CWE-38	Path Traversal: '\absolute\pathname\here'	The product accepts input in the form of a backslash absolute path ('\absolute\pathname\here') without appropriate validation, which can allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-382	J2EE Bad Practices: Use of System.exit()	A J2EE application uses System.exit(), which also shuts down its container.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-39	Path Traversal: 'C:dirname'	The product accepts input that contains a drive letter or Windows volume letter ('C:dirname') that potentially redirects access to an unintended location or arbitrary file.
CWE-390	Detection of Error Condition Without Action	The product detects a specific error, but takes no actions to handle the error.
CWE-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.
CWE-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.
CWE-393	Return of Wrong Status Code	A function or operation returns an incorrect return value or status code that does not indicate the true result of execution, causing the product to modify its behavior based on the incorrect result.
CWE-394	Unexpected Status Code or Return Value	The product does not properly check when a function or operation returns a value that is legitimate for the function, but is not expected by the product.
CWE-395	Use of NullPointerException Catch to Detect NULL Pointer Dereference	Catching NullPointerException should not be used as an alternative to programmatic checks to prevent dereferencing a null pointer.
CWE-396	Declaration of Catch for Generic Exception	Catching overly broad exceptions promotes complex error handling code that is more likely to contain security vulnerabilities.
CWE-397	Declaration of Throws for Generic Exception	The product throws or raises an overly broad exceptions that can hide important details and produce inappropriate responses to certain conditions.
CWE-40	Path Traversal: '\\UNC\share\name\' (Windows UNC Share)	The product accepts input that identifies a Windows UNC share ('\\UNC\share\name') that potentially redirects access to an unintended location or arbitrary file.
CWE-400	Uncontrolled Resource Consumption	The product does not properly control the allocation and maintenance of a limited resource.
CWE-401	Missing Release of Memory after Effective Lifetime	The product does not sufficiently track and release allocated memory after it has been used, making the memory unavailable for reallocation and reuse.
CWE-402	Transmission of Private Resources into a New Sphere ('Resource Leak')	The product makes resources available to untrusted parties when those resources are only intended to be accessed by the product.
CWE-403	Exposure of File Descriptor to Unintended Control Sphere ('File Descriptor Leak')	A process does not close sensitive file descriptors before invoking a child process, which allows the child to perform unauthorized I/O operations using those descriptors.
CWE-404	Improper Resource Shutdown or Release	The product does not release or incorrectly releases a resource before it is made available for re-use.
CWE-405	Asymmetric Resource Consumption (Amplification)	The product does not properly control situations in which an adversary can cause the product to consume or produce excessive resources without requiring the adversary to invest equivalent work or otherwise prove authorization, i.e., the adversary's influence is "asymmetric."
CWE-406	Insufficient Control of Network Message Volume (Network Amplification)	The product does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the product to transmit more traffic than should be allowed for that actor.
CWE-407	Inefficient Algorithmic Complexity	An algorithm in a product has an inefficient worst-case computational complexity that may be detrimental to system performance and can be triggered by an attacker, typically using crafted manipulations that ensure that the worst case is being reached.
CWE-408	Incorrect Behavior Order: Early Amplification	The product allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place.
CWE-409	Improper Handling of Highly Compressed Data (Data Amplification)	The product does not handle or incorrectly handles a compressed input with a very high compression ratio that produces a large output.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-414	Missing Lock Check	A product does not check to see if a lock is present before performing sensitive operations on a resource.
CWE-415	Double Free	The product calls free() twice on the same memory address.
CWE-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.
CWE-419	Unprotected Primary Channel	The product uses a primary channel for administration or restricted functionality, but it does not properly protect the channel.
CWE-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.
CWE-420	Unprotected Alternate Channel	The product protects a primary channel, but it does not use the same level of protection for an alternate channel.
CWE-421	Race Condition During Access to Alternate Channel	The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors.
CWE-422	Unprotected Windows Messaging Channel ('Shatter')	The product does not properly verify the source of a message in the Windows Messaging System while running at elevated privileges, creating an alternate channel through which an attacker can directly send a message to the product.
CWE-423	DEPRECATED: Proxied Trusted Channel	This entry has been deprecated because it was a duplicate of CWE-441. All content has been transferred to CWE-441.
CWE-424	Improper Protection of Alternate Path	The product does not sufficiently protect all possible paths that a user can take to access restricted functionality or resources.
CWE-425	Direct Request ('Forced Browsing')	The web application does not adequately enforce appropriate authorization on all restricted URLs, scripts, or files.
CWE-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.
CWE-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.
CWE-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.
CWE-43	Path Equivalence: 'filename....' (Multiple Trailing Dot)	The product accepts path input in the form of multiple trailing dot ('filedir....') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-430	Deployment of Wrong Handler	The wrong "handler" is assigned to process an object.
CWE-431	Missing Handler	A handler is not available or implemented.
CWE-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.
CWE-433	Unparsed Raw Web Content Delivery	The product stores raw content or supporting code under the web document root with an extension that is not specifically handled by the server.
CWE-434	Unrestricted Upload of File with Dangerous Type	The product allows the upload or transfer of dangerous file types that are automatically processed within its environment.
CWE-435	Improper Interaction Between Multiple Correctly-Behaving Entities	An interaction error occurs when two entities have correct behavior when running independently of each other, but when they are integrated as components in a larger system or process, they introduce incorrect behaviors that may cause resultant weaknesses.
CWE-436	Interpretation Conflict	Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state.
CWE-437	Incomplete Model of Endpoint Features	A product acts as an intermediary or monitor between two or more endpoints, but it does not have a complete model of an endpoint's features, behaviors, or state, potentially causing the product to perform incorrect actions based on this incomplete model.
CWE-439	Behavioral Change in New Version or Environment	A's behavior or functionality changes with a new version of A, or a new environment, which is not known (or manageable) by B.
CWE-44	Path Equivalence: 'file.name' (Internal Dot)	The product accepts path input in the form of internal dot ('file.ordir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-440	Expected Behavior Violation	A feature, API, or function does not perform according to its specification.
CWE-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.
CWE-443	DEPRECATED: HTTP response splitting	This weakness can be found at CWE-113.
CWE-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.
CWE-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.
CWE-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.
CWE-448	Obsolete Feature in UI	A UI function is obsolete and the product does not warn the user.
CWE-449	The UI Performs the Wrong Action	The UI performs the wrong action with respect to the user's request.
CWE-45	Path Equivalence: 'file...name' (Multiple Internal Dot)	The product accepts path input in the form of multiple internal dot ('file...dir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-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.
CWE-453	Insecure Default Variable Initialization	The product, by default, initializes an internal variable with an insecure or less secure value than is possible.
CWE-454	External Initialization of Trusted Variables or Data Stores	The product initializes critical internal variables or data stores using inputs that can be modified by untrusted actors.
CWE-455	Non-exit on Failed Initialization	The product does not exit or otherwise modify its operation when security-relevant errors occur during initialization, such as when a configuration file has a format error or a hardware security module (HSM) cannot be activated, which can cause the product to execute in a less secure fashion than intended by the administrator.
CWE-456	Missing Initialization of a Variable	The product does not initialize critical variables, which causes the execution environment to use unexpected values.
CWE-457	Use of Uninitialized Variable	The code uses a variable that has not been initialized, leading to unpredictable or unintended results.
CWE-458	DEPRECATED: Incorrect Initialization	This weakness has been deprecated because its name and description did not match. The description duplicated CWE-454, while the name suggested a more abstract initialization problem. Please refer to CWE-665 for the more abstract problem.
CWE-459	Incomplete Cleanup	The product does not properly "clean up" and remove temporary or supporting resources after they have been used.
CWE-46	Path Equivalence: 'filename ' (Trailing Space)	The product accepts path input in the form of trailing space ('filedir ') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-462	Duplicate Key in Associative List (Alist)	Duplicate keys in associative lists can lead to non-unique keys being mistaken for an error.
CWE-463	Deletion of Data Structure Sentinel	The accidental deletion of a data-structure sentinel can cause serious programming logic problems.
CWE-464	Addition of Data Structure Sentinel	The accidental addition of a data-structure sentinel can cause serious programming logic problems.
CWE-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.
CWE-467	Use of sizeof() on a Pointer Type	The code calls sizeof() on a pointer type, which can be an incorrect calculation if the programmer intended to determine the size of the data that is being pointed to.
CWE-468	Incorrect Pointer Scaling	In C and C++, one may often accidentally refer to the wrong memory due to the semantics of when math operations are implicitly scaled.
CWE-469	Use of Pointer Subtraction to Determine Size	The product subtracts one pointer from another in order to determine size, but this calculation can be incorrect if the pointers do not exist in the same memory chunk.
CWE-47	Path Equivalence: ' filename' (Leading Space)	The product accepts path input in the form of leading space (' filedir') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-471	Modification of Assumed-Immutable Data (MAID)	The product does not properly protect an assumed-immutable element from being modified by an attacker.
CWE-472	External Control of Assumed-Immutable Web Parameter	The web application does not sufficiently verify inputs that are assumed to be immutable but are actually externally controllable, such as hidden form fields.
CWE-473	PHP External Variable Modification	A PHP application does not properly protect against the modification of variables from external sources, such as query parameters or cookies. This can expose the application to numerous weaknesses that would not exist otherwise.
CWE-474	Use of Function with Inconsistent Implementations	The code uses a function that has inconsistent implementations across operating systems and versions.
CWE-475	Undefined Behavior for Input to API	The behavior of this function is undefined unless its control parameter is set to a specific value.
CWE-476	NULL Pointer Dereference	The product dereferences a pointer that it expects to be valid but is NULL.
CWE-477	Use of Obsolete Function	The code uses deprecated or obsolete functions, which suggests that the code has not been actively reviewed or maintained.
CWE-478	Missing Default Case in Multiple Condition Expression	The code does not have a default case in an expression with multiple conditions, such as a switch statement.
CWE-479	Signal Handler Use of a Non-reentrant Function	The product defines a signal handler that calls a non-reentrant function.
CWE-48	Path Equivalence: 'file name' (Internal Whitespace)	The product accepts path input in the form of internal space ('file(SPACE)name') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-480	Use of Incorrect Operator	The product accidentally uses the wrong operator, which changes the logic in security-relevant ways.
CWE-481	Assigning instead of Comparing	The code uses an operator for assignment when the intention was to perform a comparison.
CWE-482	Comparing instead of Assigning	The code uses an operator for comparison when the intention was to perform an assignment.
CWE-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.
CWE-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.
CWE-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.
CWE-487	Reliance on Package-level Scope	Java packages are not inherently closed; therefore, relying on them for code security is not a good practice.
CWE-488	Exposure of Data Element to Wrong Session	The product does not sufficiently enforce boundaries between the states of different sessions, causing data to be provided to, or used by, the wrong session.
CWE-489	Active Debug Code	The product is released with debugging code still enabled or active.
CWE-49	Path Equivalence: 'filename/' (Trailing Slash)	The product accepts path input in the form of trailing slash ('filedir/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-497	Exposure of Sensitive System Information to an Unauthorized Control Sphere	The product does not properly prevent sensitive system-level information from being accessed by unauthorized actors who do not have the same level of access to the underlying system as the product does.
CWE-498	Cloneable Class Containing Sensitive Information	The code contains a class with sensitive data, but the class is cloneable. The data can then be accessed by cloning the class.
CWE-499	Serializable Class Containing Sensitive Data	The code contains a class with sensitive data, but the class does not explicitly deny serialization. The data can be accessed by serializing the class through another class.
CWE-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.
CWE-50	Path Equivalence: '//multiple/leading/slash'	The product accepts path input in the form of multiple leading slash ('//multiple/leading/slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-501	Trust Boundary Violation	The product mixes trusted and untrusted data in the same data structure or structured message.
CWE-502	Deserialization of Untrusted Data	The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.
CWE-506	Embedded Malicious Code	The product contains code that appears to be malicious in nature.
CWE-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.
CWE-508	Non-Replicating Malicious Code	Non-replicating malicious code only resides on the target system or product that is attacked; it does not attempt to spread to other systems.
CWE-509	Replicating Malicious Code (Virus or Worm)	Replicating malicious code, including viruses and worms, will attempt to attack other systems once it has successfully compromised the target system or the product.
CWE-51	Path Equivalence: '/multiple//internal/slash'	The product accepts path input in the form of multiple internal slash ('/multiple//internal/slash/') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-510	Trapdoor	A trapdoor is a hidden piece of code that responds to a special input, allowing its user access to resources without passing through the normal security enforcement mechanism.
CWE-511	Logic/Time Bomb	The product contains code that is designed to disrupt the legitimate operation of the product (or its environment) when a certain time passes, or when a certain logical condition is met.
CWE-512	Spyware	The product collects personally identifiable information about a human user or the user's activities, but the product accesses this information using other resources besides itself, and it does not require that user's explicit approval or direct input into the product.
CWE-514	Covert Channel	A covert channel is a path that can be used to transfer information in a way not intended by the system's designers.
CWE-515	Covert Storage Channel	A covert storage channel transfers information through the setting of bits by one program and the reading of those bits by another. What distinguishes this case from that of ordinary operation is that the bits are used to convey encoded information.
CWE-516	DEPRECATED: Covert Timing Channel	This weakness can be found at CWE-385.
CWE-52	Path Equivalence: '/multiple/trailing/slash//'	The product accepts path input in the form of multiple trailing slash ('/multiple/trailing/slash//') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-526	Cleartext Storage of Sensitive Information in an Environment Variable	The product uses an environment variable to store unencrypted sensitive information.
CWE-527	Exposure of Version-Control Repository to an Unauthorized Control Sphere	The product stores a CVS, git, or other repository in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.
CWE-528	Exposure of Core Dump File to an Unauthorized Control Sphere	The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.
CWE-529	Exposure of Access Control List Files to an Unauthorized Control Sphere	The product stores access control list files in a directory or other container that is accessible to actors outside of the intended control sphere.
CWE-53	Path Equivalence: '\multiple\\internal\backslash'	The product accepts path input in the form of multiple internal backslash ('\multiple\trailing\\slash') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-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.
CWE-532	Insertion of Sensitive Information into Log File	The product writes sensitive information to a log file.
CWE-533	DEPRECATED: Information Exposure Through Server Log Files	This entry has been deprecated because its abstraction was too low-level. See CWE-532.
CWE-534	DEPRECATED: Information Exposure Through Debug Log Files	This entry has been deprecated because its abstraction was too low-level. See CWE-532.
CWE-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.
CWE-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.
CWE-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.
CWE-538	Insertion of Sensitive Information into Externally-Accessible File or Directory	The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.
CWE-539	Use of Persistent Cookies Containing Sensitive Information	The web application uses persistent cookies, but the cookies contain sensitive information.
CWE-54	Path Equivalence: 'filedir\' (Trailing Backslash)	The product accepts path input in the form of trailing backslash ('filedir\') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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.
CWE-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.
CWE-542	DEPRECATED: Information Exposure Through Cleanup Log Files	This entry has been deprecated because its abstraction was too low-level. See CWE-532.
CWE-543	Use of Singleton Pattern Without Synchronization in a Multithreaded Context	The product uses the singleton pattern when creating a resource within a multithreaded environment.
CWE-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.
CWE-545	DEPRECATED: Use of Dynamic Class Loading	This weakness has been deprecated because it partially overlaps CWE-470, it describes legitimate programmer behavior, and other portions will need to be integrated into other entries.
CWE-546	Suspicious Comment	The code contains comments that suggest the presence of bugs, incomplete functionality, or weaknesses.
CWE-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.
CWE-548	Exposure of Information Through Directory Listing	The product inappropriately exposes a directory listing with an index of all the resources located inside of the directory.
CWE-549	Missing Password Field Masking	The product does not mask passwords during entry, increasing the potential for attackers to observe and capture passwords.
CWE-55	Path Equivalence: '/./' (Single Dot Directory)	The product accepts path input in the form of single dot directory exploit ('/./') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-550	Server-generated Error Message Containing Sensitive Information	Certain conditions, such as network failure, will cause a server error message to be displayed.
CWE-551	Incorrect Behavior Order: Authorization Before Parsing and Canonicalization	If a web server does not fully parse requested URLs before it examines them for authorization, it may be possible for an attacker to bypass authorization protection.
CWE-552	Files or Directories Accessible to External Parties	The product makes files or directories accessible to unauthorized actors, even though they should not be.
CWE-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.
CWE-554	ASP.NET Misconfiguration: Not Using Input Validation Framework	The ASP.NET application does not use an input validation framework.
CWE-555	J2EE Misconfiguration: Plaintext Password in Configuration File	The J2EE application stores a plaintext password in a configuration file.
CWE-556	ASP.NET Misconfiguration: Use of Identity Impersonation	Configuring an ASP.NET application to run with impersonated credentials may give the application unnecessary privileges.
CWE-558	Use of getlogin() in Multithreaded Application	The product uses the getlogin() function in a multithreaded context, potentially causing it to return incorrect values.
CWE-56	Path Equivalence: 'filedir*' (Wildcard)	The product accepts path input in the form of asterisk wildcard ('filedir*') without appropriate validation, which can lead to ambiguous path resolution and allow an attacker to traverse the file system to unintended locations or access arbitrary files.
CWE-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().
CWE-561	Dead Code	The product contains dead code, which can never be executed.
CWE-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.
CWE-563	Assignment to Variable without Use	The variable's value is assigned but never used, making it a dead store.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-568	finalize() Method Without super.finalize()	The product contains a finalize() method that does not call super.finalize().
CWE-57	Path Equivalence: 'fakedir/../realdir/filename'	The product contains protection mechanisms to restrict access to 'realdir/filename', but it constructs pathnames using external input in the form of 'fakedir/../realdir/filename' that are not handled by those mechanisms. This allows attackers to perform unauthorized actions against the targeted file.
CWE-570	Expression is Always False	The product contains an expression that will always evaluate to false.
CWE-571	Expression is Always True	The product contains an expression that will always evaluate to true.
CWE-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.
CWE-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.
CWE-574	EJB Bad Practices: Use of Synchronization Primitives	The product violates the Enterprise JavaBeans (EJB) specification by using thread synchronization primitives.
CWE-575	EJB Bad Practices: Use of AWT Swing	The product violates the Enterprise JavaBeans (EJB) specification by using AWT/Swing.
CWE-576	EJB Bad Practices: Use of Java I/O	The product violates the Enterprise JavaBeans (EJB) specification by using the java.io package.
CWE-577	EJB Bad Practices: Use of Sockets	The product violates the Enterprise JavaBeans (EJB) specification by using sockets.
CWE-578	EJB Bad Practices: Use of Class Loader	The product violates the Enterprise JavaBeans (EJB) specification by using the class loader.
CWE-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.
CWE-58	Path Equivalence: Windows 8.3 Filename	The product contains a protection mechanism that restricts access to a long filename on a Windows operating system, but it does not properly restrict access to the equivalent short "8.3" filename.
CWE-580	clone() Method Without super.clone()	The product contains a clone() method that does not call super.clone() to obtain the new object.
CWE-581	Object Model Violation: Just One of Equals and Hashcode Defined	The product does not maintain equal hashcodes for equal objects.
CWE-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.
CWE-583	finalize() Method Declared Public	The product violates secure coding principles for mobile code by declaring a finalize() method public.
CWE-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.
CWE-585	Empty Synchronized Block	The product contains an empty synchronized block.
CWE-586	Explicit Call to Finalize()	The product makes an explicit call to the finalize() method from outside the finalizer.
CWE-587	Assignment of a Fixed Address to a Pointer	The product sets a pointer to a specific address other than NULL or 0.
CWE-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.
CWE-589	Call to Non-ubiquitous API	The product uses an API function that does not exist on all versions of the target platform. This could cause portability problems or inconsistencies that allow denial of service or other consequences.
CWE-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.
CWE-590	Free of Memory not on the Heap	The product calls free() on a pointer to memory that was not allocated using associated heap allocation functions such as malloc(), calloc(), or realloc().
CWE-591	Sensitive Data Storage in Improperly Locked Memory	The product stores sensitive data in memory that is not locked, or that has been incorrectly locked, which might cause the memory to be written to swap files on disk by the virtual memory manager. This can make the data more accessible to external actors.
CWE-592	DEPRECATED: Authentication Bypass Issues	This weakness has been deprecated because it covered redundant concepts already described in CWE-287.
CWE-593	Authentication Bypass: OpenSSL CTX Object Modified after SSL Objects are Created	The product modifies the SSL context after connection creation has begun.
CWE-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.
CWE-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.
CWE-596	DEPRECATED: Incorrect Semantic Object Comparison	This weakness has been deprecated. It was poorly described and difficult to distinguish from other entries. It was also inappropriate to assign a separate ID solely because of domain-specific considerations. Its closest equivalent is CWE-1023.
CWE-597	Use of Wrong Operator in String Comparison	The product uses the wrong operator when comparing a string, such as using "==" when the .equals() method should be used instead.
CWE-598	Use of 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.
CWE-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.
CWE-6	J2EE Misconfiguration: Insufficient Session-ID Length	The J2EE application is configured to use an insufficient session ID length.
CWE-600	Uncaught Exception in Servlet	The Servlet does not catch all exceptions, which may reveal sensitive debugging information.
CWE-601	URL Redirection to Untrusted Site ('Open Redirect')	The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
CWE-602	Client-Side Enforcement of Server-Side Security	The product is composed of a server that relies on the client to implement a mechanism that is intended to protect the server.
CWE-603	Use of Client-Side Authentication	A client/server product performs authentication within client code but not in server code, allowing server-side authentication to be bypassed via a modified client that omits the authentication check.
CWE-605	Multiple Binds to the Same Port	When multiple sockets are allowed to bind to the same port, other services on that port may be stolen or spoofed.
CWE-606	Unchecked Input for Loop Condition	The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.
CWE-607	Public Static Final Field References Mutable Object	A public or protected static final field references a mutable object, which allows the object to be changed by malicious code, or accidentally from another package.
CWE-608	Struts: Non-private Field in ActionForm Class	An ActionForm class contains a field that has not been declared private, which can be accessed without using a setter or getter.
CWE-609	Double-Checked Locking	The product uses double-checked locking to access a resource without the overhead of explicit synchronization, but the locking is insufficient.
CWE-61	UNIX Symbolic Link (Symlink) Following	The product, when opening a file or directory, does not sufficiently account for when the file is a symbolic link that resolves to a target outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-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.
CWE-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.
CWE-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.
CWE-613	Insufficient Session Expiration	According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."
CWE-614	Sensitive Cookie in HTTPS Session Without 'Secure' Attribute	The Secure attribute for sensitive cookies in HTTPS sessions is not set.
CWE-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.
CWE-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.
CWE-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.
CWE-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).
CWE-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."
CWE-62	UNIX Hard Link	The product, when opening a file or directory, does not sufficiently account for when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-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.
CWE-621	Variable Extraction Error	The product uses external input to determine the names of variables into which information is extracted, without verifying that the names of the specified variables are valid. This could cause the program to overwrite unintended variables.
CWE-622	Improper Validation of Function Hook Arguments	The product adds hooks to user-accessible API functions, but it does not properly validate the arguments. This could lead to resultant vulnerabilities.
CWE-623	Unsafe ActiveX Control Marked Safe For Scripting	An ActiveX control is intended for restricted use, but it has been marked as safe-for-scripting.
CWE-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.
CWE-625	Permissive Regular Expression	The product uses a regular expression that does not sufficiently restrict the set of allowed values.
CWE-626	Null Byte Interaction Error (Poison Null Byte)	The product does not properly handle null bytes or NUL characters when passing data between different representations or components.
CWE-627	Dynamic Variable Evaluation	In a language where the user can influence the name of a variable at runtime, if the variable names are not controlled, an attacker can read or write to arbitrary variables, or access arbitrary functions.
CWE-628	Function Call with Incorrectly Specified Arguments	The product calls a function, procedure, or routine with arguments that are not correctly specified, leading to always-incorrect behavior and resultant weaknesses.
CWE-636	Not Failing Securely ('Failing Open')	When the product encounters an error condition or failure, its design requires it to fall back to a state that is less secure than other options that are available, such as selecting the weakest encryption algorithm or using the most permissive access control restrictions.
CWE-637	Unnecessary Complexity in Protection Mechanism (Not Using 'Economy of Mechanism')	The product uses a more complex mechanism than necessary, which could lead to resultant weaknesses when the mechanism is not correctly understood, modeled, configured, implemented, or used.
CWE-638	Not Using Complete Mediation	The product does not perform access checks on a resource every time the resource is accessed by an entity, which can create resultant weaknesses if that entity's rights or privileges change over time.
CWE-639	Authorization Bypass Through User-Controlled Key	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
CWE-64	Windows Shortcut Following (.LNK)	The product, when opening a file or directory, does not sufficiently handle when the file is a Windows shortcut (.LNK) whose target is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-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.
CWE-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.
CWE-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.
CWE-643	Improper Neutralization of Data within XPath Expressions ('XPath Injection')	The product uses external input to dynamically construct an XPath expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query.
CWE-644	Improper Neutralization of HTTP Headers for Scripting Syntax	The product does not neutralize or incorrectly neutralizes web scripting syntax in HTTP headers that can be used by web browser components that can process raw headers, such as Flash.
CWE-645	Overly Restrictive Account Lockout Mechanism	The product contains an account lockout protection mechanism, but the mechanism is too restrictive and can be triggered too easily, which allows attackers to deny service to legitimate users by causing their accounts to be locked out.
CWE-646	Reliance on File Name or Extension of Externally-Supplied File	The product allows a file to be uploaded, but it relies on the file name or extension of the file to determine the appropriate behaviors. This could be used by attackers to cause the file to be misclassified and processed in a dangerous fashion.
CWE-647	Use of Non-Canonical URL Paths for Authorization Decisions	The product defines policy namespaces and makes authorization decisions based on the assumption that a URL is canonical. This can allow a non-canonical URL to bypass the authorization.
CWE-648	Incorrect Use of Privileged APIs	The product does not conform to the API requirements for a function call that requires extra privileges. This could allow attackers to gain privileges by causing the function to be called incorrectly.
CWE-649	Reliance on Obfuscation or Encryption of Security-Relevant Inputs without Integrity Checking	The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.
CWE-65	Windows Hard Link	The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.
CWE-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.
CWE-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).
CWE-652	Improper Neutralization of Data within XQuery Expressions ('XQuery Injection')	The product uses external input to dynamically construct an XQuery expression used to retrieve data from an XML database, but it does not neutralize or incorrectly neutralizes that input. This allows an attacker to control the structure of the query.
CWE-653	Improper Isolation or Compartmentalization	The product does not properly compartmentalize or isolate functionality, processes, or resources that require different privilege levels, rights, or permissions.
CWE-654	Reliance on a Single Factor in a Security Decision	A protection mechanism relies exclusively, or to a large extent, on the evaluation of a single condition or the integrity of a single object or entity in order to make a decision about granting access to restricted resources or functionality.
CWE-655	Insufficient Psychological Acceptability	The product has a protection mechanism that is too difficult or inconvenient to use, encouraging non-malicious users to disable or bypass the mechanism, whether by accident or on purpose.
CWE-656	Reliance on Security Through Obscurity	The product uses a protection mechanism whose strength depends heavily on its obscurity, such that knowledge of its algorithms or key data is sufficient to defeat the mechanism.
CWE-657	Violation of Secure Design Principles	The product violates well-established principles for secure design.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-667	Improper Locking	The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
CWE-668	Exposure of Resource to Wrong Sphere	The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.
CWE-669	Incorrect Resource Transfer Between Spheres	The product does not properly transfer a resource/behavior to another sphere, or improperly imports a resource/behavior from another sphere, in a manner that provides unintended control over that resource.
CWE-67	Improper Handling of Windows Device Names	The product constructs pathnames from user input, but it does not handle or incorrectly handles a pathname containing a Windows device name such as AUX or CON. This typically leads to denial of service or an information exposure when the application attempts to process the pathname as a regular file.
CWE-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.
CWE-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.
CWE-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.
CWE-673	External Influence of Sphere Definition	The product does not prevent the definition of control spheres from external actors.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-684	Incorrect Provision of Specified Functionality	The code does not function according to its published specifications, potentially leading to incorrect usage.
CWE-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.
CWE-686	Function Call With Incorrect Argument Type	The product calls a function, procedure, or routine, but the caller specifies an argument that is the wrong data type, which may lead to resultant weaknesses.
CWE-687	Function Call With Incorrectly Specified Argument Value	The product calls a function, procedure, or routine, but the caller specifies an argument that contains the wrong value, which may lead to resultant weaknesses.
CWE-688	Function Call With Incorrect Variable or Reference as Argument	The product calls a function, procedure, or routine, but the caller specifies the wrong variable or reference as one of the arguments, which may lead to undefined behavior and resultant weaknesses.
CWE-689	Permission Race Condition During Resource Copy	The product, while copying or cloning a resource, does not set the resource's permissions or access control until the copy is complete, leaving the resource exposed to other spheres while the copy is taking place.
CWE-69	Improper Handling of Windows ::DATA Alternate Data Stream	The product does not properly prevent access to, or detect usage of, alternate data streams (ADS).
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-697	Incorrect Comparison	The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses.
CWE-698	Execution After Redirect (EAR)	The web application sends a redirect to another location, but instead of exiting, it executes additional code.
CWE-7	J2EE Misconfiguration: Missing Custom Error Page	The default error page of a web application should not display sensitive information about the product.
CWE-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.
CWE-704	Incorrect Type Conversion or Cast	The product does not correctly convert an object, resource, or structure from one type to a different type.
CWE-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.
CWE-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.
CWE-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.
CWE-708	Incorrect Ownership Assignment	The product assigns an owner to a resource, but the owner is outside of the intended control sphere.
CWE-71	DEPRECATED: Apple '.DS_Store'	This entry has been deprecated as it represents a specific observed example of a UNIX Hard Link weakness type rather than its own individual weakness type. Please refer to CWE-62.
CWE-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.
CWE-72	Improper Handling of Apple HFS+ Alternate Data Stream Path	The product does not properly handle special paths that may identify the data or resource fork of a file on the HFS+ file system.
CWE-73	External Control of File Name or Path	The product allows user input to control or influence paths or file names that are used in filesystem operations.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-755	Improper Handling of Exceptional Conditions	The product does not handle or incorrectly handles an exceptional condition.
CWE-756	Missing Custom Error Page	The product does not return custom error pages to the user, possibly exposing sensitive information.
CWE-757	Selection of Less-Secure Algorithm During Negotiation ('Algorithm Downgrade')	A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.
CWE-758	Reliance on Undefined, Unspecified, or Implementation-Defined Behavior	The product uses an API function, data structure, or other entity in a way that relies on properties that are not always guaranteed to hold for that entity.
CWE-759	Use of a One-Way Hash without a Salt	The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of the input.
CWE-76	Improper Neutralization of Equivalent Special Elements	The product correctly neutralizes certain special elements, but it improperly neutralizes equivalent special elements.
CWE-760	Use of a One-Way Hash with a Predictable Salt	The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product uses a predictable salt as part of the input.
CWE-761	Free of Pointer not at Start of Buffer	The product calls free() on a pointer to a memory resource that was allocated on the heap, but the pointer is not at the start of the buffer.
CWE-762	Mismatched Memory Management Routines	The product attempts to return a memory resource to the system, but it calls a release function that is not compatible with the function that was originally used to allocate that resource.
CWE-763	Release of Invalid Pointer or Reference	The product attempts to return a memory resource to the system, but it calls the wrong release function or calls the appropriate release function incorrectly.
CWE-764	Multiple Locks of a Critical Resource	The product locks a critical resource more times than intended, leading to an unexpected state in the system.
CWE-765	Multiple Unlocks of a Critical Resource	The product unlocks a critical resource more times than intended, leading to an unexpected state in the system.
CWE-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.
CWE-767	Access to Critical Private Variable via Public Method	The product defines a public method that reads or modifies a private variable.
CWE-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.
CWE-769	DEPRECATED: Uncontrolled File Descriptor Consumption	This entry has been deprecated because it was a duplicate of CWE-774. All content has been transferred to CWE-774.
CWE-77	Improper Neutralization of Special Elements used in a Command ('Command Injection')	The product constructs all or part of a command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended command when it is sent to a downstream component.
CWE-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 intended restrictions on the size or number of resources that can be allocated.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-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.
CWE-78	Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')	The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.
CWE-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.
CWE-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.
CWE-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.
CWE-783	Operator Precedence Logic Error	The product uses an expression in which operator precedence causes incorrect logic to be used.
CWE-784	Reliance on Cookies without Validation and Integrity Checking in a Security Decision	The product uses a protection mechanism that relies on the existence or values of a cookie, but it does not properly ensure that the cookie is valid for the associated user.
CWE-785	Use of Path Manipulation Function without Maximum-sized Buffer	The product invokes a function for normalizing paths or file names, but it provides an output buffer that is smaller than the maximum possible size, such as PATH_MAX.
CWE-786	Access of Memory Location Before Start of Buffer	The product reads or writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.
CWE-787	Out-of-bounds Write	The product writes data past the end, or before the beginning, of the intended buffer.
CWE-788	Access of Memory Location After End of Buffer	The product reads or writes to a buffer using an index or pointer that references a memory location after the end of the buffer.
CWE-789	Memory Allocation with Excessive Size Value	The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated.
CWE-79	Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')	The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
CWE-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.
CWE-791	Incomplete Filtering of Special Elements	The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.
CWE-792	Incomplete Filtering of One or More Instances of Special Elements	The product receives data from an upstream component, but does not completely filter one or more instances of special elements before sending it to a downstream component.
CWE-793	Only Filtering One Instance of a Special Element	The product receives data from an upstream component, but only filters a single instance of a special element before sending it to a downstream component.
CWE-794	Incomplete Filtering of Multiple Instances of Special Elements	The product receives data from an upstream component, but does not filter all instances of a special element before sending it to a downstream component.
CWE-795	Only Filtering Special Elements at a Specified Location	The product receives data from an upstream component, but only accounts for special elements at a specified location, thereby missing remaining special elements that may exist before sending it to a downstream component.
CWE-796	Only Filtering Special Elements Relative to a Marker	The product receives data from an upstream component, but only accounts for special elements positioned relative to a marker (e.g. "at the beginning/end of a string; the second argument"), thereby missing remaining special elements that may exist before sending it to a downstream component.
CWE-797	Only Filtering Special Elements at an Absolute Position	The product receives data from an upstream component, but only accounts for special elements at an absolute position (e.g. "byte number 10"), thereby missing remaining special elements that may exist before sending it to a downstream component.
CWE-798	Use of Hard-coded Credentials	The product contains hard-coded credentials, such as a password or cryptographic key.
CWE-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.
CWE-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.
CWE-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.
CWE-804	Guessable CAPTCHA	The product uses a CAPTCHA challenge, but the challenge can be guessed or automatically recognized by a non-human actor.
CWE-805	Buffer Access with Incorrect Length Value	The product uses a sequential operation to read or write a buffer, but it uses an incorrect length value that causes it to access memory that is outside of the bounds of the buffer.
CWE-806	Buffer Access Using Size of Source Buffer	The product uses the size of a source buffer when reading from or writing to a destination buffer, which may cause it to access memory that is outside of the bounds of the buffer.
CWE-807	Reliance on Untrusted Inputs in a Security Decision	The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism.
CWE-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.
CWE-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.
CWE-820	Missing Synchronization	The product utilizes a shared resource in a concurrent manner but does not attempt to synchronize access to the resource.
CWE-821	Incorrect Synchronization	The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.
CWE-822	Untrusted Pointer Dereference	The product obtains a value from an untrusted source, converts this value to a pointer, and dereferences the resulting pointer.
CWE-823	Use of Out-of-range Pointer Offset	The product performs pointer arithmetic on a valid pointer, but it uses an offset that can point outside of the intended range of valid memory locations for the resulting pointer.
CWE-824	Access of Uninitialized Pointer	The product accesses or uses a pointer that has not been initialized.
CWE-825	Expired Pointer Dereference	The product dereferences a pointer that contains a location for memory that was previously valid, but is no longer valid.
CWE-826	Premature Release of Resource During Expected Lifetime	The product releases a resource that is still intended to be used by itself or another actor.
CWE-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.
CWE-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.
CWE-829	Inclusion of Functionality from Untrusted Control Sphere	The product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere.
CWE-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.
CWE-830	Inclusion of Web Functionality from an Untrusted Source	The product includes web functionality (such as a web widget) from another domain, which causes it to operate within the domain of the product, potentially granting total access and control of the product to the untrusted source.
CWE-831	Signal Handler Function Associated with Multiple Signals	The product defines a function that is used as a handler for more than one signal.
CWE-832	Unlock of a Resource that is not Locked	The product attempts to unlock a resource that is not locked.
CWE-833	Deadlock	The product contains multiple threads or executable segments that are waiting for each other to release a necessary lock, resulting in deadlock.
CWE-834	Excessive Iteration	The product performs an iteration or loop without sufficiently limiting the number of times that the loop is executed.
CWE-835	Loop with Unreachable Exit Condition ('Infinite Loop')	The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.
CWE-836	Use of Password Hash Instead of Password for Authentication	The product records password hashes in a data store, receives a hash of a password from a client, and compares the supplied hash to the hash obtained from the data store.
CWE-837	Improper Enforcement of a Single, Unique Action	The product requires that an actor should only be able to perform an action once, or to have only one unique action, but the product does not enforce or improperly enforces this restriction.
CWE-838	Inappropriate Encoding for Output Context	The product uses or specifies an encoding when generating output to a downstream component, but the specified encoding is not the same as the encoding that is expected by the downstream component.
CWE-839	Numeric Range Comparison Without Minimum Check	The product checks a value to ensure that it is less than or equal to a maximum, but it does not also verify that the value is greater than or equal to the minimum.
CWE-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.
CWE-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.
CWE-842	Placement of User into Incorrect Group	The product or the administrator places a user into an incorrect group.
CWE-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.
CWE-85	Doubled Character XSS Manipulations	The web application does not filter user-controlled input for executable script disguised using doubling of the involved characters.
CWE-86	Improper Neutralization of Invalid Characters in Identifiers in Web Pages	The product does not neutralize or incorrectly neutralizes invalid characters or byte sequences in the middle of tag names, URI schemes, and other identifiers.
CWE-862	Missing Authorization	The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
CWE-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.
CWE-87	Improper Neutralization of Alternate XSS Syntax	The product does not neutralize or incorrectly neutralizes user-controlled input for alternate script syntax.
CWE-88	Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')	The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
CWE-89	Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')	The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
CWE-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.
CWE-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.
CWE-908	Use of Uninitialized Resource	The product uses or accesses a resource that has not been initialized.
CWE-909	Missing Initialization of Resource	The product does not initialize a critical resource.
CWE-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.
CWE-910	Use of Expired File Descriptor	The product uses or accesses a file descriptor after it has been closed.
CWE-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.
CWE-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.
CWE-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.
CWE-914	Improper Control of Dynamically-Identified Variables	The product does not properly restrict reading from or writing to dynamically-identified variables.
CWE-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.
CWE-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.
CWE-917	Improper Neutralization of Special Elements used in an Expression Language Statement ('Expression Language Injection')	The product constructs all or part of an expression language (EL) statement in a framework such as a Java Server Page (JSP) using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended EL statement before it is executed.
CWE-918	Server-Side Request Forgery (SSRF)	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
CWE-92	DEPRECATED: Improper Sanitization of Custom Special Characters	This entry has been deprecated. It originally came from PLOVER, which sometimes defined "other" and "miscellaneous" categories in order to satisfy exhaustiveness requirements for taxonomies. Within the context of CWE, the use of a more abstract entry is preferred in mapping situations. CWE-75 is a more appropriate mapping.
CWE-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.
CWE-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.
CWE-922	Insecure Storage of Sensitive Information	The product stores sensitive information without properly limiting read or write access by unauthorized actors.
CWE-923	Improper Restriction of Communication Channel to Intended Endpoints	The product establishes a communication channel to (or from) an endpoint for privileged or protected operations, but it does not properly ensure that it is communicating with the correct endpoint.
CWE-924	Improper Enforcement of Message Integrity During Transmission in a Communication Channel	The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission.
CWE-925	Improper Verification of Intent by Broadcast Receiver	The Android application uses a Broadcast Receiver that receives an Intent but does not properly verify that the Intent came from an authorized source.
CWE-926	Improper Export of Android Application Components	The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains.
CWE-927	Use of Implicit Intent for Sensitive Communication	The Android application uses an implicit intent for transmitting sensitive data to other applications.
CWE-93	Improper Neutralization of CRLF Sequences ('CRLF Injection')	The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
CWE-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.
CWE-94	Improper Control of Generation of Code ('Code Injection')	The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
CWE-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.
CWE-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.
CWE-942	Permissive Cross-domain Security Policy with Untrusted Domains	The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate.
CWE-943	Improper Neutralization of Special Elements in Data Query Logic	The product generates a query intended to access or manipulate data in a data store such as a database, but it does not neutralize or incorrectly neutralizes special elements that can modify the intended logic of the query.
CWE-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").
CWE-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.
CWE-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.
CWE-98	Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')	The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions.
CWE-99	Improper Control of Resource Identifiers ('Resource Injection')	The product receives input from an upstream component, but it does not restrict or incorrectly restricts the input before it is used as an identifier for a resource that may be outside the intended sphere of control.
CWE-1	DEPRECATED: Location	This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-10	DEPRECATED: ASP.NET Environment Issues	This category has been deprecated. It added unnecessary depth and complexity to its associated views.
CWE-100	DEPRECATED: Technology-Specific Input Validation Problems	This category has been deprecated. It was originally intended as a "catch-all" for input validation problems in technologies that did not have their own CWE, but introduces unnecessary depth to the hierarchy.
CWE-1001	SFP Secondary Cluster: Use of an Improper API	This category identifies Software Fault Patterns (SFPs) within the Use of an Improper API cluster (SFP3).
CWE-1002	SFP Secondary Cluster: Unexpected Entry Points	This category identifies Software Fault Patterns (SFPs) within the Unexpected Entry Points cluster.
CWE-1005	7PK - Input Validation and Representation	This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that exist when an application does not properly validate or represent input. According to the authors of the Seven Pernicious Kingdoms, "Input validation and representation problems are caused by metacharacters, alternate encodings and numeric representations. Security problems result from trusting input."
CWE-1006	Bad Coding Practices	Weaknesses in this category are related to coding practices that are deemed unsafe and increase the chances that an exploitable vulnerability will be present in the application. These weaknesses do not directly introduce a vulnerability, but indicate that the product has not been carefully developed or maintained. If a program is complex, difficult to maintain, not portable, or shows evidence of neglect, then there is a higher likelihood that weaknesses are buried in the code.
CWE-1009	Audit	Weaknesses in this category are related to the design and architecture of audit-based components of the system. Frequently these deal with logging user activities in order to identify attackers and modifications to the system. The weaknesses in this category could lead to a degradation of the quality of the audit capability if they are not addressed when designing or implementing a secure architecture.
CWE-101	DEPRECATED: Struts Validation Problems	This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-1010	Authenticate Actors	Weaknesses in this category are related to the design and architecture of authentication components of the system. Frequently these deal with verifying the entity is indeed who it claims to be. The weaknesses in this category could lead to a degradation of the quality of authentication if they are not addressed when designing or implementing a secure architecture.
CWE-1011	Authorize Actors	Weaknesses in this category are related to the design and architecture of a system's authorization components. Frequently these deal with enforcing that agents have the required permissions before performing certain operations, such as modifying data. The weaknesses in this category could lead to a degradation of quality of the authorization capability if they are not addressed when designing or implementing a secure architecture.
CWE-1012	Cross Cutting	Weaknesses in this category are related to the design and architecture of multiple security tactics and how they affect a system. For example, information exposure can impact the Limit Access and Limit Exposure security tactics. The weaknesses in this category could lead to a degradation of the quality of many capabilities if they are not addressed when designing or implementing a secure architecture.
CWE-1013	Encrypt Data	Weaknesses in this category are related to the design and architecture of data confidentiality in a system. Frequently these deal with the use of encryption libraries. The weaknesses in this category could lead to a degradation of the quality data encryption if they are not addressed when designing or implementing a secure architecture.
CWE-1014	Identify Actors	Weaknesses in this category are related to the design and architecture of a system's identification management components. Frequently these deal with verifying that external agents provide inputs into the system. The weaknesses in this category could lead to a degradation of the quality of identification management if they are not addressed when designing or implementing a secure architecture.
CWE-1015	Limit Access	Weaknesses in this category are related to the design and architecture of system resources. Frequently these deal with restricting the amount of resources that are accessed by actors, such as memory, network connections, CPU or access points. The weaknesses in this category could lead to a degradation of the quality of authentication if they are not addressed when designing or implementing a secure architecture.
CWE-1016	Limit Exposure	Weaknesses in this category are related to the design and architecture of the entry points to a system. Frequently these deal with minimizing the attack surface through designing the system with the least needed amount of entry points. The weaknesses in this category could lead to a degradation of a system's defenses if they are not addressed when designing or implementing a secure architecture.
CWE-1017	Lock Computer	Weaknesses in this category are related to the design and architecture of a system's lockout mechanism. Frequently these deal with scenarios that take effect in case of multiple failed attempts to access a given resource. The weaknesses in this category could lead to a degradation of access to system assets if they are not addressed when designing or implementing a secure architecture.
CWE-1018	Manage User Sessions	Weaknesses in this category are related to the design and architecture of session management. Frequently these deal with the information or status about each user and their access rights for the duration of multiple requests. The weaknesses in this category could lead to a degradation of the quality of session management if they are not addressed when designing or implementing a secure architecture.
CWE-1019	Validate Inputs	Weaknesses in this category are related to the design and architecture of a system's input validation components. Frequently these deal with sanitizing, neutralizing and validating any externally provided inputs to minimize malformed data from entering the system and preventing code injection in the input data. The weaknesses in this category could lead to a degradation of the quality of data flow in a system if they are not addressed when designing or implementing a secure architecture.
CWE-1020	Verify Message Integrity	Weaknesses in this category are related to the design and architecture of a system's data integrity components. Frequently these deal with ensuring integrity of data, such as messages, resource files, deployment files, and configuration files. The weaknesses in this category could lead to a degradation of data integrity quality if they are not addressed when designing or implementing a secure architecture.
CWE-1027	OWASP Top Ten 2017 Category A1 - Injection	Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2017.
CWE-1028	OWASP Top Ten 2017 Category A2 - Broken Authentication	Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2017.
CWE-1029	OWASP Top Ten 2017 Category A3 - Sensitive Data Exposure	Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2017.
CWE-1030	OWASP Top Ten 2017 Category A4 - XML External Entities (XXE)	Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2017.
CWE-1031	OWASP Top Ten 2017 Category A5 - Broken Access Control	Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2017.
CWE-1032	OWASP Top Ten 2017 Category A6 - Security Misconfiguration	Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2017.
CWE-1033	OWASP Top Ten 2017 Category A7 - Cross-Site Scripting (XSS)	Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2017.
CWE-1034	OWASP Top Ten 2017 Category A8 - Insecure Deserialization	Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2017.
CWE-1035	OWASP Top Ten 2017 Category A9 - Using Components with Known Vulnerabilities	Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2017.
CWE-1036	OWASP Top Ten 2017 Category A10 - Insufficient Logging & Monitoring	Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2017.
CWE-1129	CISQ Quality Measures (2016) - Reliability	Weaknesses in this category are related to the CISQ Quality Measures for Reliability, as documented in 2016 with the Automated Source Code CISQ Reliability Measure (ASCRM) Specification 1.0. Presence of these weaknesses could reduce the reliability of the software.
CWE-1130	CISQ Quality Measures (2016) - Maintainability	Weaknesses in this category are related to the CISQ Quality Measures for Maintainability, as documented in 2016 with the Automated Source Code Maintainability Measure (ASCMM) Specification 1.0. Presence of these weaknesses could reduce the maintainability of the software.
CWE-1131	CISQ Quality Measures (2016) - Security	Weaknesses in this category are related to the CISQ Quality Measures for Security, as documented in 2016 with the Automated Source Code Security Measure (ASCSM) Specification 1.0. Presence of these weaknesses could reduce the security of the software.
CWE-1132	CISQ Quality Measures (2016) - Performance Efficiency	Weaknesses in this category are related to the CISQ Quality Measures for Performance Efficiency, as documented in 2016 with the Automated Source Code Performance Efficiency Measure (ASCPEM) Specification 1.0. Presence of these weaknesses could reduce the performance efficiency of the software.
CWE-1134	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 00. Input Validation and Data Sanitization (IDS)	Weaknesses in this category are related to the rules and recommendations in the Input Validation and Data Sanitization (IDS) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1135	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 01. Declarations and Initialization (DCL)	Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1136	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 02. Expressions (EXP)	Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1137	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 03. Numeric Types and Operations (NUM)	Weaknesses in this category are related to the rules and recommendations in the Numeric Types and Operations (NUM) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1138	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 04. Characters and Strings (STR)	Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1139	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 05. Object Orientation (OBJ)	Weaknesses in this category are related to the rules and recommendations in the Object Orientation (OBJ) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1140	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 06. Methods (MET)	Weaknesses in this category are related to the rules and recommendations in the Methods (MET) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1141	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 07. Exceptional Behavior (ERR)	Weaknesses in this category are related to the rules and recommendations in the Exceptional Behavior (ERR) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1142	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 08. Visibility and Atomicity (VNA)	Weaknesses in this category are related to the rules and recommendations in the Visibility and Atomicity (VNA) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1143	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 09. Locking (LCK)	Weaknesses in this category are related to the rules and recommendations in the Locking (LCK) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1144	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 10. Thread APIs (THI)	Weaknesses in this category are related to the rules and recommendations in the Thread APIs (THI) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1145	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 11. Thread Pools (TPS)	Weaknesses in this category are related to the rules and recommendations in the Thread Pools (TPS) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1146	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 12. Thread-Safety Miscellaneous (TSM)	Weaknesses in this category are related to the rules and recommendations in the Thread-Safety Miscellaneous (TSM) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1147	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 13. Input Output (FIO)	Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1148	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 14. Serialization (SER)	Weaknesses in this category are related to the rules and recommendations in the Serialization (SER) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1149	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 15. Platform Security (SEC)	Weaknesses in this category are related to the rules and recommendations in the Platform Security (SEC) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1150	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 16. Runtime Environment (ENV)	Weaknesses in this category are related to the rules and recommendations in the Runtime Environment (ENV) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1151	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 17. Java Native Interface (JNI)	Weaknesses in this category are related to the rules and recommendations in the Java Native Interface (JNI) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1152	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 49. Miscellaneous (MSC)	Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1153	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 50. Android (DRD)	Weaknesses in this category are related to the rules and recommendations in the Android (DRD) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1155	SEI CERT C Coding Standard - Guidelines 01. Preprocessor (PRE)	Weaknesses in this category are related to the rules and recommendations in the Preprocessor (PRE) section of the SEI CERT C Coding Standard.
CWE-1156	SEI CERT C Coding Standard - Guidelines 02. Declarations and Initialization (DCL)	Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT C Coding Standard.
CWE-1157	SEI CERT C Coding Standard - Guidelines 03. Expressions (EXP)	Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT C Coding Standard.
CWE-1158	SEI CERT C Coding Standard - Guidelines 04. Integers (INT)	Weaknesses in this category are related to the rules and recommendations in the Integers (INT) section of the SEI CERT C Coding Standard.
CWE-1159	SEI CERT C Coding Standard - Guidelines 05. Floating Point (FLP)	Weaknesses in this category are related to the rules and recommendations in the Floating Point (FLP) section of the SEI CERT C Coding Standard.
CWE-1160	SEI CERT C Coding Standard - Guidelines 06. Arrays (ARR)	Weaknesses in this category are related to the rules and recommendations in the Arrays (ARR) section of the SEI CERT C Coding Standard.
CWE-1161	SEI CERT C Coding Standard - Guidelines 07. Characters and Strings (STR)	Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) section of the SEI CERT C Coding Standard.
CWE-1162	SEI CERT C Coding Standard - Guidelines 08. Memory Management (MEM)	Weaknesses in this category are related to the rules and recommendations in the Memory Management (MEM) section of the SEI CERT C Coding Standard.
CWE-1163	SEI CERT C Coding Standard - Guidelines 09. Input Output (FIO)	Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) section of the SEI CERT C Coding Standard.
CWE-1165	SEI CERT C Coding Standard - Guidelines 10. Environment (ENV)	Weaknesses in this category are related to the rules and recommendations in the Environment (ENV) section of the SEI CERT C Coding Standard.
CWE-1166	SEI CERT C Coding Standard - Guidelines 11. Signals (SIG)	Weaknesses in this category are related to the rules and recommendations in the Signals (SIG) section of the SEI CERT C Coding Standard.
CWE-1167	SEI CERT C Coding Standard - Guidelines 12. Error Handling (ERR)	Weaknesses in this category are related to the rules and recommendations in the Error Handling (ERR) section of the SEI CERT C Coding Standard.
CWE-1168	SEI CERT C Coding Standard - Guidelines 13. Application Programming Interfaces (API)	Weaknesses in this category are related to the rules and recommendations in the Application Programming Interfaces (API) section of the SEI CERT C Coding Standard.
CWE-1169	SEI CERT C Coding Standard - Guidelines 14. Concurrency (CON)	Weaknesses in this category are related to the rules and recommendations in the Concurrency (CON) section of the SEI CERT C Coding Standard.
CWE-1170	SEI CERT C Coding Standard - Guidelines 48. Miscellaneous (MSC)	Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT C Coding Standard.
CWE-1171	SEI CERT C Coding Standard - Guidelines 50. POSIX (POS)	Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) section of the SEI CERT C Coding Standard.
CWE-1172	SEI CERT C Coding Standard - Guidelines 51. Microsoft Windows (WIN)	Weaknesses in this category are related to the rules and recommendations in the Microsoft Windows (WIN) section of the SEI CERT C Coding Standard.
CWE-1175	SEI CERT Oracle Secure Coding Standard for Java - Guidelines 18. Concurrency (CON)	Weaknesses in this category are related to the rules and recommendations in the Concurrency (CON) section of the SEI CERT Oracle Secure Coding Standard for Java.
CWE-1179	SEI CERT Perl Coding Standard - Guidelines 01. Input Validation and Data Sanitization (IDS)	Weaknesses in this category are related to the rules and recommendations in the Input Validation and Data Sanitization (IDS) section of the SEI CERT Perl Coding Standard.
CWE-1180	SEI CERT Perl Coding Standard - Guidelines 02. Declarations and Initialization (DCL)	Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) section of the SEI CERT Perl Coding Standard.
CWE-1181	SEI CERT Perl Coding Standard - Guidelines 03. Expressions (EXP)	Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) section of the SEI CERT Perl Coding Standard.
CWE-1182	SEI CERT Perl Coding Standard - Guidelines 04. Integers (INT)	Weaknesses in this category are related to the rules and recommendations in the Integers (INT) section of the SEI CERT Perl Coding Standard.
CWE-1183	SEI CERT Perl Coding Standard - Guidelines 05. Strings (STR)	Weaknesses in this category are related to the rules and recommendations in the Strings (STR) section of the SEI CERT Perl Coding Standard.
CWE-1184	SEI CERT Perl Coding Standard - Guidelines 06. Object-Oriented Programming (OOP)	Weaknesses in this category are related to the rules and recommendations in the Object-Oriented Programming (OOP) section of the SEI CERT Perl Coding Standard.
CWE-1185	SEI CERT Perl Coding Standard - Guidelines 07. File Input and Output (FIO)	Weaknesses in this category are related to the rules and recommendations in the File Input and Output (FIO) section of the SEI CERT Perl Coding Standard.
CWE-1186	SEI CERT Perl Coding Standard - Guidelines 50. Miscellaneous (MSC)	Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) section of the SEI CERT Perl Coding Standard.
CWE-1195	Manufacturing and Life Cycle Management Concerns	Weaknesses in this category are root-caused to defects that arise in the semiconductor-manufacturing process or during the life cycle and supply chain.
CWE-1196	Security Flow Issues	Weaknesses in this category are related to improper design of full-system security flows, including but not limited to secure boot, secure update, and hardware-device attestation.
CWE-1197	Integration Issues	Weaknesses in this category are those that arise due to integration of multiple hardware Intellectual Property (IP) cores, from System-on-a-Chip (SoC) subsystem interactions, or from hardware platform subsystem interactions.
CWE-1198	Privilege Separation and Access Control Issues	Weaknesses in this category are related to features and mechanisms providing hardware-based isolation and access control (e.g., identity, policy, locking control) of sensitive shared hardware resources such as registers and fuses.
CWE-1199	General Circuit and Logic Design Concerns	Weaknesses in this category are related to hardware-circuit design and logic (e.g., CMOS transistors, finite state machines, and registers) as well as issues related to hardware description languages such as System Verilog and VHDL.
CWE-1201	Core and Compute Issues	Weaknesses in this category are typically associated with CPUs, Graphics, Vision, AI, FPGA, and microcontrollers.
CWE-1202	Memory and Storage Issues	Weaknesses in this category are typically associated with memory (e.g., DRAM, SRAM) and storage technologies (e.g., NAND Flash, OTP, EEPROM, and eMMC).
CWE-1203	Peripherals, On-chip Fabric, and Interface/IO Problems	Weaknesses in this category are related to hardware security problems that apply to peripheral devices, IO interfaces, on-chip interconnects, network-on-chip (NoC), and buses. For example, this category includes issues related to design of hardware interconnect and/or protocols such as PCIe, USB, SMBUS, general-purpose IO pins, and user-input peripherals such as mouse and keyboard.
CWE-1205	Security Primitives and Cryptography Issues	Weaknesses in this category are related to hardware implementations of cryptographic protocols and other hardware-security primitives such as physical unclonable functions (PUFs) and random number generators (RNGs).
CWE-1206	Power, Clock, Thermal, and Reset Concerns	Weaknesses in this category are related to system power, voltage, current, temperature, clocks, system state saving/restoring, and resets at the platform and SoC level.
CWE-1207	Debug and Test Problems	Weaknesses in this category are related to hardware debug and test interfaces such as JTAG and scan chain.
CWE-1208	Cross-Cutting Problems	Weaknesses in this category can arise in multiple areas of hardware design or can apply to a wide cross-section of components.
CWE-1210	Audit / Logging Errors	Weaknesses in this category are related to audit-based components of a software system. Frequently these deal with logging user activities in order to identify undesired access and modifications to the system. The weaknesses in this category could lead to a degradation of the quality of the audit capability if they are not addressed.
CWE-1211	Authentication Errors	Weaknesses in this category are related to authentication components of a system. Frequently these deal with the ability to verify that an entity is indeed who it claims to be. If not addressed when designing or implementing a software system, these weaknesses could lead to a degradation of the quality of the authentication capability.
CWE-1212	Authorization Errors	Weaknesses in this category are related to authorization components of a system. Frequently these deal with the ability to enforce that agents have the required permissions before performing certain operations, such as modifying data. If not addressed when designing or implementing a software system, these weaknesses could lead to a degradation of the quality of the authorization capability.
CWE-1213	Random Number Issues	Weaknesses in this category are related to a software system's random number generation.
CWE-1214	Data Integrity Issues	Weaknesses in this category are related to a software system's data integrity components. Frequently these deal with the ability to ensure the integrity of data, such as messages, resource files, deployment files, and configuration files. The weaknesses in this category could lead to a degradation of data integrity quality if they are not addressed.
CWE-1215	Data Validation Issues	Weaknesses in this category are related to a software system's components for input validation, output validation, or other kinds of validation. Validation is a frequently-used technique for ensuring that data conforms to expectations before it is further processed as input or output. There are many varieties of validation (see CWE-20, which is just for input validation). Validation is distinct from other techniques that attempt to modify data before processing it, although developers may consider all attempts to product "safe" inputs or outputs as some kind of validation. Regardless, validation is a powerful tool that is often used to minimize malformed data from entering the system, or indirectly avoid code injection or other potentially-malicious patterns when generating output. The weaknesses in this category could lead to a degradation of the quality of data flow in a system if they are not addressed.
CWE-1216	Lockout Mechanism Errors	Weaknesses in this category are related to a software system's lockout mechanism. Frequently these deal with scenarios that take effect in case of multiple failed attempts to access a given resource. The weaknesses in this category could lead to a degradation of access to system assets if they are not addressed.
CWE-1217	User Session Errors	Weaknesses in this category are related to session management. Frequently these deal with the information or status about each user and their access rights for the duration of multiple requests. The weaknesses in this category could lead to a degradation of the quality of session management if they are not addressed.
CWE-1218	Memory Buffer Errors	Weaknesses in this category are related to the handling of memory buffers within a software system.
CWE-1219	File Handling Issues	Weaknesses in this category are related to the handling of files within a software system. Files, directories, and folders are so central to information technology that many different weaknesses and variants have been discovered.
CWE-1225	Documentation Issues	Weaknesses in this category are related to the documentation provided to support, create, or analyze a product.
CWE-1226	Complexity Issues	Weaknesses in this category are associated with things being overly complex.
CWE-1227	Encapsulation Issues	Weaknesses in this category are related to issues surrounding the bundling of data with the methods intended to operate on that data.
CWE-1228	API / Function Errors	Weaknesses in this category are related to the use of built-in functions or external APIs.
CWE-1237	SFP Primary Cluster: Faulty Resource Release	This category identifies Software Fault Patterns (SFPs) within the Faulty Resource Release cluster (SFP37).
CWE-1238	SFP Primary Cluster: Failure to Release Memory	This category identifies Software Fault Patterns (SFPs) within the Failure to Release Memory cluster (SFP38).
CWE-1306	CISQ Quality Measures - Reliability	Weaknesses in this category are related to the CISQ Quality Measures for Reliability. Presence of these weaknesses could reduce the reliability of the software.
CWE-1307	CISQ Quality Measures - Maintainability	Weaknesses in this category are related to the CISQ Quality Measures for Maintainability. Presence of these weaknesses could reduce the maintainability of the software.
CWE-1308	CISQ Quality Measures - Security	Weaknesses in this category are related to the CISQ Quality Measures for Security. Presence of these weaknesses could reduce the security of the software.
CWE-1309	CISQ Quality Measures - Efficiency	Weaknesses in this category are related to the CISQ Quality Measures for Efficiency. Presence of these weaknesses could reduce the efficiency of the software.
CWE-133	String Errors	Weaknesses in this category are related to the creation and modification of strings.
CWE-1345	OWASP Top Ten 2021 Category A01:2021 - Broken Access Control	Weaknesses in this category are related to the A01 category "Broken Access Control" in the OWASP Top Ten 2021.
CWE-1346	OWASP Top Ten 2021 Category A02:2021 - Cryptographic Failures	Weaknesses in this category are related to the A02 category "Cryptographic Failures" in the OWASP Top Ten 2021.
CWE-1347	OWASP Top Ten 2021 Category A03:2021 - Injection	Weaknesses in this category are related to the A03 category "Injection" in the OWASP Top Ten 2021.
CWE-1348	OWASP Top Ten 2021 Category A04:2021 - Insecure Design	Weaknesses in this category are related to the A04 "Insecure Design" category in the OWASP Top Ten 2021.
CWE-1349	OWASP Top Ten 2021 Category A05:2021 - Security Misconfiguration	Weaknesses in this category are related to the A05 category "Security Misconfiguration" in the OWASP Top Ten 2021.
CWE-1352	OWASP Top Ten 2021 Category A06:2021 - Vulnerable and Outdated Components	Weaknesses in this category are related to the A06 category "Vulnerable and Outdated Components" in the OWASP Top Ten 2021.
CWE-1353	OWASP Top Ten 2021 Category A07:2021 - Identification and Authentication Failures	Weaknesses in this category are related to the A07 category "Identification and Authentication Failures" in the OWASP Top Ten 2021.
CWE-1354	OWASP Top Ten 2021 Category A08:2021 - Software and Data Integrity Failures	Weaknesses in this category are related to the A08 category "Software and Data Integrity Failures" in the OWASP Top Ten 2021.
CWE-1355	OWASP Top Ten 2021 Category A09:2021 - Security Logging and Monitoring Failures	Weaknesses in this category are related to the A09 category "Security Logging and Monitoring Failures" in the OWASP Top Ten 2021.
CWE-1356	OWASP Top Ten 2021 Category A10:2021 - Server-Side Request Forgery (SSRF)	Weaknesses in this category are related to the A10 category "Server-Side Request Forgery (SSRF)" in the OWASP Top Ten 2021.
CWE-1359	ICS Communications	Weaknesses in this category are related to the "ICS Communications" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.
CWE-136	Type Errors	Weaknesses in this category are caused by improper data type transformation or improper handling of multiple data types.
CWE-1360	ICS Dependencies (& Architecture)	Weaknesses in this category are related to the "ICS Dependencies (& Architecture)" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.
CWE-1361	ICS Supply Chain	Weaknesses in this category are related to the "ICS Supply Chain" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.
CWE-1362	ICS Engineering (Constructions/Deployment)	Weaknesses in this category are related to the "ICS Engineering (Constructions/Deployment)" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.
CWE-1363	ICS Operations (& Maintenance)	Weaknesses in this category are related to the "ICS Operations (& Maintenance)" super category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022.
CWE-1364	ICS Communications: Zone Boundary Failures	Weaknesses in this category are related to the "Zone Boundary Failures" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Within an ICS system, for traffic that crosses through network zone boundaries, vulnerabilities arise when those boundaries were designed for safety or other purposes but are being repurposed for security." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1365	ICS Communications: Unreliability	Weaknesses in this category are related to the "Unreliability" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Vulnerabilities arise in reaction to disruptions in the physical layer (e.g. creating electrical noise) used to carry the traffic." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1366	ICS Communications: Frail Security in Protocols	Weaknesses in this category are related to the "Frail Security in Protocols" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Vulnerabilities arise as a result of mis-implementation or incomplete implementation of security in ICS implementations of communication protocols." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1367	ICS Dependencies (& Architecture): External Physical Systems	Weaknesses in this category are related to the "External Physical Systems" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Due to the highly interconnected technologies in use, an external dependency on another physical system could cause an availability interruption for the protected system." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1368	ICS Dependencies (& Architecture): External Digital Systems	Weaknesses in this category are related to the "External Digital Systems" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Due to the highly interconnected technologies in use, an external dependency on another digital system could cause a confidentiality, integrity, or availability incident for the protected system." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1369	ICS Supply Chain: IT/OT Convergence/Expansion	Weaknesses in this category are related to the "IT/OT Convergence/Expansion" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "The increased penetration of DER devices and smart loads make emerging ICS networks more like IT networks and thus susceptible to vulnerabilities similar to those of IT networks." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-137	Data Neutralization Issues	Weaknesses in this category are related to the creation or neutralization of data using an incorrect format.
CWE-1370	ICS Supply Chain: Common Mode Frailties	Weaknesses in this category are related to the "Common Mode Frailties" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "At the component level, most ICS systems are assembled from common parts made by other companies. One or more of these common parts might contain a vulnerability that could result in a wide-spread incident." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1371	ICS Supply Chain: Poorly Documented or Undocumented Features	Weaknesses in this category are related to the "Poorly Documented or Undocumented Features" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Undocumented capabilities and configurations pose a risk by not having a clear understanding of what the device is specifically supposed to do and only do. Therefore possibly opening up the attack surface and vulnerabilities." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1372	ICS Supply Chain: OT Counterfeit and Malicious Corruption	Weaknesses in this category are related to the "OT Counterfeit and Malicious Corruption" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "In ICS, when this procurement process results in a vulnerability or component damage, it can have grid impacts or cause physical harm." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1373	ICS Engineering (Construction/Deployment): Trust Model Problems	Weaknesses in this category are related to the "Trust Model Problems" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Assumptions made about the user during the design or construction phase may result in vulnerabilities after the system is installed if the user operates it using a different security approach or process than what was designed or built." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1374	ICS Engineering (Construction/Deployment): Maker Breaker Blindness	Weaknesses in this category are related to the "Maker Breaker Blindness" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Lack of awareness of deliberate attack techniques by people (vs failure modes from natural causes like weather or metal fatigue) may lead to insufficient security controls being built into ICS systems." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1375	ICS Engineering (Construction/Deployment): Gaps in Details/Data	Weaknesses in this category are related to the "Gaps in Details/Data" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Highly complex systems are often operated by personnel who have years of experience in managing that particular facility or plant. Much of their knowledge is passed along through verbal or hands-on training but may not be fully documented in written practices and procedures." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1376	ICS Engineering (Construction/Deployment): Security Gaps in Commissioning	Weaknesses in this category are related to the "Security Gaps in Commissioning" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "As a large system is brought online components of the system may remain vulnerable until the entire system is operating and functional and security controls are put in place. This creates a window of opportunity for an adversary during the commissioning process." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1377	ICS Engineering (Construction/Deployment): Inherent Predictability in Design	Weaknesses in this category are related to the "Inherent Predictability in Design" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "The commonality of design (in ICS/SCADA architectures) for energy systems and environments opens up the possibility of scaled compromise by leveraging the inherent predictability in the design." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1378	ICS Operations (& Maintenance): Gaps in obligations and training	Weaknesses in this category are related to the "Gaps in obligations and training" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "OT ownership and responsibility for identifying and mitigating vulnerabilities are not clearly defined or communicated within an organization, leaving environments unpatched, exploitable, and with a broader attack surface." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1379	ICS Operations (& Maintenance): Human factors in ICS environments	Weaknesses in this category are related to the "Human factors in ICS environments" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Environmental factors in ICS including physical duress, system complexities, and isolation may result in security gaps or inadequacies in the performance of individual duties and responsibilities." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1380	ICS Operations (& Maintenance): Post-analysis changes	Weaknesses in this category are related to the "Post-analysis changes" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Changes made to a previously analyzed and approved ICS environment can introduce new security vulnerabilities (as opposed to safety)." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1381	ICS Operations (& Maintenance): Exploitable Standard Operational Procedures	Weaknesses in this category are related to the "Exploitable Standard Operational Procedures" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "Standard ICS Operational Procedures developed for safety and operational functionality in a closed, controlled communications environment can introduce vulnerabilities in a more connected environment." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1382	ICS Operations (& Maintenance): Emerging Energy Technologies	Weaknesses in this category are related to the "Emerging Energy Technologies" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "With the rapid evolution of the energy system accelerated by the emergence of new technologies such as DERs, electric vehicles, advanced communications (5G+), novel and diverse challenges arise for secure and resilient operation of the system." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1383	ICS Operations (& Maintenance): Compliance/Conformance with Regulatory Requirements	Weaknesses in this category are related to the "Compliance/Conformance with Regulatory Requirements" category from the SEI ETF "Categories of Security Vulnerabilities in ICS" as published in March 2022: "The ICS environment faces overlapping regulatory regimes and authorities with multiple focus areas (e.g., operational resiliency, physical safety, interoperability, and security) which can result in cyber security vulnerabilities when implemented as written due to gaps in considerations, outdatedness, or conflicting requirements." Note: members of this category include "Nearest IT Neighbor" recommendations from the report, as well as suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1388	Physical Access Issues and Concerns	Weaknesses in this category are related to concerns of physical access.
CWE-139	DEPRECATED: General Special Element Problems	This entry has been deprecated. It is a leftover from PLOVER, but CWE-138 is a more appropriate mapping.
CWE-1396	Comprehensive Categorization: Access Control	Weaknesses in this category are related to access control.
CWE-1397	Comprehensive Categorization: Comparison	Weaknesses in this category are related to comparison.
CWE-1398	Comprehensive Categorization: Component Interaction	Weaknesses in this category are related to component interaction.
CWE-1399	Comprehensive Categorization: Memory Safety	Weaknesses in this category are related to memory safety.
CWE-1401	Comprehensive Categorization: Concurrency	Weaknesses in this category are related to concurrency.
CWE-1402	Comprehensive Categorization: Encryption	Weaknesses in this category are related to encryption.
CWE-1403	Comprehensive Categorization: Exposed Resource	Weaknesses in this category are related to exposed resource.
CWE-1404	Comprehensive Categorization: File Handling	Weaknesses in this category are related to file handling.
CWE-1405	Comprehensive Categorization: Improper Check or Handling of Exceptional Conditions	Weaknesses in this category are related to improper check or handling of exceptional conditions.
CWE-1406	Comprehensive Categorization: Improper Input Validation	Weaknesses in this category are related to improper input validation.
CWE-1407	Comprehensive Categorization: Improper Neutralization	Weaknesses in this category are related to improper neutralization.
CWE-1408	Comprehensive Categorization: Incorrect Calculation	Weaknesses in this category are related to incorrect calculation.
CWE-1409	Comprehensive Categorization: Injection	Weaknesses in this category are related to injection.
CWE-1410	Comprehensive Categorization: Insufficient Control Flow Management	Weaknesses in this category are related to insufficient control flow management.
CWE-1411	Comprehensive Categorization: Insufficient Verification of Data Authenticity	Weaknesses in this category are related to insufficient verification of data authenticity.
CWE-1412	Comprehensive Categorization: Poor Coding Practices	Weaknesses in this category are related to poor coding practices.
CWE-1413	Comprehensive Categorization: Protection Mechanism Failure	Weaknesses in this category are related to protection mechanism failure.
CWE-1414	Comprehensive Categorization: Randomness	Weaknesses in this category are related to randomness.
CWE-1415	Comprehensive Categorization: Resource Control	Weaknesses in this category are related to resource control.
CWE-1416	Comprehensive Categorization: Resource Lifecycle Management	Weaknesses in this category are related to resource lifecycle management.
CWE-1417	Comprehensive Categorization: Sensitive Information Exposure	Weaknesses in this category are related to sensitive information exposure.
CWE-1418	Comprehensive Categorization: Violation of Secure Design Principles	Weaknesses in this category are related to violation of secure design principles.
CWE-1433	2025 MIHW Supplement: Expert Insights	Weaknesses in this category were not included in the 2025 Most Important Hardware Weaknesses (MIHW) because they did not have sufficient weakness data to support their inclusion. However, they stand out as expert-driven selections. Each of these weaknesses received high scores from Subject Matter Experts, reflecting strong consensus among those with deep domain knowledge.
CWE-16	Configuration	Weaknesses in this category are typically introduced during the configuration of the software.
CWE-169	DEPRECATED: Technology-Specific Special Elements	This category has been deprecated. It was originally intended as a "catch-all" for input validation problems in technologies that did not have their own CWE, but introduces unnecessary depth to the hierarchy.
CWE-17	DEPRECATED: Code	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-171	DEPRECATED: Cleansing, Canonicalization, and Comparison Errors	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree. Weaknesses in this category were related to improper handling of data within protection mechanisms that attempt to perform neutralization for untrusted data. These weaknesses can be found in other similar categories.
CWE-18	DEPRECATED: Source Code	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-189	Numeric Errors	Weaknesses in this category are related to improper calculation or conversion of numbers.
CWE-19	Data Processing Errors	Weaknesses in this category are typically found in functionality that processes data. Data processing is the manipulation of input to retrieve or save information.
CWE-199	Information Management Errors	Weaknesses in this category are related to improper handling of sensitive information.
CWE-2	7PK - Environment	This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that are typically introduced during unexpected environmental conditions. According to the authors of the Seven Pernicious Kingdoms, "This section includes everything that is outside of the source code but is still critical to the security of the product that is being created. Because the issues covered by this kingdom are not directly related to source code, we separated it from the rest of the kingdoms."
CWE-21	DEPRECATED: Pathname Traversal and Equivalence Errors	This category has been deprecated. It was originally used for organizing weaknesses involving file names, which enabled access to files outside of a restricted directory (path traversal) or to perform operations on files that would otherwise be restricted (path equivalence). Consider using either the File Handling Issues category (CWE-1219) or the class Use of Incorrectly-Resolved Name or Reference (CWE-706).
CWE-227	7PK - API Abuse	This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that involve the software using an API in a manner contrary to its intended use. According to the authors of the Seven Pernicious Kingdoms, "An API is a contract between a caller and a callee. The most common forms of API misuse occurs when the caller does not honor its end of this contract. For example, if a program does not call chdir() after calling chroot(), it violates the contract that specifies how to change the active root directory in a secure fashion. Another good example of library abuse is expecting the callee to return trustworthy DNS information to the caller. In this case, the caller misuses the callee API by making certain assumptions about its behavior (that the return value can be used for authentication purposes). One can also violate the caller-callee contract from the other side. For example, if a coder subclasses SecureRandom and returns a non-random value, the contract is violated."
CWE-251	Often Misused: String Management	Functions that manipulate strings encourage buffer overflows.
CWE-254	7PK - Security Features	Software security is not security software. Here we're concerned with topics like authentication, access control, confidentiality, cryptography, and privilege management.
CWE-255	Credentials Management Errors	Weaknesses in this category are related to the management of credentials.
CWE-264	Permissions, Privileges, and Access Controls	Weaknesses in this category are related to the management of permissions, privileges, and other security features that are used to perform access control.
CWE-265	Privilege Issues	Weaknesses in this category occur with improper handling, assignment, or management of privileges. A privilege is a property of an agent, such as a user. It lets the agent do things that are not ordinarily allowed. For example, there are privileges which allow an agent to perform maintenance functions such as restart a computer.
CWE-275	Permission Issues	Weaknesses in this category are related to improper assignment or handling of permissions.
CWE-3	DEPRECATED: Technology-specific Environment Issues	This category has been deprecated. It was originally intended as a "catch-all" for environment issues for technologies that did not have their own CWE, but it introduced unnecessary depth and complexity to the Development View (CWE-699).
CWE-310	Cryptographic Issues	Weaknesses in this category are related to the design and implementation of data confidentiality and integrity. Frequently these deal with the use of encoding techniques, encryption libraries, and hashing algorithms. The weaknesses in this category could lead to a degradation of the quality data if they are not addressed.
CWE-320	Key Management Errors	Weaknesses in this category are related to errors in the management of cryptographic keys.
CWE-355	User Interface Security Issues	Weaknesses in this category are related to or introduced in the User Interface (UI).
CWE-361	7PK - Time and State	This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses related to the improper management of time and state in an environment that supports simultaneous or near-simultaneous computation by multiple systems, processes, or threads. According to the authors of the Seven Pernicious Kingdoms, "Distributed computation is about time and state. That is, in order for more than one component to communicate, state must be shared, and all that takes time. Most programmers anthropomorphize their work. They think about one thread of control carrying out the entire program in the same way they would if they had to do the job themselves. Modern computers, however, switch between tasks very quickly, and in multi-core, multi-CPU, or distributed systems, two events may take place at exactly the same time. Defects rush to fill the gap between the programmer's model of how a program executes and what happens in reality. These defects are related to unexpected interactions between threads, processes, time, and information. These interactions happen through shared state: semaphores, variables, the file system, and, basically, anything that can store information."
CWE-371	State Issues	Weaknesses in this category are related to improper management of system state.
CWE-376	DEPRECATED: Temporary File Issues	This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree. Consider using the File Handling Issues category (CWE-1219).
CWE-380	DEPRECATED: Technology-Specific Time and State Issues	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-381	DEPRECATED: J2EE Time and State Issues	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-387	Signal Errors	Weaknesses in this category are related to the improper handling of signals.
CWE-388	7PK - Errors	This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when an application does not properly handle errors that occur during processing. According to the authors of the Seven Pernicious Kingdoms, "Errors and error handling represent a class of API. Errors related to error handling are so common that they deserve a special kingdom of their own. As with 'API Abuse,' there are two ways to introduce an error-related security vulnerability: the most common one is handling errors poorly (or not at all). The second is producing errors that either give out too much information (to possible attackers) or are difficult to handle."
CWE-389	Error Conditions, Return Values, Status Codes	This category includes weaknesses that occur if a function does not generate the correct return/status code, or if the application does not handle all possible return/status codes that could be generated by a function. This type of problem is most often found in conditions that are rarely encountered during the normal operation of the product. Presumably, most bugs related to common conditions are found and eliminated during development and testing. In some cases, the attacker can directly control or influence the environment to trigger the rare conditions.
CWE-398	7PK - Code Quality	This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that do not directly introduce a weakness or vulnerability, but indicate that the product has not been carefully developed or maintained. According to the authors of the Seven Pernicious Kingdoms, "Poor code quality leads to unpredictable behavior. From a user's perspective that often manifests itself as poor usability. For an adversary it provides an opportunity to stress the system in unexpected ways."
CWE-399	Resource Management Errors	Weaknesses in this category are related to improper management of system resources.
CWE-4	DEPRECATED: J2EE Environment Issues	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-411	Resource Locking Problems	Weaknesses in this category are related to improper handling of locks that are used to control access to resources.
CWE-417	Communication Channel Errors	Weaknesses in this category are related to improper handling of communication channels and access paths. These weaknesses include problems in creating, managing, or removing alternate channels and alternate paths. Some of these can overlap virtual file problems and are commonly used in "bypass" attacks, such as those that exploit authentication errors.
CWE-418	DEPRECATED: Channel Errors	This category has been deprecated because it redundant with the grouping provided by CWE-417.
CWE-429	Handler Errors	Weaknesses in this category are related to improper management of handlers.
CWE-438	Behavioral Problems	Weaknesses in this category are related to unexpected behaviors from code that an application uses.
CWE-442	DEPRECATED: Web Problems	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-445	DEPRECATED: User Interface Errors	This weakness has been deprecated because it was a duplicate of CWE-355. All content has been transferred to CWE-355.
CWE-452	Initialization and Cleanup Errors	Weaknesses in this category occur in behaviors that are used for initialization and breakdown.
CWE-461	DEPRECATED: Data Structure Issues	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-465	Pointer Issues	Weaknesses in this category are related to improper handling of pointers.
CWE-485	7PK - Encapsulation	This category represents one of the phyla in the Seven Pernicious Kingdoms vulnerability classification. It includes weaknesses that occur when the product does not sufficiently encapsulate critical data or functionality. According to the authors of the Seven Pernicious Kingdoms, "Encapsulation is about drawing strong boundaries. In a web browser that might mean ensuring that your mobile code cannot be abused by other mobile code. On the server it might mean differentiation between validated data and unvalidated data, between one user's data and another's, or between data users are allowed to see and data that they are not."
CWE-490	DEPRECATED: Mobile Code Issues	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-503	DEPRECATED: Byte/Object Code	This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-504	DEPRECATED: Motivation/Intent	This category has been deprecated. It was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-505	DEPRECATED: Intentionally Introduced Weakness	This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-513	DEPRECATED: Intentionally Introduced Nonmalicious Weakness	This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-517	DEPRECATED: Other Intentional, Nonmalicious Weakness	This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-518	DEPRECATED: Inadvertently Introduced Weakness	This category has been deprecated as it was originally used for organizing the Development View (CWE-699), but it introduced unnecessary complexity and depth to the resulting tree.
CWE-519	DEPRECATED: .NET Environment Issues	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-557	Concurrency Issues	Weaknesses in this category are related to concurrent use of shared resources.
CWE-559	DEPRECATED: Often Misused: Arguments and Parameters	This entry has been deprecated. It was originally used for organizing the Development View (CWE-699) and some other views, but it introduced unnecessary complexity and depth to the resulting tree.
CWE-569	Expression Issues	Weaknesses in this category are related to incorrectly written expressions within code.
CWE-60	DEPRECATED: UNIX Path Link Problems	This category has been deprecated. It covered a very low level of abstraction based on operating system, which was not useful for any existing view.
CWE-63	DEPRECATED: Windows Path Link Problems	This category has been deprecated. It covered a very low level of abstraction based on operating system, which was not useful for any existing view.
CWE-632	DEPRECATED: Weaknesses that Affect Files or Directories	This category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.
CWE-633	DEPRECATED: Weaknesses that Affect Memory	This category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.
CWE-634	DEPRECATED: Weaknesses that Affect System Processes	This category has been deprecated. It was not actively maintained, and it was not useful to stakeholders. It was originally created before CWE 1.0 as part of view CWE-631, which was a simple example of how views could be structured within CWE.
CWE-68	DEPRECATED: Windows Virtual File Problems	This category has been deprecated as it was found to be an unnecessary abstraction of platform specific details. Please refer to the category CWE-632 and weakness CWE-66 for relevant relationships.
CWE-70	DEPRECATED: Mac Virtual File Problems	This category has been deprecated as it was found to be an unnecessary abstraction of platform specific details. Please refer to the category CWE-632 and weakness CWE-66 for relevant relationships.
CWE-712	OWASP Top Ten 2007 Category A1 - Cross Site Scripting (XSS)	Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2007.
CWE-713	OWASP Top Ten 2007 Category A2 - Injection Flaws	Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2007.
CWE-714	OWASP Top Ten 2007 Category A3 - Malicious File Execution	Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2007.
CWE-715	OWASP Top Ten 2007 Category A4 - Insecure Direct Object Reference	Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2007.
CWE-716	OWASP Top Ten 2007 Category A5 - Cross Site Request Forgery (CSRF)	Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2007.
CWE-717	OWASP Top Ten 2007 Category A6 - Information Leakage and Improper Error Handling	Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2007.
CWE-718	OWASP Top Ten 2007 Category A7 - Broken Authentication and Session Management	Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2007.
CWE-719	OWASP Top Ten 2007 Category A8 - Insecure Cryptographic Storage	Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2007.
CWE-720	OWASP Top Ten 2007 Category A9 - Insecure Communications	Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2007.
CWE-721	OWASP Top Ten 2007 Category A10 - Failure to Restrict URL Access	Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2007.
CWE-722	OWASP Top Ten 2004 Category A1 - Unvalidated Input	Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2004.
CWE-723	OWASP Top Ten 2004 Category A2 - Broken Access Control	Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2004.
CWE-724	OWASP Top Ten 2004 Category A3 - Broken Authentication and Session Management	Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2004.
CWE-725	OWASP Top Ten 2004 Category A4 - Cross-Site Scripting (XSS) Flaws	Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2004.
CWE-726	OWASP Top Ten 2004 Category A5 - Buffer Overflows	Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2004.
CWE-727	OWASP Top Ten 2004 Category A6 - Injection Flaws	Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2004.
CWE-728	OWASP Top Ten 2004 Category A7 - Improper Error Handling	Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2004.
CWE-729	OWASP Top Ten 2004 Category A8 - Insecure Storage	Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2004.
CWE-730	OWASP Top Ten 2004 Category A9 - Denial of Service	Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2004.
CWE-731	OWASP Top Ten 2004 Category A10 - Insecure Configuration Management	Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2004.
CWE-735	CERT C Secure Coding Standard (2008) Chapter 2 - Preprocessor (PRE)	Weaknesses in this category are related to the rules and recommendations in the Preprocessor (PRE) chapter of the CERT C Secure Coding Standard (2008).
CWE-736	CERT C Secure Coding Standard (2008) Chapter 3 - Declarations and Initialization (DCL)	Weaknesses in this category are related to the rules and recommendations in the Declarations and Initialization (DCL) chapter of the CERT C Secure Coding Standard (2008).
CWE-737	CERT C Secure Coding Standard (2008) Chapter 4 - Expressions (EXP)	Weaknesses in this category are related to the rules and recommendations in the Expressions (EXP) chapter of the CERT C Secure Coding Standard (2008).
CWE-738	CERT C Secure Coding Standard (2008) Chapter 5 - Integers (INT)	Weaknesses in this category are related to the rules and recommendations in the Integers (INT) chapter of the CERT C Secure Coding Standard (2008).
CWE-739	CERT C Secure Coding Standard (2008) Chapter 6 - Floating Point (FLP)	Weaknesses in this category are related to the rules and recommendations in the Floating Point (FLP) chapter of the CERT C Secure Coding Standard (2008).
CWE-740	CERT C Secure Coding Standard (2008) Chapter 7 - Arrays (ARR)	Weaknesses in this category are related to the rules and recommendations in the Arrays (ARR) chapter of the CERT C Secure Coding Standard (2008).
CWE-741	CERT C Secure Coding Standard (2008) Chapter 8 - Characters and Strings (STR)	Weaknesses in this category are related to the rules and recommendations in the Characters and Strings (STR) chapter of the CERT C Secure Coding Standard (2008).
CWE-742	CERT C Secure Coding Standard (2008) Chapter 9 - Memory Management (MEM)	Weaknesses in this category are related to the rules and recommendations in the Memory Management (MEM) chapter of the CERT C Secure Coding Standard (2008).
CWE-743	CERT C Secure Coding Standard (2008) Chapter 10 - Input Output (FIO)	Weaknesses in this category are related to the rules and recommendations in the Input Output (FIO) chapter of the CERT C Secure Coding Standard (2008).
CWE-744	CERT C Secure Coding Standard (2008) Chapter 11 - Environment (ENV)	Weaknesses in this category are related to the rules and recommendations in the Environment (ENV) chapter of the CERT C Secure Coding Standard (2008).
CWE-745	CERT C Secure Coding Standard (2008) Chapter 12 - Signals (SIG)	Weaknesses in this category are related to the rules and recommendations in the Signals (SIG) chapter of the CERT C Secure Coding Standard (2008).
CWE-746	CERT C Secure Coding Standard (2008) Chapter 13 - Error Handling (ERR)	Weaknesses in this category are related to the rules and recommendations in the Error Handling (ERR) chapter of the CERT C Secure Coding Standard (2008).
CWE-747	CERT C Secure Coding Standard (2008) Chapter 14 - Miscellaneous (MSC)	Weaknesses in this category are related to the rules and recommendations in the Miscellaneous (MSC) chapter of the CERT C Secure Coding Standard (2008).
CWE-748	CERT C Secure Coding Standard (2008) Appendix - POSIX (POS)	Weaknesses in this category are related to the rules and recommendations in the POSIX (POS) appendix of the CERT C Secure Coding Standard (2008).
CWE-751	2009 Top 25 - Insecure Interaction Between Components	Weaknesses in this category are listed in the "Insecure Interaction Between Components" section of the 2009 CWE/SANS Top 25 Programming Errors.
CWE-752	2009 Top 25 - Risky Resource Management	Weaknesses in this category are listed in the "Risky Resource Management" section of the 2009 CWE/SANS Top 25 Programming Errors.
CWE-753	2009 Top 25 - Porous Defenses	Weaknesses in this category are listed in the "Porous Defenses" section of the 2009 CWE/SANS Top 25 Programming Errors.
CWE-801	2010 Top 25 - Insecure Interaction Between Components	Weaknesses in this category are listed in the "Insecure Interaction Between Components" section of the 2010 CWE/SANS Top 25 Programming Errors.
CWE-802	2010 Top 25 - Risky Resource Management	Weaknesses in this category are listed in the "Risky Resource Management" section of the 2010 CWE/SANS Top 25 Programming Errors.
CWE-803	2010 Top 25 - Porous Defenses	Weaknesses in this category are listed in the "Porous Defenses" section of the 2010 CWE/SANS Top 25 Programming Errors.
CWE-808	2010 Top 25 - Weaknesses On the Cusp	Weaknesses in this category are not part of the general Top 25, but they were part of the original nominee list from which the Top 25 was drawn.
CWE-810	OWASP Top Ten 2010 Category A1 - Injection	Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2010.
CWE-811	OWASP Top Ten 2010 Category A2 - Cross-Site Scripting (XSS)	Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2010.
CWE-812	OWASP Top Ten 2010 Category A3 - Broken Authentication and Session Management	Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2010.
CWE-813	OWASP Top Ten 2010 Category A4 - Insecure Direct Object References	Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2010.
CWE-814	OWASP Top Ten 2010 Category A5 - Cross-Site Request Forgery(CSRF)	Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2010.
CWE-815	OWASP Top Ten 2010 Category A6 - Security Misconfiguration	Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2010.
CWE-816	OWASP Top Ten 2010 Category A7 - Insecure Cryptographic Storage	Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2010.
CWE-817	OWASP Top Ten 2010 Category A8 - Failure to Restrict URL Access	Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2010.
CWE-818	OWASP Top Ten 2010 Category A9 - Insufficient Transport Layer Protection	Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2010.
CWE-819	OWASP Top Ten 2010 Category A10 - Unvalidated Redirects and Forwards	Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2010.
CWE-840	Business Logic Errors	Weaknesses in this category identify some of the underlying problems that commonly allow attackers to manipulate the business logic of an application. Errors in business logic can be devastating to an entire application. They can be difficult to find automatically, since they typically involve legitimate use of the application's functionality. However, many business logic errors can exhibit patterns that are similar to well-understood implementation and design weaknesses.
CWE-845	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 2 - Input Validation and Data Sanitization (IDS)	Weaknesses in this category are related to rules in the Input Validation and Data Sanitization (IDS) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-846	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 3 - Declarations and Initialization (DCL)	Weaknesses in this category are related to rules in the Declarations and Initialization (DCL) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-847	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 4 - Expressions (EXP)	Weaknesses in this category are related to rules in the Expressions (EXP) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-848	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 5 - Numeric Types and Operations (NUM)	Weaknesses in this category are related to rules in the Numeric Types and Operations (NUM) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-849	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 6 - Object Orientation (OBJ)	Weaknesses in this category are related to rules in the Object Orientation (OBJ) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-850	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 7 - Methods (MET)	Weaknesses in this category are related to rules in the Methods (MET) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-851	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 8 - Exceptional Behavior (ERR)	Weaknesses in this category are related to rules in the Exceptional Behavior (ERR) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-852	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 9 - Visibility and Atomicity (VNA)	Weaknesses in this category are related to rules in the Visibility and Atomicity (VNA) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-853	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 10 - Locking (LCK)	Weaknesses in this category are related to rules in the Locking (LCK) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-854	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 11 - Thread APIs (THI)	Weaknesses in this category are related to rules in the Thread APIs (THI) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-855	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 12 - Thread Pools (TPS)	Weaknesses in this category are related to rules in the Thread Pools (TPS) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-856	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 13 - Thread-Safety Miscellaneous (TSM)	Weaknesses in this category are related to rules in the Thread-Safety Miscellaneous (TSM) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-857	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 14 - Input Output (FIO)	Weaknesses in this category are related to rules in the Input Output (FIO) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-858	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 15 - Serialization (SER)	Weaknesses in this category are related to rules in the Serialization (SER) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-859	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 16 - Platform Security (SEC)	Weaknesses in this category are related to rules in the Platform Security (SEC) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-860	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 17 - Runtime Environment (ENV)	Weaknesses in this category are related to rules in the Runtime Environment (ENV) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-861	The CERT Oracle Secure Coding Standard for Java (2011) Chapter 18 - Miscellaneous (MSC)	Weaknesses in this category are related to rules in the Miscellaneous (MSC) chapter of The CERT Oracle Secure Coding Standard for Java (2011).
CWE-864	2011 Top 25 - Insecure Interaction Between Components	Weaknesses in this category are listed in the "Insecure Interaction Between Components" section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.
CWE-865	2011 Top 25 - Risky Resource Management	Weaknesses in this category are listed in the "Risky Resource Management" section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.
CWE-866	2011 Top 25 - Porous Defenses	Weaknesses in this category are listed in the "Porous Defenses" section of the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.
CWE-867	2011 Top 25 - Weaknesses On the Cusp	Weaknesses in this category are not part of the general Top 25, but they were part of the original nominee list from which the Top 25 was drawn.
CWE-869	CERT C++ Secure Coding Section 01 - Preprocessor (PRE)	Weaknesses in this category are related to rules in the Preprocessor (PRE) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-870	CERT C++ Secure Coding Section 02 - Declarations and Initialization (DCL)	Weaknesses in this category are related to rules in the Declarations and Initialization (DCL) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-871	CERT C++ Secure Coding Section 03 - Expressions (EXP)	Weaknesses in this category are related to rules in the Expressions (EXP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-872	CERT C++ Secure Coding Section 04 - Integers (INT)	Weaknesses in this category are related to rules in the Integers (INT) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-873	CERT C++ Secure Coding Section 05 - Floating Point Arithmetic (FLP)	Weaknesses in this category are related to rules in the Floating Point Arithmetic (FLP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-874	CERT C++ Secure Coding Section 06 - Arrays and the STL (ARR)	Weaknesses in this category are related to rules in the Arrays and the STL (ARR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-875	CERT C++ Secure Coding Section 07 - Characters and Strings (STR)	Weaknesses in this category are related to rules in the Characters and Strings (STR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-876	CERT C++ Secure Coding Section 08 - Memory Management (MEM)	Weaknesses in this category are related to rules in the Memory Management (MEM) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-877	CERT C++ Secure Coding Section 09 - Input Output (FIO)	Weaknesses in this category are related to rules in the Input Output (FIO) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-878	CERT C++ Secure Coding Section 10 - Environment (ENV)	Weaknesses in this category are related to rules in the Environment (ENV) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-879	CERT C++ Secure Coding Section 11 - Signals (SIG)	Weaknesses in this category are related to rules in the Signals (SIG) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-880	CERT C++ Secure Coding Section 12 - Exceptions and Error Handling (ERR)	Weaknesses in this category are related to rules in the Exceptions and Error Handling (ERR) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-881	CERT C++ Secure Coding Section 13 - Object Oriented Programming (OOP)	Weaknesses in this category are related to rules in the Object Oriented Programming (OOP) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-882	CERT C++ Secure Coding Section 14 - Concurrency (CON)	Weaknesses in this category are related to rules in the Concurrency (CON) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-883	CERT C++ Secure Coding Section 49 - Miscellaneous (MSC)	Weaknesses in this category are related to rules in the Miscellaneous (MSC) section of the CERT C++ Secure Coding Standard. Since not all rules map to specific weaknesses, this category may be incomplete.
CWE-885	SFP Primary Cluster: Risky Values	This category identifies Software Fault Patterns (SFPs) within the Risky Values cluster (SFP1).
CWE-886	SFP Primary Cluster: Unused entities	This category identifies Software Fault Patterns (SFPs) within the Unused entities cluster (SFP2).
CWE-887	SFP Primary Cluster: API	This category identifies Software Fault Patterns (SFPs) within the API cluster (SFP3).
CWE-889	SFP Primary Cluster: Exception Management	This category identifies Software Fault Patterns (SFPs) within the Exception Management cluster (SFP4, SFP5, SFP6).
CWE-890	SFP Primary Cluster: Memory Access	This category identifies Software Fault Patterns (SFPs) within the Memory Access cluster (SFP7, SFP8).
CWE-891	SFP Primary Cluster: Memory Management	This category identifies Software Fault Patterns (SFPs) within the Memory Management cluster (SFP38).
CWE-892	SFP Primary Cluster: Resource Management	This category identifies Software Fault Patterns (SFPs) within the Resource Management cluster (SFP37).
CWE-893	SFP Primary Cluster: Path Resolution	This category identifies Software Fault Patterns (SFPs) within the Path Resolution cluster (SFP16, SFP17, SFP18).
CWE-894	SFP Primary Cluster: Synchronization	This category identifies Software Fault Patterns (SFPs) within the Synchronization cluster (SFP19, SFP20, SFP21, SFP22).
CWE-895	SFP Primary Cluster: Information Leak	This category identifies Software Fault Patterns (SFPs) within the Information Leak cluster (SFP23).
CWE-896	SFP Primary Cluster: Tainted Input	This category identifies Software Fault Patterns (SFPs) within the Tainted Input cluster (SFP24, SFP25, SFP26, SFP27).
CWE-897	SFP Primary Cluster: Entry Points	This category identifies Software Fault Patterns (SFPs) within the Entry Points cluster (SFP28).
CWE-898	SFP Primary Cluster: Authentication	This category identifies Software Fault Patterns (SFPs) within the Authentication cluster (SFP29, SFP30, SFP31, SFP32, SFP33, SFP34).
CWE-899	SFP Primary Cluster: Access Control	This category identifies Software Fault Patterns (SFPs) within the Access Control cluster (SFP35).
CWE-901	SFP Primary Cluster: Privilege	This category identifies Software Fault Patterns (SFPs) within the Privilege cluster (SFP36).
CWE-902	SFP Primary Cluster: Channel	This category identifies Software Fault Patterns (SFPs) within the Channel cluster.
CWE-903	SFP Primary Cluster: Cryptography	This category identifies Software Fault Patterns (SFPs) within the Cryptography cluster.
CWE-904	SFP Primary Cluster: Malware	This category identifies Software Fault Patterns (SFPs) within the Malware cluster.
CWE-905	SFP Primary Cluster: Predictability	This category identifies Software Fault Patterns (SFPs) within the Predictability cluster.
CWE-906	SFP Primary Cluster: UI	This category identifies Software Fault Patterns (SFPs) within the UI cluster.
CWE-907	SFP Primary Cluster: Other	This category identifies Software Fault Patterns (SFPs) within the Other cluster.
CWE-929	OWASP Top Ten 2013 Category A1 - Injection	Weaknesses in this category are related to the A1 category in the OWASP Top Ten 2013.
CWE-930	OWASP Top Ten 2013 Category A2 - Broken Authentication and Session Management	Weaknesses in this category are related to the A2 category in the OWASP Top Ten 2013.
CWE-931	OWASP Top Ten 2013 Category A3 - Cross-Site Scripting (XSS)	Weaknesses in this category are related to the A3 category in the OWASP Top Ten 2013.
CWE-932	OWASP Top Ten 2013 Category A4 - Insecure Direct Object References	Weaknesses in this category are related to the A4 category in the OWASP Top Ten 2013.
CWE-933	OWASP Top Ten 2013 Category A5 - Security Misconfiguration	Weaknesses in this category are related to the A5 category in the OWASP Top Ten 2013.
CWE-934	OWASP Top Ten 2013 Category A6 - Sensitive Data Exposure	Weaknesses in this category are related to the A6 category in the OWASP Top Ten 2013.
CWE-935	OWASP Top Ten 2013 Category A7 - Missing Function Level Access Control	Weaknesses in this category are related to the A7 category in the OWASP Top Ten 2013.
CWE-936	OWASP Top Ten 2013 Category A8 - Cross-Site Request Forgery (CSRF)	Weaknesses in this category are related to the A8 category in the OWASP Top Ten 2013.
CWE-937	OWASP Top Ten 2013 Category A9 - Using Components with Known Vulnerabilities	Weaknesses in this category are related to the A9 category in the OWASP Top Ten 2013.
CWE-938	OWASP Top Ten 2013 Category A10 - Unvalidated Redirects and Forwards	Weaknesses in this category are related to the A10 category in the OWASP Top Ten 2013.
CWE-944	SFP Secondary Cluster: Access Management	This category identifies Software Fault Patterns (SFPs) within the Access Management cluster.
CWE-945	SFP Secondary Cluster: Insecure Resource Access	This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Access cluster (SFP35).
CWE-946	SFP Secondary Cluster: Insecure Resource Permissions	This category identifies Software Fault Patterns (SFPs) within the Insecure Resource Permissions cluster.
CWE-947	SFP Secondary Cluster: Authentication Bypass	This category identifies Software Fault Patterns (SFPs) within the Authentication Bypass cluster.
CWE-948	SFP Secondary Cluster: Digital Certificate	This category identifies Software Fault Patterns (SFPs) within the Digital Certificate cluster.
CWE-949	SFP Secondary Cluster: Faulty Endpoint Authentication	This category identifies Software Fault Patterns (SFPs) within the Faulty Endpoint Authentication cluster (SFP29).
CWE-950	SFP Secondary Cluster: Hardcoded Sensitive Data	This category identifies Software Fault Patterns (SFPs) within the Hardcoded Sensitive Data cluster (SFP33).
CWE-951	SFP Secondary Cluster: Insecure Authentication Policy	This category identifies Software Fault Patterns (SFPs) within the Insecure Authentication Policy cluster.
CWE-952	SFP Secondary Cluster: Missing Authentication	This category identifies Software Fault Patterns (SFPs) within the Missing Authentication cluster.
CWE-953	SFP Secondary Cluster: Missing Endpoint Authentication	This category identifies Software Fault Patterns (SFPs) within the Missing Endpoint Authentication cluster (SFP30).
CWE-954	SFP Secondary Cluster: Multiple Binds to the Same Port	This category identifies Software Fault Patterns (SFPs) within the Multiple Binds to the Same Port cluster (SFP32).
CWE-955	SFP Secondary Cluster: Unrestricted Authentication	This category identifies Software Fault Patterns (SFPs) within the Unrestricted Authentication cluster (SFP34).
CWE-956	SFP Secondary Cluster: Channel Attack	This category identifies Software Fault Patterns (SFPs) within the Channel Attack cluster.
CWE-957	SFP Secondary Cluster: Protocol Error	This category identifies Software Fault Patterns (SFPs) within the Protocol Error cluster.
CWE-958	SFP Secondary Cluster: Broken Cryptography	This category identifies Software Fault Patterns (SFPs) within the Broken Cryptography cluster.
CWE-959	SFP Secondary Cluster: Weak Cryptography	This category identifies Software Fault Patterns (SFPs) within the Weak Cryptography cluster.
CWE-960	SFP Secondary Cluster: Ambiguous Exception Type	This category identifies Software Fault Patterns (SFPs) within the Ambiguous Exception Type cluster (SFP5).
CWE-961	SFP Secondary Cluster: Incorrect Exception Behavior	This category identifies Software Fault Patterns (SFPs) within the Incorrect Exception Behavior cluster (SFP6).
CWE-962	SFP Secondary Cluster: Unchecked Status Condition	This category identifies Software Fault Patterns (SFPs) within the Unchecked Status Condition cluster (SFP4).
CWE-963	SFP Secondary Cluster: Exposed Data	This category identifies Software Fault Patterns (SFPs) within the Exposed Data cluster (SFP23).
CWE-964	SFP Secondary Cluster: Exposure Temporary File	This category identifies Software Fault Patterns (SFPs) within the Exposure Temporary File cluster.
CWE-965	SFP Secondary Cluster: Insecure Session Management	This category identifies Software Fault Patterns (SFPs) within the Insecure Session Management cluster.
CWE-966	SFP Secondary Cluster: Other Exposures	This category identifies Software Fault Patterns (SFPs) within the Other Exposures cluster.
CWE-967	SFP Secondary Cluster: State Disclosure	This category identifies Software Fault Patterns (SFPs) within the State Disclosure cluster.
CWE-968	SFP Secondary Cluster: Covert Channel	This category identifies Software Fault Patterns (SFPs) within the Covert Channel cluster.
CWE-969	SFP Secondary Cluster: Faulty Memory Release	This category identifies Software Fault Patterns (SFPs) within the Faulty Memory Release cluster (SFP12).
CWE-970	SFP Secondary Cluster: Faulty Buffer Access	This category identifies Software Fault Patterns (SFPs) within the Faulty Buffer Access cluster (SFP8).
CWE-971	SFP Secondary Cluster: Faulty Pointer Use	This category identifies Software Fault Patterns (SFPs) within the Faulty Pointer Use cluster (SFP7).
CWE-972	SFP Secondary Cluster: Faulty String Expansion	This category identifies Software Fault Patterns (SFPs) within the Faulty String Expansion cluster (SFP9).
CWE-973	SFP Secondary Cluster: Improper NULL Termination	This category identifies Software Fault Patterns (SFPs) within the Improper NULL Termination cluster (SFP11).
CWE-974	SFP Secondary Cluster: Incorrect Buffer Length Computation	This category identifies Software Fault Patterns (SFPs) within the Incorrect Buffer Length Computation cluster (SFP10).
CWE-975	SFP Secondary Cluster: Architecture	This category identifies Software Fault Patterns (SFPs) within the Architecture cluster.
CWE-976	SFP Secondary Cluster: Compiler	This category identifies Software Fault Patterns (SFPs) within the Compiler cluster.
CWE-977	SFP Secondary Cluster: Design	This category identifies Software Fault Patterns (SFPs) within the Design cluster.
CWE-978	SFP Secondary Cluster: Implementation	This category identifies Software Fault Patterns (SFPs) within the Implementation cluster.
CWE-979	SFP Secondary Cluster: Failed Chroot Jail	This category identifies Software Fault Patterns (SFPs) within the Failed Chroot Jail cluster (SFP17).
CWE-980	SFP Secondary Cluster: Link in Resource Name Resolution	This category identifies Software Fault Patterns (SFPs) within the Link in Resource Name Resolution cluster (SFP18).
CWE-981	SFP Secondary Cluster: Path Traversal	This category identifies Software Fault Patterns (SFPs) within the Path Traversal cluster (SFP16).
CWE-982	SFP Secondary Cluster: Failure to Release Resource	This category identifies Software Fault Patterns (SFPs) within the Failure to Release Resource cluster (SFP14).
CWE-983	SFP Secondary Cluster: Faulty Resource Use	This category identifies Software Fault Patterns (SFPs) within the Faulty Resource Use cluster (SFP15).
CWE-984	SFP Secondary Cluster: Life Cycle	This category identifies Software Fault Patterns (SFPs) within the Life Cycle cluster.
CWE-985	SFP Secondary Cluster: Unrestricted Consumption	This category identifies Software Fault Patterns (SFPs) within the Unrestricted Consumption cluster (SFP13).
CWE-986	SFP Secondary Cluster: Missing Lock	This category identifies Software Fault Patterns (SFPs) within the Missing Lock cluster (SFP19).
CWE-987	SFP Secondary Cluster: Multiple Locks/Unlocks	This category identifies Software Fault Patterns (SFPs) within the Multiple Locks/Unlocks cluster (SFP21).
CWE-988	SFP Secondary Cluster: Race Condition Window	This category identifies Software Fault Patterns (SFPs) within the Race Condition Window cluster (SFP20).
CWE-989	SFP Secondary Cluster: Unrestricted Lock	This category identifies Software Fault Patterns (SFPs) within the Unrestricted Lock cluster (SFP22).
CWE-990	SFP Secondary Cluster: Tainted Input to Command	This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Command cluster (SFP24).
CWE-991	SFP Secondary Cluster: Tainted Input to Environment	This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Environment cluster (SFP27).
CWE-992	SFP Secondary Cluster: Faulty Input Transformation	This category identifies Software Fault Patterns (SFPs) within the Faulty Input Transformation cluster.
CWE-993	SFP Secondary Cluster: Incorrect Input Handling	This category identifies Software Fault Patterns (SFPs) within the Incorrect Input Handling cluster.
CWE-994	SFP Secondary Cluster: Tainted Input to Variable	This category identifies Software Fault Patterns (SFPs) within the Tainted Input to Variable cluster (SFP25).
CWE-995	SFP Secondary Cluster: Feature	This category identifies Software Fault Patterns (SFPs) within the Feature cluster.
CWE-996	SFP Secondary Cluster: Security	This category identifies Software Fault Patterns (SFPs) within the Security cluster.
CWE-997	SFP Secondary Cluster: Information Loss	This category identifies Software Fault Patterns (SFPs) within the Information Loss cluster.
CWE-998	SFP Secondary Cluster: Glitch in Computation	This category identifies Software Fault Patterns (SFPs) within the Glitch in Computation cluster (SFP1).
CWE-1000	Research Concepts	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.
CWE-1003	Weaknesses for Simplified Mapping of Published Vulnerabilities	CWE entries in this view (graph) may be used to categorize potential weaknesses within sources that handle public, third-party vulnerability information, such as the National Vulnerability Database (NVD). By design, this view is incomplete. It is limited to a small number of the most commonly-seen weaknesses, so that it is easier for humans to use. This view uses a shallow hierarchy of two levels in order to simplify the complex navigation of the entire CWE corpus.
CWE-1008	Architectural Concepts	This view organizes weaknesses according to common architectural security tactics. It is intended to assist architects in identifying potential mistakes that can be made when designing software.
CWE-1026	Weaknesses in OWASP Top Ten (2017)	CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2017.
CWE-1040	Quality Weaknesses with Indirect Security Impacts	CWE identifiers in this view (slice) are quality issues that only indirectly make it easier to introduce a vulnerability and/or make the vulnerability more difficult to detect or mitigate.
CWE-1081	Entries with Maintenance Notes	CWE entries in this view have maintenance notes. Maintenance notes are an indicator that an entry might change significantly in future versions. This view was created due to feedback from the CWE Board and participants in the CWE Compatibility Summit in March 2021.
CWE-1128	CISQ Quality Measures (2016)	This view outlines the most important software quality issues as identified by the Consortium for Information & Software Quality (CISQ) Automated Quality Characteristic Measures, released in 2016. These measures are derived from Object Management Group (OMG) standards.
CWE-1133	Weaknesses Addressed by the SEI CERT Oracle Coding Standard for Java	CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the online wiki that reflects that current rules and recommendations of the SEI CERT Oracle Coding Standard for Java.
CWE-1154	Weaknesses Addressed by the SEI CERT C Coding Standard	CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the online wiki that reflects that current rules and recommendations of the SEI CERT C Coding Standard.
CWE-1178	Weaknesses Addressed by the SEI CERT Perl Coding Standard	CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the online wiki that reflects that current rules and recommendations of the SEI CERT Perl Coding Standard.
CWE-1194	Hardware Design	This view organizes weaknesses around concepts that are frequently used or encountered in hardware design. Accordingly, this view can align closely with the perspectives of designers, manufacturers, educators, and assessment vendors. It provides a variety of categories that are intended to simplify navigation, browsing, and mapping.
CWE-1200	Weaknesses in the 2019 CWE Top 25 Most Dangerous Software Errors	CWE entries in this view are listed in the 2019 CWE Top 25 Most Dangerous Software Errors.
CWE-1305	CISQ Quality Measures (2020)	This view outlines the most important software quality issues as identified by the Consortium for Information & Software Quality (CISQ) Automated Quality Characteristic Measures, released in 2020. These measures are derived from Object Management Group (OMG) standards.
CWE-1337	Weaknesses in the 2021 CWE Top 25 Most Dangerous Software Weaknesses	CWE entries in this view are listed in the 2021 CWE Top 25 Most Dangerous Software Weaknesses.
CWE-1340	CISQ Data Protection Measures	This view outlines the SMM representation of the Automated Source Code Data Protection Measurement specifications, as identified by the Consortium for Information & Software Quality (CISQ) Working Group.
CWE-1343	Weaknesses in the 2021 CWE Most Important Hardware Weaknesses List	CWE entries in this view are listed in the 2021 CWE Most Important Hardware Weaknesses List, as determined by the Hardware CWE Special Interest Group (HW CWE SIG).
CWE-1344	Weaknesses in OWASP Top Ten (2021)	CWE entries in this view (graph) are associated with the OWASP Top Ten, as released in 2021.
CWE-1350	Weaknesses in the 2020 CWE Top 25 Most Dangerous Software Weaknesses	CWE entries in this view are listed in the 2020 CWE Top 25 Most Dangerous Software Weaknesses.
CWE-1358	Weaknesses in SEI ETF Categories of Security Vulnerabilities in ICS	CWE entries in this view (graph) are associated with the Categories of Security Vulnerabilities in ICS, as published by the Securing Energy Infrastructure Executive Task Force (SEI ETF) in March 2022. Weaknesses and categories in this view are focused on issues that affect ICS (Industrial Control Systems) but have not been traditionally covered by CWE in the past due to its earlier emphasis on enterprise IT software. Note: weaknesses in this view are based on "Nearest IT Neighbor" recommendations and other suggestions by the CWE team. These relationships are likely to change in future CWE versions.
CWE-1387	Weaknesses in the 2022 CWE Top 25 Most Dangerous Software Weaknesses	CWE entries in this view are listed in the 2022 CWE Top 25 Most Dangerous Software Weaknesses.
CWE-1400	Comprehensive Categorization for Software Assurance Trends
CWE-1424	Weaknesses Addressed by ISA/IEC 62443 Requirements	This view (slice) covers weaknesses that are addressed by following requirements in the ISA/IEC 62443 series of standards for industrial automation and control systems (IACS). Members of the CWE ICS/OT SIG analyzed a set of CWEs and mapped them to specific requirements covered by ISA/IEC 62443. These mappings are recorded in Taxonomy_Mapping elements.
CWE-1425	Weaknesses in the 2023 CWE Top 25 Most Dangerous Software Weaknesses	CWE entries in this view are listed in the 2023 CWE Top 25 Most Dangerous Software Weaknesses.
CWE-1430	Weaknesses in the 2024 CWE Top 25 Most Dangerous Software Weaknesses	CWE entries in this view are listed in the 2024 CWE Top 25 Most Dangerous Software Weaknesses.
CWE-1432	Weaknesses in the 2025 CWE Most Important Hardware Weaknesses List	CWE entries in this view are listed in the 2025 CWE Most Important Hardware Weaknesses List, as determined by the Hardware CWE Special Interest Group (HW CWE SIG). The 2025 MIHW aims to drive awareness of critical hardware weaknesses and provide the cybersecurity community with practical guidance to prevent security issues at the source. By combining advanced data analysis with expert consensus, the list helps organizations prioritize mitigations, strengthen design practices, and make informed decisions throughout the hardware lifecycle.
CWE-2000	Comprehensive CWE Dictionary	This view (slice) covers all the elements in CWE.
CWE-604	Deprecated Entries	CWE nodes in this view (slice) have been deprecated. There should be a reference pointing to the replacement in each deprecated weakness.
CWE-629	Weaknesses in OWASP Top Ten (2007)	CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2007. This view is considered obsolete as a newer version of the OWASP Top Ten is available.
CWE-630	DEPRECATED: Weaknesses Examined by SAMATE	This view has been deprecated. It was only used for an early year of the NIST SAMATE project, and it did not represent any official or commonly-utilized list.
CWE-631	DEPRECATED: Resource-specific Weaknesses	This view has been deprecated because it is not actively maintained and does not provide utility to stakeholders. It was originally created before CWE 1.0 as a simple example of how views could be structured within CWE.
CWE-635	Weaknesses Originally Used by NVD from 2008 to 2016	CWE nodes in this view (slice) were used by NIST to categorize vulnerabilities within NVD, from 2008 to 2016. This original version has been used by many other projects.
CWE-658	Weaknesses in Software Written in C	This view (slice) covers issues that are found in C programs that are not common to all languages.
CWE-659	Weaknesses in Software Written in C++	This view (slice) covers issues that are found in C++ programs that are not common to all languages.
CWE-660	Weaknesses in Software Written in Java	This view (slice) covers issues that are found in Java programs that are not common to all languages.
CWE-661	Weaknesses in Software Written in PHP	This view (slice) covers issues that are found in PHP programs that are not common to all languages.
CWE-677	Weakness Base Elements	This view (slice) displays only weakness base elements.
CWE-678	Composites	This view displays only composite weaknesses.
CWE-679	DEPRECATED: Chain Elements	This view has been deprecated. It has limited utility for stakeholders, since all weaknesses can be links in a chain.
CWE-699	Software Development	This view organizes weaknesses around concepts that are frequently used or encountered in software development. This includes all aspects of the software development lifecycle including both architecture and implementation. Accordingly, this view can align closely with the perspectives of architects, developers, educators, and assessment vendors. It provides a variety of categories that are intended to simplify navigation, browsing, and mapping.
CWE-700	Seven Pernicious Kingdoms	This view (graph) organizes weaknesses using a hierarchical structure that is similar to that used by Seven Pernicious Kingdoms.
CWE-701	Weaknesses Introduced During Design	This view (slice) lists weaknesses that can be introduced during design.
CWE-702	Weaknesses Introduced During Implementation	This view (slice) lists weaknesses that can be introduced during implementation.
CWE-709	Named Chains	This view displays Named Chains and their components.
CWE-711	Weaknesses in OWASP Top Ten (2004)	CWE entries in this view (graph) are associated with the OWASP Top Ten, as released in 2004, and as required for compliance with PCI DSS version 1.1. This view is considered obsolete as a newer version of the OWASP Top Ten is available.
CWE-734	Weaknesses Addressed by the CERT C Secure Coding Standard (2008)	CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the book "The CERT C Secure Coding Standard" published in 2008. This view is considered obsolete, as a newer version of the coding standard is available. This view statically represents the coding rules as they were in 2008.
CWE-750	Weaknesses in the 2009 CWE/SANS Top 25 Most Dangerous Programming Errors	CWE entries in this view (graph) are listed in the 2009 CWE/SANS Top 25 Programming Errors. This view is considered obsolete as a newer version of the Top 25 is available.
CWE-800	Weaknesses in the 2010 CWE/SANS Top 25 Most Dangerous Programming Errors	CWE entries in this view (graph) are listed in the 2010 CWE/SANS Top 25 Programming Errors. This view is considered obsolete as a newer version of the Top 25 is available.
CWE-809	Weaknesses in OWASP Top Ten (2010)	CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2010. This view is considered obsolete as a newer version of the OWASP Top Ten is available.
CWE-844	Weaknesses Addressed by The CERT Oracle Secure Coding Standard for Java (2011)	CWE entries in this view (graph) are fully or partially eliminated by following the guidance presented in the book "The CERT Oracle Secure Coding Standard for Java" published in 2011. This view is considered obsolete as a newer version of the coding standard is available.
CWE-868	Weaknesses Addressed by the SEI CERT C++ Coding Standard (2016 Version)	CWE entries in this view (graph) are fully or partially eliminated by following the SEI CERT C++ Coding Standard, as published in 2016. This view is no longer being actively maintained, since it statically represents the coding rules as they were in 2016.
CWE-884	CWE Cross-section	This view contains a selection of weaknesses that represent the variety of weaknesses that are captured in CWE, at a level of abstraction that is likely to be useful to most audiences. It can be used by researchers to determine how broad their theories, models, or tools are. It will also be used by the CWE content team in 2012 to focus quality improvement efforts for individual CWE entries.
CWE-888	Software Fault Pattern (SFP) Clusters	CWE identifiers in this view are associated with clusters of Software Fault Patterns (SFPs).
CWE-900	Weaknesses in the 2011 CWE/SANS Top 25 Most Dangerous Software Errors	CWE entries in this view (graph) are listed in the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.
CWE-919	Weaknesses in Mobile Applications	CWE entries in this view (slice) are often seen in mobile applications.
CWE-928	Weaknesses in OWASP Top Ten (2013)	CWE nodes in this view (graph) are associated with the OWASP Top Ten, as released in 2013. This view is considered obsolete as a newer version of the OWASP Top Ten is available.
CWE-999	DEPRECATED: Weaknesses without Software Fault Patterns	This view has been deprecated. It was based on gaps in another view (CWE-888) related to research that is no longer updated, but was complete with respect to CWE at the time it was conducted.

Mapping Notes

Usage: Prohibited

Reasons: View

Rationale:

This entry is a View. Views are not weaknesses and therefore inappropriate to describe the root causes of vulnerabilities.

Comment:

Use this View or other Views to search and navigate for the appropriate weakness.