Common Weakness Enumeration (CWE)

The product uses obfuscation or encryption of inputs that should not be mutable by an external actor, but the product does not use integrity checks to detect if those inputs have been modified.

The product does not properly handle null bytes or NUL characters when passing data between different representations or components.

The product stores sensitive information in cleartext within the GUI.

The product does not follow certain coding rules for development, which can lead to resultant weaknesses or increase the severity of the associated vulnerabilities.

The product accepts XML from an untrusted source but does not validate the XML against the proper schema.

The code has a synchronous call to a remote resource, but there is no timeout for the call, or the timeout is set to infinite.

The product allows an entity to perform a legitimate but expensive operation before authentication or authorization has taken place.

The product does not use a standardized method for handling errors throughout the code, which might introduce inconsistent error handling and resultant weaknesses.

The product reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations prior to the targeted buffer.

The product stores sensitive information in cleartext in a cookie.

A function returns the address of a stack variable, which will cause unintended program behavior, typically in the form of a crash.

The product validates input before applying protection mechanisms that modify the input, which could allow an attacker to bypass the validation via dangerous inputs that only arise after the modification.

Immutable data, such as a first-stage bootloader, device identifiers, and "write-once" configuration settings are stored in writable memory that can be re-programmed or updated in the field.

The product does not properly handle when an input uses an alternate encoding that is valid for the control sphere to which the input is being sent.

The web application does not neutralize or incorrectly neutralizes scripting elements within attributes of HTML IMG tags, such as the src attribute.

The product opens an alternate channel to communicate with an authorized user, but the channel is accessible to other actors.

A certificate expiration is not validated or is incorrectly validated, so trust may be assigned to certificates that have been abandoned due to age.

A process does not close sensitive file descriptors before invoking a child process, which allows the child to perform unauthorized I/O operations using those descriptors.

A function can return a pointer to memory that is outside of the buffer that the pointer is expected to reference.

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

An exact value or random number can be precisely predicted by observing previous values.

No description available.

The product, when opening a file or directory, does not sufficiently handle when the name is associated with a hard link to a target that is outside of the intended control sphere. This could allow an attacker to cause the product to operate on unauthorized files.

The product properly checks for the existence of a lock, but the lock can be externally controlled or influenced by an actor that is outside of the intended sphere of control.

The web application uses persistent cookies, but the cookies contain sensitive information.