Common Weakness Enumeration (CWE)

The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type.

The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.

The product uses or accesses a resource that has not been initialized.

The product does not verify, or incorrectly verifies, the cryptographic signature for data.

The product calls free() twice on the same memory address, potentially leading to modification of unexpected memory locations.

The product contains an assert() or similar statement that can be triggered by an attacker, which leads to an application exit or other behavior that is more severe than necessary.

The product checks the state of a resource before using that resource, but the resource's state can change between the check and the use in a way that invalidates the results of the check. This can cause the product to perform invalid actions when the resource is in an unexpected state.

The product stores sensitive information in cleartext within a resource that might be accessible to another control sphere.

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

The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data.

The product does not release or incorrectly releases a resource before it is made available for re-use.

The product does not properly verify that the source of data or communication is valid.

The product behaves differently or sends different responses under different circumstances in a way that is observable to an unauthorized actor, which exposes security-relevant information about the state of the product, such as whether a particular operation was successful or not.

This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.

No description available.

The product exposes a resource to the wrong control sphere, providing unintended actors with inappropriate access to the resource.

The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.

The product allows user input to control or influence paths or file names that are used in filesystem operations.

The product uses a broken or risky cryptographic algorithm or protocol.

The product searches for critical resources using an externally-supplied search path that can point to resources that are not under the product's direct control.

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

The product does not implement sufficient measures to prevent multiple failed authentication attempts within a short time frame, making it more susceptible to brute force attacks.

The product uses untrusted input when calculating or using an array index, but the product does not validate or incorrectly validates the index to ensure the index references a valid position within the array.

According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization."