CWE-566 Variant Incomplete

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.

Definition

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.
Auswirkungen in der Praxis

Real-world CVEs caused by CWE-566

Bisher sind in MITREs Katalog keine öffentlichen CVE-Referenzen mit dieser CWE verknüpft.

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

  1. 1

    Identifiziere einen Codepfad, der nicht vertrauenswürdige Eingaben ohne Validierung verarbeitet.

  2. 2

    Erzeuge eine Payload, die das unsichere Verhalten auslöst — Injection, Traversal, Overflow oder Logik-Missbrauch.

  3. 3

    Liefere die Payload über einen normalen Request aus und beobachte die Reaktion der Anwendung.

  4. 4

    Iteriere, bis die Antwort Daten preisgibt, Angreifer-Code ausführt oder Berechtigungen eskaliert.

Verwundbares Codebeispiel

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.

Verwundbar 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();
   ...
Sicheres Codebeispiel

Secure pseudo

Sicher 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.
Präventions-Checkliste

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

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

Plexicus Auto-Fix

Plexicus erkennt CWE-566 automatisch und öffnet in unter 60 Sekunden einen Fix-PR.

Codex Remedium scannt jeden Commit, identifiziert genau diese Schwachstelle und liefert einen reviewer-ready Pull Request mit dem Patch. Keine Tickets. Keine Hand-offs.

Demo anfordern Plexicus kostenlos testen
Häufig gestellte Fragen

Frequently asked questions

Was ist 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.

Wie gravierend ist CWE-566?

MITRE hat für diese Schwachstelle keine Exploit-Wahrscheinlichkeit veröffentlicht. Behandle sie als mittlere Auswirkung, bis dein Threat Model anderes belegt.

Welche Sprachen oder Plattformen sind von CWE-566 betroffen?

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

Wie kann ich CWE-566 verhindern?

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.

Wie erkennt und behebt Plexicus CWE-566?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-566 bei jedem Commit. Bei einem Treffer öffnet unser Codex-Remedium-Agent einen Fix-PR mit korrigiertem Code, Tests und einer einzeiligen Zusammenfassung für den Reviewer.

Wo erfahre ich mehr über CWE-566?

MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/566.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.

Verwandte Schwachstellen

Weaknesses related to CWE-566

CWE-639 Parent

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…

Ressourcen

Further reading

Bereit, wenn du es bist

Schluss mit dem Bezahlen pro Entwickler.
Schließ den Kreislauf.

Plexicus ist die KI-native ASPM, die scannt, filtert, fixt, pentestet und erklärt — autonom. Unbegrenzte Entwickler, unbegrenzte Repos, Fair-Use-KI-Aktionen. Echter kostenloser Tarif, €269/mo jährlich, wenn du bereit bist.

Kostenlos starten Demo buchen