Categories

Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion.

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.

The software uses a handler for a custom URL scheme, but it does not properly restrict which actors can invoke the handler using the scheme.

The application stores sensitive data under the web document root with insufficient access control, which might make it accessible to untrusted parties.

The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key.

The software receives input from an upstream component, but it does not neutralize or incorrectly neutralizes special characters that could be interpreted as web-scripting elements when they are sent to an error page.

The server contains a protection mechanism that assumes that any URI that is accessed using HTTP GET will not cause a state change to the associated resource. This might allow attackers to bypass intended access restrictions and conduct resource modification and deletion attacks, since some applications allow GET to modify state.