CWE-566
Authorization 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.
{"xhtml:p":["When a user can set a primary key to any value, then the user can modify the key to point to unauthorized records.","Database access control errors occur when:"],"xhtml:ul":[{"xhtml:li":["Data enters a program from an untrusted source.","The data is used to specify the value of a primary key in a SQL query.","The untrusted source does not have the permissions to be able to access all rows in the associated table."]}]}
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Read Application Data, Modify Application Data, Bypass Protection Mechanism
Potential Mitigations
Assume 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.
Use a parameterized query AND make sure that the accepted values conform to the business rules. Construct your SQL statement accordingly.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now