Categories

The software allocates file descriptors or handles on behalf of an actor without imposing any restrictions on how many descriptors can be allocated, in violation of the intended security policy for that actor.

Software that does not appropriately monitor or control resource consumption can lead to adverse system performance.

The software receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified.

This entry has been deprecated, as it was not effective as a weakness and was structured more like a category. In addition, the name is inappropriate, since the container term is widely understood by developers in different ways than originally intended by PLOVER, the original source for this entry.

Weaknesses in this category are related to improper management of system state.Weaknesses in this category are related to improper management of system state.

The software does not sufficiently monitor or control transmitted network traffic volume, so that an actor can cause the software to transmit more traffic than should be allowed for that actor.

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

Opening temporary files without appropriate measures or controls can leave the file, its contents and any function that it impacts vulnerable to attack.

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

The software does not lock or does not correctly lock a resource when the software must have exclusive access to the resource.