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.

Definición

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 en el mundo real

Real-world CVEs caused by CWE-566

Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    Identifica una ruta de código que maneje entrada no confiable sin validación.

  2. 2

    Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.

  3. 3

    Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.

  4. 4

    Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.

Ejemplo de código vulnerable

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.

Vulnerable C# 
...
   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();
   ...
Ejemplo de código seguro

Secure pseudo

Seguro 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 prevención

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.
Señales de detección

How to detect CWE-566

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

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-566 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es 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.

¿Qué gravedad tiene CWE-566?

MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.

¿Qué lenguajes o plataformas se ven afectados por CWE-566?

MITRE lists the following affected platforms: SQL, Database Server.

¿Cómo puedo prevenir 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.

¿Cómo detecta y corrige Plexicus CWE-566?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-566 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-566?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/566.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-566

CWE-639 Padre

Authorization Bypass Through User-Controlled Key

This vulnerability occurs when an application's authorization system fails to verify that a user is allowed to access specific data before…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo