Since these bugs typically introduce incorrect behavior that is obvious to users, they are found quickly, unless they occur in rarely-tested code paths. Managing the correct number of arguments can be made more difficult in cases where format strings are used, or when variable numbers of arguments are supported.
CWE-628 Base Brouillon
Function Call with Incorrectly Specified Arguments
This weakness occurs when a function is called with arguments that are incorrectly specified, causing the function to behave in an unintended and consistently wrong manner.
Définition
What is CWE-628?
This weakness occurs when a function is called with arguments that are incorrectly specified, causing the function to behave in an unintended and consistently wrong manner.
This bug happens when the arguments passed to a function don't match what the function expects. Common mistakes include passing the wrong variable, providing too many or too few arguments, mixing up the argument order, using an incompatible data type, or supplying an incorrect literal value. Any of these errors will cause the function to process the wrong data, leading to unpredictable results, crashes, or security vulnerabilities.
For developers, preventing this issue requires careful attention to function signatures and API documentation. Always double-check the number, type, and order of arguments when calling functions, especially when working with external libraries or complex internal APIs. Using modern IDE features like type hints and auto-completion can help catch these mismatches early in the development cycle.
Impact réel
Real-world CVEs caused by CWE-628
-
The method calls the functions with the wrong argument order, which allows remote attackers to bypass intended access restrictions.
Comment les attaquants l'exploitent
Parcours de l'attaquant étape par étape
- 1
The following PHP method authenticates a user given a username/password combination but is called with the parameters in reverse order.
- 2
This Perl code intends to record whether a user authenticated successfully or not, and to exit if the user fails to authenticate. However, when it calls ReportAuth(), the third argument is specified as 0 instead of 1, so it does not exit.
- 3
In the following Java snippet, the accessGranted() method is accidentally called with the static ADMIN_ROLES array rather than the user roles.
Exemple de code vulnérable
Vulnerable PHP
The following PHP method authenticates a user given a username/password combination but is called with the parameters in reverse order.
function authenticate($username, $password) {
```
// authenticate user*
...}
authenticate($_POST['password'], $_POST['username']); 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-628
- Build and Compilation Once found, these issues are easy to fix. Use code inspection tools and relevant compiler features to identify potential violations. Pay special attention to code that is not likely to be exercised heavily during QA.
- Architecture and Design Make sure your API's are stable before you use them in production code.
Signaux de détection
How to detect CWE-628
CWE-628
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-628 ?
Quelle est la gravité de CWE-628 ?
Quels langages ou plateformes sont affectés par CWE-628 ?
Comment puis-je prévenir CWE-628 ?
Comment Plexicus détecte et corrige CWE-628 ?
Où puis-je en savoir plus sur CWE-628 ?
Frequently asked questions
Qu'est-ce que CWE-628 ?
This weakness occurs when a function is called with arguments that are incorrectly specified, causing the function to behave in an unintended and consistently wrong manner.
Quelle est la gravité de CWE-628 ?
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-628 ?
MITRE n'a pas spécifié les plateformes affectées pour ce CWE — il peut s'appliquer à la plupart des stacks applicatives.
Comment puis-je prévenir CWE-628 ?
Once found, these issues are easy to fix. Use code inspection tools and relevant compiler features to identify potential violations. Pay special attention to code that is not likely to be exercised heavily during QA. Make sure your API's are stable before you use them in production code.
Comment Plexicus détecte et corrige CWE-628 ?
Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-628 à 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-628 ?
MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/628.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.
Faiblesses associées
Weaknesses related to CWE-628
CWE-573 Parent
Improper Following of Specification by Caller
This weakness occurs when software fails to properly follow the documented rules, protocols, or requirements of an external component it…
CWE-103 Frère
Struts: Incomplete validate() Method Definition
This vulnerability occurs in a Struts application when a validator form either completely omits a validate() method or includes one but…
CWE-104 Frère
Struts: Form Bean Does Not Extend Validation Class
This vulnerability occurs in Apache Struts applications when a form bean class does not properly extend the framework's validation class.…
CWE-243 Frère
Creation of chroot Jail Without Changing Working Directory
This vulnerability occurs when a program creates a chroot jail but fails to change its current working directory afterward. Because the…
CWE-253 Frère
Incorrect Check of Function Return Value
This vulnerability occurs when a program misinterprets or improperly validates the return value from a function, causing it to miss…
CWE-296 Frère
Improper Following of a Certificate's Chain of Trust
This vulnerability occurs when software fails to properly validate the entire certificate chain back to a trusted root authority. This…
CWE-304 Frère
Missing Critical Step in Authentication
This vulnerability occurs when a software authentication process omits a required step, weakening its overall security.
CWE-325 Frère
Missing Cryptographic Step
This vulnerability occurs when a software implementation skips a critical step in a cryptographic process, resulting in security that is…
CWE-329 Frère
Generation of Predictable IV with CBC Mode
This vulnerability occurs when software uses a predictable or reused Initialization Vector (IV) with Cipher Block Chaining (CBC) mode…
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.