970 indexed

CWECWE weaknesses

970 MITRE CWE entries — software weakness types that underlie vulnerabilities (CVE→CWE link). Filter by category. Authored by Adam Lundqvist.

Showing 101–150 of 970 · page 3 of 20

IDTitleSummary
CWE-1120Excessive Code ComplexityThe code is too complex, as calculated using a well-defined, quantitative measure.
CWE-1121Excessive McCabe Cyclomatic ComplexityThe code contains McCabe cyclomatic complexity that exceeds a desirable maximum.
CWE-1122Excessive Halstead ComplexityThe code is structured in a way that a Halstead complexity measure exceeds a desirable maximum.
CWE-1123Excessive Use of Self-Modifying CodeThe product uses too much self-modifying code.
CWE-1124Excessively Deep NestingThe code contains a callable or other code grouping in which the nesting / branching is too deep.
CWE-1125Excessive Attack SurfaceThe product has an attack surface whose quantitative measurement exceeds a desirable maximum.
CWE-1126Declaration of Variable with Unnecessarily Wide ScopeThe source code declares a variable in one scope, but the variable is only used within a narrower scope.
CWE-1127Compilation with Insufficient Warnings or ErrorsThe code is compiled without sufficient warnings enabled, which may prevent the detection of subtle bugs or quality issues.
CWE-113Improper 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 L…
CWE-114Process ControlExecuting commands or loading libraries from an untrusted source or in an untrusted environment can cause an application to execute malicious commands (and pay…
CWE-115Misinterpretation of InputThe product misinterprets an input, whether from an attacker or another product, in a security-relevant fashion.
CWE-116Improper Encoding or Escaping of OutputThe product prepares a structured message for communication with another component, but encoding or escaping of the data is either missing or done incorrectly.…
CWE-1164Irrelevant CodeThe 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,…
CWE-117Improper Output Neutralization for LogsThe product constructs a log message from external input, but it does not neutralize or incorrectly neutralizes special elements when the message is written to…
CWE-1173Improper Use of Validation FrameworkThe product does not use, or incorrectly uses, an input validation framework that is provided by the source language or an independent library. Many modern co…
CWE-1174ASP.NET Misconfiguration: Improper Model ValidationThe ASP.NET application does not use, or incorrectly uses, the model validation framework.
CWE-1176Inefficient CPU ComputationThe product performs CPU computations using algorithms that are not as efficient as they could be for the needs of the developer, i.e., the c…
CWE-1177Use of Prohibited CodeThe product uses a function, library, or third party component that has been explicitly prohibited, whether by the developer or the customer.
CWE-118Incorrect 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 memor…
CWE-1187DEPRECATED: Use of Uninitialized ResourceThis entry has been deprecated because it was a duplicate of CWE-908. All content has been transferred to CWE-908.
CWE-1188Initialization of a Resource with an Insecure DefaultThe product initializes or sets a resource with a default that is intended to be changed by the product's installer, administrator, or maintainer, but the defa…
CWE-1189Improper 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-119Improper Restriction of Operations within the Bounds of a Memory BufferThe 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…
CWE-1190DMA Device Enabled Too Early in Boot PhaseThe product enables a Direct Memory Access (DMA) capable device before the security configuration settings are established, which allows an attacker to extract…
CWE-1191On-Chip Debug and Test Interface With Improper Access ControlThe chip does not implement or does not correctly perform access control to check whether users are authorized to access internal registers and test modes thro…
CWE-1192Improper 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-1193Power-On of Untrusted Execution Core Before Enabling Fabric Access ControlThe product enables components that contain untrusted firmware before memory and fabric access controls have been enabled.
CWE-12ASP.NET Misconfiguration: Missing Custom Error PageAn ASP .NET application must enable custom error pages in order to prevent attackers from mining information from the framework's built-in responses.
CWE-120Buffer 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-1204Generation 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 unpredict…
CWE-1209Failure to Disable Reserved BitsThe reserved bits in a hardware design are not disabled prior to production. Typically, reserved bits are used for future capabilities and should not support a…
CWE-121Stack-based Buffer OverflowA 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 pa…
CWE-122Heap-based Buffer OverflowA 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…
CWE-1220Insufficient Granularity of Access ControlThe 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 sy…
CWE-1221Incorrect Register Defaults or Module ParametersHardware description language code incorrectly defines register defaults or hardware Intellectual Property (IP) parameters to insecure values.
CWE-1222Insufficient Granularity of Address Regions Protected by Register LocksThe product defines a large address region protected from modification by the same register lock control bit. This results in a conflict between the functional…
CWE-1223Race Condition for Write-Once AttributesA write-once register in hardware design is programmable by an untrusted software component earlier than the trusted software component, resulting in a race co…
CWE-1224Improper Restriction of Write-Once Bit FieldsThe hardware design control register "sticky bits" or write-once bit fields are improperly implemented, such that they can be reprogrammed by software.
CWE-1229Creation of Emergent ResourceThe 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 p…
CWE-123Write-what-where ConditionAny 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-1230Exposure of Sensitive Information Through MetadataThe product prevents direct access to a resource containing sensitive information, but it does not sufficiently limit access to metadata that is derived from t…
CWE-1231Improper Prevention of Lock Bit ModificationThe 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…
CWE-1232Improper Lock Behavior After Power State TransitionRegister lock bit protection disables changes to system configuration once the bit is set. Some of the protected registers or lock bits become programmable aft…
CWE-1233Security-Sensitive Hardware Controls with Missing Lock Bit ProtectionThe 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 …
CWE-1234Hardware Internal or Debug Modes Allow Override of LocksSystem configuration protection may be bypassed during debug mode.
CWE-1235Incorrect Use of Autoboxing and Unboxing for Performance Critical OperationsThe code uses boxed primitives, which may introduce inefficiencies into performance-critical operations.
CWE-1236Improper Neutralization of Formula Elements in a CSV FileThe product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements tha…
CWE-1239Improper Zeroization of Hardware RegisterThe hardware product does not properly clear sensitive information from built-in registers when the user of the hardware block changes. Hardware logic operate…
CWE-124Buffer 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-1240Use of a Cryptographic Primitive with a Risky ImplementationTo fulfill the need for a cryptographic primitive, the product implements a cryptographic algorithm using a non-standard, unproven, or disallowed/non-compliant…
Sourced from MITRE CWE 4.x XML. Curated by Adam Lundqvist, Founder at SQUR.
CWE weaknesses — by category | SQUR Knowledge Base