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 Incomplet
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.
Définition
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.
Impact réel
Real-world CVEs caused by CWE-566
Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
- 2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
- 3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
- 4
Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.
Exemple de code vulnérable
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();
... Exemple de code sécurisé
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.
Liste de contrôle de prévention
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.
Signaux de détection
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.
Questions fréquentes Qu'est-ce que CWE-566 ?
Quelle est la gravité de CWE-566 ?
Quels langages ou plateformes sont affectés par CWE-566 ?
Comment puis-je prévenir CWE-566 ?
Comment Plexicus détecte et corrige CWE-566 ?
Où puis-je en savoir plus sur CWE-566 ?
Frequently asked questions
Qu'est-ce que 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.
Quelle est la gravité de CWE-566 ?
MITRE n'a pas publié de note de probabilité d'exploitation pour cette faiblesse. Traitez-la comme un impact moyen jusqu'à ce que votre modèle de menace prouve le contraire.
Quels langages ou plateformes sont affectés par CWE-566 ?
MITRE lists the following affected platforms: SQL, Database Server.
Comment puis-je prévenir 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.
Comment Plexicus détecte et corrige CWE-566 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-566 à chaque commit. Lorsqu'une correspondance est trouvée, notre agent Codex Remedium ouvre une PR de correction avec le code corrigé, les tests et un résumé d'une ligne pour le relecteur.
Où puis-je en savoir plus sur CWE-566 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/566.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-566
Prêt à valider l'essentiel ?
Prêt à valider ce qui compte.
Plexicus est Proof-Driven AppSec : findings validés, compréhension contextuelle et remédiation relue — ancrée dans la preuve, scopée avec vous.