Common Weakness Enumeration (CWE)

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

The authentication scheme or implementation uses key data elements that are assumed to be immutable, but can be controlled or modified by the attacker.

A feature, API, or function does not perform according to its specification.

The product uses a cookie to store sensitive information, but the cookie is not marked with the HttpOnly flag.

Obscuring a password with a trivial encoding does not protect the password.

The product does not handle or incorrectly handles when it has insufficient privileges to perform an operation, leading to resultant weaknesses.

The product specifies a regular expression in a way that causes data to be improperly matched or compared.

The product receives data from an upstream component, but does not completely filter special elements before sending it to a downstream component.

The product does not properly check inputs that are used for loop conditions, potentially leading to a denial of service or other consequences because of excessive looping.

The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor.

The product writes to a buffer using an index or pointer that references a memory location prior to the beginning of the buffer.

The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

The product performs multiple related behaviors, but the behaviors are performed in the wrong order in ways which may produce resultant weaknesses.

The product implements an authentication technique, but it skips a step that weakens the technique.

The product does not properly protect an assumed-immutable element from being modified by an attacker.

The product establishes a communication channel with an endpoint and receives a message from that endpoint, but it does not sufficiently ensure that the message was not modified during transmission.

When trying to keep information confidential, an attacker can often infer some of the information by using statistics.

The product protects a primary channel, but it does not use the same level of protection for an alternate channel.

The product implements an IOCTL with functionality that should be restricted, but it does not properly enforce access control for the IOCTL.

The elevated privilege level required to perform operations such as chroot() should be dropped immediately after the operation is performed.

The product stores sensitive information in cleartext in memory.

The product does not adequately filter user-controlled input for special elements with control implications.

The product uses a WebSocket, but it does not properly verify that the source of data or communication is valid.

A protocol or its implementation supports interaction between multiple actors and allows those actors to negotiate which algorithm should be used as a protection mechanism such as encryption or authentication, but it does not select the strongest algorithm that is available to both parties.

The product releases a resource such as memory or a file so that it can be made available for reuse, but it does not clear or "zeroize" the information contained in the resource before the product performs a critical state transition or makes the resource available for reuse by other entities.