Vulnerability Database
Every documented weakness class (CWE), sorted by CWE number.
- CWE-1117: Callable with Insufficient Behavioral SummaryCallable with Insufficient Behavioral Summary occurs when code contains a function or method whose signature and/or associated inline documentation
- CWE-1118: Insufficient Documentation of Error Handling TechniquesInsufficient Documentation of Error Handling Techniques occurs when the documentation for a software product does not sufficiently describe the
- CWE-1119: Excessive Use of Unconditional BranchingExcessive Use of Unconditional Branching occurs when code uses too many unconditional branches such as 'goto' statements, unrestricted jumps, or
- CWE-1120: Excessive Code ComplexityExcessive Code Complexity occurs when code is too complex as calculated using well-defined, quantitative measures such as cyclomatic complexity,
- CWE-1121: Excessive McCabe Cyclomatic ComplexityExcessive McCabe Cyclomatic Complexity occurs when code contains McCabe cyclomatic complexity that exceeds a desirable maximum threshold.
- CWE-1122: Excessive Halstead ComplexityExcessive Halstead Complexity occurs when code is structured in a way that Halstead complexity measures exceed desirable maximums.
- CWE-1123: Excessive Use of Self-Modifying CodeExcessive Use of Self-Modifying Code occurs when a product uses too much self-modifying code, which is code that changes its own instructions during
- CWE-1124: Excessively Deep NestingExcessively Deep Nesting occurs when code contains a callable or other code grouping in which the nesting (branching depth) is too deep.
- CWE-1125: Excessive Attack SurfaceExcessive Attack Surface occurs when a product has an attack surface whose quantitative measurement exceeds a desirable maximum.
- CWE-1126: Declaration of Variable with Unnecessarily Wide ScopeDeclaration of Variable with Unnecessarily Wide Scope occurs when source code declares a variable in one scope (such as a class or function), but the
- CWE-1127: Compilation with Insufficient Warnings or ErrorsCompilation with Insufficient Warnings or Errors occurs when code is compiled without sufficient warnings enabled, which may prevent the detection of
- CWE-1164: Irrelevant CodeIrrelevant Code occurs when a product contains code that is not needed - it makes no state changes and has no side effects that alter data or control
- CWE-1173: Improper Use of Validation FrameworkImproper Use of Validation Framework occurs when a product does not use, or incorrectly uses, an input validation framework that is provided by the
- CWE-1174: ASP.NET Misconfiguration: Improper Model ValidationASP.NET Misconfiguration: Improper Model Validation occurs when an ASP.NET application does not use, or incorrectly uses, the model validation
- CWE-1176: Inefficient CPU ComputationInefficient CPU Computation occurs when a product performs CPU computations using algorithms that are not as efficient as they could be for the needs
- CWE-1177: Use of Prohibited CodeUse of Prohibited Code occurs when a product uses a function, library, or third-party component that has been explicitly prohibited, whether by the
- CWE-1188: Initialization of a Resource with an Insecure DefaultInitialization of a Resource with an Insecure Default occurs when a product initializes or sets a resource with a default value that is intended to
- CWE-1190: DMA Device Enabled Too Early in Boot PhaseDMA Device Enabled Too Early in Boot Phase occurs when a product enables a Direct Memory Access (DMA) capable device before the security
- CWE-1191: On-Chip Debug and Test Interface With Improper Access ControlOn-Chip Debug and Test Interface With Improper Access Control occurs when a chip lacks proper access control mechanisms to verify user authorization
- CWE-1192: System-on-Chip (SoC) Using Components without Unique IdentifiersSystem-on-Chip (SoC) Using Components without Unique Identifiers occurs when a System-on-Chip does not have unique, immutable identifiers for each of
- CWE-1209: Failure to Disable Reserved BitsFailure to Disable Reserved Bits occurs when reserved bits in hardware designs are not disabled before production release.
- CWE-1220: Insufficient Granularity of Access ControlInsufficient Granularity of Access Control occurs when the product's protection mechanism does not account for granularity at the bit level, which
- CWE-1221: Incorrect Register Defaults or Module ParametersIncorrect Register Defaults or Module Parameters occurs when hardware design parameters or register default values are incorrectly set during design.
- CWE-1222: Insufficient Granularity of Address Regions Protected by Register LocksInsufficient Granularity of Address Regions Protected by Register Locks occurs when a hardware design protects address regions using register locks
- CWE-1223: Race Condition for Write-Once AttributesRace Condition for Write-Once Attributes occurs when a hardware design contains write-once registers or other elements that can be modified by both
- CWE-1224: Improper Restriction of Write-Once Bit FieldsImproper Restriction of Write-Once Bit Fields occurs when hardware design control register "sticky bits" or write-once bit fields are improperly
- CWE-1229: Creation of Emergent ResourceCreation of Emergent Resource occurs when a product manages resources or behaves in a way that indirectly creates a new, distinct resource that can
- CWE-1230: Exposure of Sensitive Information Through MetadataExposure of Sensitive Information Through Metadata occurs when a product prevents direct access to a resource containing sensitive information, but
- CWE-1231: Improper Prevention of Lock Bit ModificationImproper Prevention of Lock Bit Modification occurs when a system employs a trusted lock bit to restrict access to registers or resources, but fails
- CWE-1232: Improper Lock Behavior After Power State TransitionImproper Lock Behavior After Power State Transition occurs when register lock bit protection disables changes to system configuration once the bit is
- CWE-1233: Security-Sensitive Hardware Controls with Missing Lock Bit ProtectionSecurity-Sensitive Hardware Controls with Missing Lock Bit Protection occurs when a product implements register lock bit protection but fails to
- CWE-1234: Hardware Internal or Debug Modes Allow Override of LocksHardware Internal or Debug Modes Allow Override of Locks occurs when system configuration protection can be bypassed during debug mode or other
- CWE-1235: Incorrect Use of Autoboxing and Unboxing for Performance Critical OperationsIncorrect Use of Autoboxing and Unboxing for Performance Critical Operations occurs when code uses boxed primitives, which may introduce
- CWE-1239: Improper Zeroization of Hardware RegisterImproper Zeroization of Hardware Register occurs when a hardware product does not properly clear sensitive information from built-in registers when
- CWE-1240: Use of a Cryptographic Primitive with a Risky ImplementationUse of a Cryptographic Primitive with a Risky Implementation occurs when a product implements a cryptographic algorithm using a non-standard,
- CWE-1241: Use of Predictable Algorithm in Random Number GeneratorUse of Predictable Algorithm in Random Number Generator occurs when a device employs an algorithm that generates pseudo-random numbers in a
- CWE-1242: Inclusion of Undocumented Features or Chicken BitsInclusion of Undocumented Features or Chicken Bits occurs when a device includes chicken bits or undocumented features that can create entry points
- CWE-1243: Sensitive Non-Volatile Information Not Protected During DebugSensitive Non-Volatile Information Not Protected During Debug occurs when access to security-sensitive information stored in fuses is not limited
- CWE-1244: Internal Asset Exposed to Unsafe Debug Access Level or StateInternal Asset Exposed to Unsafe Debug Access Level or State occurs when a product uses physical debug or test interfaces with multiple access levels
- CWE-1245: Improper Finite State Machines (FSMs) in Hardware LogicImproper Finite State Machines (FSMs) in Hardware Logic occurs when faulty finite state machines in the hardware logic allow an attacker to put the
- CWE-1246: Improper Write Handling in Limited-write Non-Volatile MemoriesImproper Write Handling in Limited-write Non-Volatile Memories occurs when a product does not implement or incorrectly implements wear leveling
- CWE-1247: Improper Protection Against Voltage and Clock GlitchesImproper Protection Against Voltage and Clock Glitches occurs when a device lacks appropriate circuitry or sensors to detect and mitigate voltage and
- CWE-1248: Semiconductor Defects in Hardware Logic with Security-Sensitive ImplicationsSemiconductor Defects in Hardware Logic with Security-Sensitive Implications occurs when security-sensitive hardware modules contain semiconductor
- CWE-1249: Application-Level Admin Tool with Inconsistent View of Underlying Operating SystemApplication-Level Admin Tool with Inconsistent View of Underlying Operating System occurs when an administrative application fails to accurately
- CWE-1250: Improper Preservation of Consistency Between Independent Representations of Shared StateImproper Preservation of Consistency Between Independent Representations of Shared State occurs when a product maintains multiple distributed
- CWE-1251: Mirrored Regions with Different ValuesMirrored Regions with Different Values occurs when a product's architecture duplicates regions (such as cache memory or shadow copies of registers)
- CWE-1252: CPU Hardware Not Configured to Support Exclusivity of Write and Execute OperationsCPU Hardware Not Configured to Support Exclusivity of Write and Execute Operations occurs when the CPU lacks hardware support or has disabled
- CWE-1253: Incorrect Selection of Fuse ValuesIncorrect Selection of Fuse Values occurs when a product relies on an unblown fuse to establish a secure system state.
- CWE-1254: Incorrect Comparison Logic GranularityIncorrect Comparison Logic Granularity occurs when a product performs comparison operations across multiple steps rather than as a single unified
- CWE-1255: Comparison Logic is Vulnerable to Power Side-Channel AttacksComparison Logic is Vulnerable to Power Side-Channel Attacks occurs when a device's power consumption during security token evaluation can be
- CWE-1256: Improper Restriction of Software Interfaces to Hardware FeaturesImproper Restriction of Software Interfaces to Hardware Features occurs when a product allows software control over device functionality like power
- CWE-1257: Improper Access Control Applied to Mirrored or Aliased Memory RegionsImproper Access Control Applied to Mirrored or Aliased Memory Regions occurs when a product has inconsistent read/write permissions across aliased or
- CWE-1258: Exposure of Sensitive System Information Due to Uncleared Debug InformationExposure of Sensitive System Information Due to Uncleared Debug Information occurs when hardware fails to fully clear security-sensitive values—such
- CWE-1259: Improper Restriction of Security Token AssignmentImproper Restriction of Security Token Assignment occurs when Systems-on-Chip use security tokens to differentiate which actions are permitted from
- CWE-1260: Improper Handling of Overlap Between Protected Memory RangesImproper Handling of Overlap Between Protected Memory Ranges occurs when a product allows address regions to overlap, which can result in the
- CWE-1261: Improper Handling of Single Event UpsetsImproper Handling of Single Event Upsets occurs when hardware logic does not effectively handle when single-event upsets (SEUs) occur.
- CWE-1262: Improper Access Control for Register InterfaceImproper Access Control for Register Interface occurs when a product uses memory-mapped I/O registers providing hardware access from software but
- CWE-1263: Improper Physical Access ControlImproper Physical Access Control occurs when a product restricts access to certain information but does not sufficiently protect against an
- CWE-1264: Hardware Logic with Insecure De-Synchronization between Control and Data ChannelsHardware Logic with Insecure De-Synchronization between Control and Data Channels occurs when hardware error handling and security check logic allow
- CWE-1265: Unintended Reentrant Invocation of Non-reentrant Code Via Nested CallsUnintended Reentrant Invocation of Non-reentrant Code Via Nested Calls occurs when a product invokes code assumed to be reentrant, but nested
- CWE-1266: Improper Scrubbing of Sensitive Data from Decommissioned DeviceImproper Scrubbing of Sensitive Data from Decommissioned Device occurs when a product lacks adequate capability for administrators to remove
- CWE-1267: Policy Uses Obsolete EncodingPolicy Uses Obsolete Encoding occurs when a product implements access controls using an encoding mechanism that is no longer trusted or appropriate
- CWE-1268: Policy Privileges are not Assigned Consistently Between Control and Data AgentsPolicy Privileges are not Assigned Consistently Between Control and Data Agents occurs when hardware-enforced access control fails to properly
- CWE-1269: Product Released in Non-Release ConfigurationProduct Released in Non-Release Configuration occurs when a product reaches market in a pre-production or manufacturing configuration rather than a
- CWE-1270: Generation of Incorrect Security TokensGeneration of Incorrect Security Tokens occurs when a system implements security tokens to differentiate allowed and disallowed actions but generates
- CWE-1271: Uninitialized Value on Reset for Registers Holding Security SettingsUninitialized Value on Reset for Registers Holding Security Settings occurs when security-critical logic is not set to a known value upon system reset.
- CWE-1272: Sensitive Information Uncleared Before Debug/Power State TransitionSensitive Information Uncleared Before Debug/Power State Transition occurs when a product fails to clear sensitive information during power or debug
- CWE-1273: Device Unlock Credential SharingDevice Unlock Credential Sharing occurs when the credentials necessary for unlocking a device are shared across multiple parties and may expose
- CWE-1274: Improper Access Control for Volatile Memory Containing Boot CodeImproper Access Control for Volatile Memory Containing Boot Code occurs when a secure-boot process transfers bootloader code from Non-Volatile Memory
- CWE-1275: Sensitive Cookie with Improper SameSite AttributeSensitive Cookie with Improper SameSite Attribute occurs when the SameSite attribute for sensitive cookies is not set, or an insecure value is used.
- CWE-1276: Hardware Child Block Incorrectly Connected to Parent SystemHardware Child Block Incorrectly Connected to Parent System occurs when signals between a hardware IP component and the parent system design are
- CWE-1277: Firmware Not UpdateableFirmware Not Updateable occurs when a product lacks the ability to update or patch firmware to address vulnerabilities or weaknesses.
- CWE-1278: Missing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging TechniquesMissing Protection Against Hardware Reverse Engineering Using Integrated Circuit (IC) Imaging Techniques occurs when information stored in hardware
- CWE-1279: Cryptographic Operations are run Before Supporting Units are ReadyCryptographic Operations are run Before Supporting Units are Ready occurs when performing cryptographic operations without ensuring that the
- CWE-1280: Access Control Check Implemented After Asset is AccessedAccess Control Check Implemented After Asset is Accessed occurs when a product's hardware-based access control check happens after the asset has
- CWE-1281: Sequence of Processor Instructions Leads to Unexpected BehaviorSequence of Processor Instructions Leads to Unexpected Behavior occurs when specific combinations of processor instructions lead to undesirable
- CWE-1282: Assumed-Immutable Data is Stored in Writable MemoryAssumed-Immutable Data is Stored in Writable Memory occurs when security-critical assets like bootloaders, device identifiers, and configuration
- CWE-1283: Mutable Attestation or Measurement Reporting DataMutable Attestation or Measurement Reporting Data occurs when attestation or measurement registers used in secure boot processes can be modified by
- CWE-1284: Improper Validation of Specified Quantity in InputImproper Validation of Specified Quantity in Input occurs when a product receives input specifying a quantity (size, length, frequency, price, rate,
- CWE-1285: Improper Validation of Specified Index, Position, or Offset in InputImproper Validation of Specified Index, Position, or Offset in Input occurs when a product fails to properly validate indices, positions, or offsets
- CWE-1286: Improper Validation of Syntactic Correctness of InputImproper Validation of Syntactic Correctness of Input occurs when a product receives input expected to follow specific syntax but fails to validate
- CWE-1287: Improper Validation of Specified Type of InputImproper Validation of Specified Type of Input occurs when a product receives input expected to be a specific type but fails to validate or
- CWE-1288: Improper Validation of Consistency within InputImproper Validation of Consistency within Input occurs when a product receives inputs with multiple elements or fields that should align with each
- CWE-1289: Improper Validation of Unsafe Equivalence in InputImproper Validation of Unsafe Equivalence in Input occurs when a product accepts an input used as a resource identifier but fails to validate that
- CWE-1290: Incorrect Decoding of Security IdentifiersIncorrect Decoding of Security Identifiers occurs when a product implements a decoding mechanism to decode bus-transaction signals to security
- CWE-1291: Public Key Re-Use for Signing both Debug and Production CodePublic Key Re-Use for Signing both Debug and Production Code occurs when a single public key is employed to authenticate both debug and production
- CWE-1292: Incorrect Conversion of Security IdentifiersIncorrect Conversion of Security Identifiers occurs when a product's bus-transaction signal to security identifier mapping contains conversion
- CWE-1293: Missing Source Correlation of Multiple Independent DataMissing Source Correlation of Multiple Independent Data occurs when a product relies on a single source of data, preventing the ability to detect if
- CWE-1294: Insecure Security Identifier MechanismInsecure Security Identifier Mechanism occurs when a System-on-Chip (SoC) implements a Security Identifier mechanism to differentiate what actions
- CWE-1295: Debug Messages Revealing Unnecessary InformationDebug Messages Revealing Unnecessary Information occurs when a product fails to adequately prevent the revealing of unnecessary and potentially
- CWE-1296: Incorrect Chaining or Granularity of Debug ComponentsIncorrect Chaining or Granularity of Debug Components occurs when a product's debug components contain incorrect chaining or granularity
- CWE-1297: Unprotected Confidential Information on Device is Accessible by OSAT VendorsUnprotected Confidential Information on Device is Accessible by OSAT Vendors occurs when a product fails to adequately protect confidential
- CWE-1298: Hardware Logic Contains Race ConditionsHardware Logic Contains Race Conditions occurs when a race condition in the hardware logic results in undermining security guarantees of the system.
- CWE-1299: Missing Protection Mechanism for Alternate Hardware InterfaceMissing Protection Mechanism for Alternate Hardware Interface occurs when assets lack protections across all access paths.
- CWE-1300: Improper Protection of Physical Side ChannelsImproper Protection of Physical Side Channels occurs when a device lacks adequate protection mechanisms to prevent physical side channels from
- CWE-1301: Insufficient or Incomplete Data Removal within Hardware ComponentInsufficient or Incomplete Data Removal within Hardware Component occurs when a product's data removal process fails to completely eliminate all
- CWE-1302: Missing Source Identifier in Entity Transactions on a System-On-Chip (SOC)Missing Source Identifier in Entity Transactions on a System-On-Chip occurs when a product implements a security identifier mechanism but sends
- CWE-1303: Non-Transparent Sharing of Microarchitectural ResourcesNon-Transparent Sharing of Microarchitectural Resources occurs when hardware structures shared across execution contexts (e.g., caches and branch
- CWE-1304: Improperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore OperationImproperly Preserved Integrity of Hardware Configuration State During a Power Save/Restore Operation occurs when a product performs a power
- CWE-1310: Missing Ability to Patch ROM CodeMissing Ability to Patch ROM Code occurs when the absence of patching capability for ROM code leaves systems vulnerable to unfixable security issues
