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.)
CWE-566 Variante Incompleto
Authorization Bypass Through User-Controlled SQL Primary Key
This vulnerability occurs when an application allows a user to directly control the primary key value used in a SQL query, enabling them to access database records they are not authorized to view.
Definição
What is CWE-566?
This vulnerability occurs when an application allows a user to directly control the primary key value used in a SQL query, enabling them to access database records they are not authorized to view.
This flaw typically unfolds in three steps: first, user-supplied data from an untrusted source (like a URL parameter or form field) is accepted without proper validation. Second, this data is directly used to specify a primary key in a SQL statement, such as in a `WHERE` clause. Finally, because the database query does not enforce additional row-level permissions, the user can manipulate the key to retrieve or modify records belonging to other users, effectively bypassing the application's intended authorization checks.
Preventing this requires implementing proper access control at the data layer, such as adding checks to ensure the requested record belongs to the current user's session. Managing this at scale is difficult; an ASPM like Plexicus can help you track and remediate these authorization flaws across your entire stack by correlating user flows with data access patterns.
Impacto no mundo real
Real-world CVEs caused by CWE-566
Ainda não há referências CVE públicas associadas a este CWE no catálogo da MITRE.
Como os atacantes a exploram
Trajeto do atacante passo a passo
- 1
Identificar um caminho de código que trata input não confiável sem validação.
- 2
Criar um payload que explora o comportamento inseguro — injeção, traversal, overflow ou abuso de lógica.
- 3
Entregar o payload através de um pedido normal e observar a reação da aplicação.
- 4
Iterar até que a resposta exponha dados, execute código do atacante ou escale privilégios.
Exemplo de código vulnerável
Vulnerable C#
The following code uses a parameterized statement, which escapes metacharacters and prevents SQL injection vulnerabilities, to construct and execute a SQL query that searches for an invoice matching the specified identifier [1]. The identifier is selected from a list of all invoices associated with the current authenticated user.
...
conn = new SqlConnection(_ConnectionString);
conn.Open();
int16 id = System.Convert.ToInt16(invoiceID.Text);
SqlCommand query = new SqlCommand( "SELECT * FROM invoices WHERE id = @id", conn);
query.Parameters.AddWithValue("@id", id);
SqlDataReader objReader = objCommand.ExecuteReader();
... Exemplo de código seguro
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Lista de verificação de prevenção
How to prevent CWE-566
- Implementation 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 Use a parameterized query AND make sure that the accepted values conform to the business rules. Construct your SQL statement accordingly.
Sinais de deteção
How to detect CWE-566
CWE-566
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Perguntas frequentes O que é o CWE-566?
Qual a gravidade do CWE-566?
Que linguagens ou plataformas são afetadas pelo CWE-566?
Como posso prevenir o CWE-566?
Como é que o Plexicus deteta e corrige o CWE-566?
Onde posso saber mais sobre o CWE-566?
Frequently asked questions
O que é o CWE-566?
This vulnerability occurs when an application allows a user to directly control the primary key value used in a SQL query, enabling them to access database records they are not authorized to view.
Qual a gravidade do CWE-566?
A MITRE não publicou uma classificação de probabilidade de exploração para esta fraqueza. Trate-a como impacto médio até o seu modelo de ameaças provar o contrário.
Que linguagens ou plataformas são afetadas pelo CWE-566?
MITRE lists the following affected platforms: SQL, Database Server.
Como posso prevenir o CWE-566?
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.
Como é que o Plexicus deteta e corrige o CWE-566?
O motor SAST do Plexicus correlaciona a assinatura de fluxo de dados do CWE-566 em cada commit. Quando é encontrada uma correspondência, o nosso agente Codex Remedium abre um PR de correção com o código corrigido, testes e um resumo de uma linha para o revisor.
Onde posso saber mais sobre o CWE-566?
A MITRE publica a definição canónica em https://cwe.mitre.org/data/definitions/566.html. Pode também consultar a documentação da OWASP e do NIST para orientações adjacentes.
Fraquezas relacionadas
Weaknesses related to CWE-566
Pronto para validar o que importa?
Pronto para validar o que importa.
O Plexicus é Proof-Driven AppSec: achados validados, compreensão contextual e remediação revisada — ancorada em evidência, escopada com você.