Categories

The software uses, accesses, or otherwise operates on a resource after that resource has been expired, released, or revoked.

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

A product requires authentication, but the product has an alternate path or channel that does not require authentication.

A product incorrectly assigns a privilege to a particular actor, creating an unintended sphere of control for that actor.

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."

Weaknesses in this category are related to errors in the management of cryptographic keys.

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

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

The software uses a Pseudo-Random Number Generator (PRNG) that does not correctly manage seeds.

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