Common Weakness Enumeration (CWE)

The product calls free() on a pointer to a memory resource that was allocated on the heap, but the pointer is not at the start of the buffer.

The code uses an operator for comparison when the intention was to perform an assignment.

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.

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '...' (triple dot) sequences that can resolve to a location that is outside of that directory.

The product generates a core dump file in a directory, archive, or other resource that is stored, transferred, or otherwise made accessible to unauthorized actors.

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

A Pseudo-Random Number Generator (PRNG) uses a relatively small seed space, which makes it more susceptible to brute force attacks.

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.

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.

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.

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

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

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '\dir\..\filename' (leading backslash dot dot) sequences that can resolve to a location that is outside of that directory.

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

No description available.

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.

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.

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

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

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

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

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

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

The product calls a function, procedure, or routine, but the caller specifies too many arguments, or too few arguments, which may lead to undefined behavior and resultant weaknesses.

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