2011 Top 25 - Porous Defenses

The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of ot...

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

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. This allows ...

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

The product does not perform an authorization check when an actor attempts to access a resource or perform an action.

The product does not encrypt sensitive or critical information before storage or transmission.

The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses ...

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

The product uses a one-way cryptographic hash against an input that should not be reversible, such as a password, but the product does not also use a salt as part of t...

The product contains hard-coded credentials, such as a password or cryptographic key, which it uses for its own inbound authentication, outbound communication to exter...

CWE entries in this view (graph) are listed in the 2011 CWE/SANS Top 25 Most Dangerous Software Errors.