CWE•Variant•Incomplete•5 recent CVEs
CWE-566Authorization Bypass Through User-Controlled SQL Primary Key
Description
The product uses a database table that includes records that should not be accessible to an actor, but it executes a SQL statement with a primary key that can be controlled by that actor.
Common consequences
- Confidentiality,Integrity,Access Control→Read Application Data,Modify Application Data,Bypass Protection MechanismWhen a user can set a primary key to any value, then the user can modify the key to point to unauthorized records.
Potential mitigations
- ImplementationModify the query to include a clause that performs an authorization check, or otherwise ensure that the check is performed before the query is executed.
- ImplementationAssume all input is malicious. Use a standard input validation mechanism to validate all input for length, type, syntax, and business rules before accepting the data. Use an "accept known good" validation strategy.
- ImplementationUse a parameterized query AND make sure that the accepted values conform to the business rules. Construct your SQL statement accordingly.