Categories

The software does not initialize a critical resource.

The software does not correctly calculate the size to be used when allocating a buffer, which could lead to a buffer overflow.

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

The software 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.

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.

The software 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.

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

Weaknesses in this category are related to improper calculation or conversion of numbers.

The software uses an algorithm or scheme that produces insufficient entropy, leaving patterns or clusters of values that are more likely to occur than others.

Weaknesses in this category are related to improper assignment or handling of permissions.