CWE-628 Base Draft

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.

Definition

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

Real-world CVEs caused by CWE-628

  • CVE-2006-7049

    The method calls the functions with the wrong argument order, which allows remote attackers to bypass intended access restrictions.

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

  1. 1

    The following PHP method authenticates a user given a username/password combination but is called with the parameters in reverse order.

  2. 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. 3

    In the following Java snippet, the accessGranted() method is accidentally called with the static ADMIN_ROLES array rather than the user roles.

Verwundbares Codebeispiel

Vulnerable PHP

The following PHP method authenticates a user given a username/password combination but is called with the parameters in reverse order.

Verwundbar PHP 
function authenticate($username, $password) {
```
// authenticate user* 
  		...}
  
  authenticate($_POST['password'], $_POST['username']);
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-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.
Erkennungssignale

How to detect CWE-628

Other

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.

Plexicus Auto-Fix

Plexicus erkennt CWE-628 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-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.

Wie gravierend ist CWE-628?

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-628 betroffen?

MITRE hat für diese CWE keine betroffenen Plattformen spezifiziert — sie kann in den meisten Anwendungs-Stacks auftreten.

Wie kann ich CWE-628 verhindern?

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.

Wie erkennt und behebt Plexicus CWE-628?

Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-628 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-628?

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

Verwandte Schwachstellen

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

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 Sibling

Missing Critical Step in Authentication

This vulnerability occurs when a software authentication process omits a required step, weakening its overall security.

CWE-325 Sibling

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 Sibling

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…

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