COMMON WEAKNESS ENUMERATIONIncomplete

CWE-566

Authorization Bypass Through User-Controlled SQL Primary Key

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.

Soyutlama

Variant

Yapı

Simple

Sömürü İhtimali

Medium

Problemi anla

Problem nedir?

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.

Genişletilmiş açıklama

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: - 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.

Kök neden

Problem nasıl ve ne zaman oluşur?

Yaşam döngüsü evresi

Architecture and Design

COMMISSION: This weakness refers to an incorrect design related to an architectural security tactic.

Yaşam döngüsü evresi

Implementation

Risk

Başarılı sömürü neye yol açar?

Read Application DataModify Application DataBypass Protection Mechanism

Etkilenen güvenlik alanları: Confidentiality, Integrity, Access Control

Savunma

Nasıl önlenir ve çözülür?

Implementation

Uygulama aşaması savunması

Detay
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.

Implementation

Uygulama aşaması savunması

Detay
Use a parameterized query AND make sure that the accepted values conform to the business rules. Construct your SQL statement accordingly.

Doğrulama

Nasıl tespit edilir?

Automated Static Analysis

High
Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)