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-474 Base Draft
Use of Function with Inconsistent Implementations
This vulnerability occurs when code relies on a function whose behavior changes across different operating systems or versions, leading to unpredictable security risks when the software runs in an…
Definition
What is CWE-474?
This vulnerability occurs when code relies on a function whose behavior changes across different operating systems or versions, leading to unpredictable security risks when the software runs in an unexpected environment.
Functions can behave differently depending on where your code runs. These inconsistencies might involve how parameters are interpreted, what return codes mean, or whether the function even exists on a given platform. When you build or deploy software in an environment other than the one you tested in, these subtle differences can cause crashes, logic errors, or unexpected behavior that attackers might exploit.
Some implementations of a function might have known security flaws, while others are safe. This means your application's security could depend entirely on the underlying system it's running on, creating a hidden risk. To avoid this, never assume a function behaves identically everywhere; always check documentation for the specific platforms you target and consider using standardized, portable alternatives where possible.
Auswirkungen in der Praxis
Real-world CVEs caused by CWE-474
Bisher sind in MITREs Katalog keine öffentlichen CVE-Referenzen mit dieser CWE verknüpft.
Wie Angreifer es ausnutzen
Angreiferpfad Schritt für Schritt
- 1
Identifiziere einen Codepfad, der nicht vertrauenswürdige Eingaben ohne Validierung verarbeitet.
- 2
Erzeuge eine Payload, die das unsichere Verhalten auslöst — Injection, Traversal, Overflow oder Logik-Missbrauch.
- 3
Liefere die Payload über einen normalen Request aus und beobachte die Reaktion der Anwendung.
- 4
Iteriere, bis die Antwort Daten preisgibt, Angreifer-Code ausführt oder Berechtigungen eskaliert.
Verwundbares Codebeispiel
Vulnerable pseudo
MITRE hat kein Codebeispiel für diese CWE veröffentlicht. Das untenstehende Muster ist illustrativ — kanonische Referenzen findest du unter Ressourcen.
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
// Untrusted input flows directly into the sensitive sink.
return executeUnsafe(input);
} Sicheres Codebeispiel
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.
Präventions-Checkliste
How to prevent CWE-474
- Architecture and Design / Requirements Do not accept inconsistent behavior from the API specifications when the deviant behavior increase the risk level.
Erkennungssignale
How to detect CWE-474
CWE-474
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.
Häufig gestellte Fragen Was ist CWE-474?
Wie gravierend ist CWE-474?
Welche Sprachen oder Plattformen sind von CWE-474 betroffen?
Wie kann ich CWE-474 verhindern?
Wie erkennt und behebt Plexicus CWE-474?
Wo erfahre ich mehr über CWE-474?
Frequently asked questions
Was ist CWE-474?
This vulnerability occurs when code relies on a function whose behavior changes across different operating systems or versions, leading to unpredictable security risks when the software runs in an unexpected environment.
Wie gravierend ist CWE-474?
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-474 betroffen?
MITRE lists the following affected platforms: C, PHP.
Wie kann ich CWE-474 verhindern?
Do not accept inconsistent behavior from the API specifications when the deviant behavior increase the risk level.
Wie erkennt und behebt Plexicus CWE-474?
Die SAST-Engine von Plexicus erkennt die Datenfluss-Signatur von CWE-474 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-474?
MITRE veröffentlicht die kanonische Definition unter https://cwe.mitre.org/data/definitions/474.html. Für ergänzende Hinweise kannst du auch die OWASP- und NIST-Dokumentation heranziehen.
Verwandte Schwachstellen
Weaknesses related to CWE-474
CWE-758 Parent
Reliance on Undefined, Unspecified, or Implementation-Defined Behavior
This weakness occurs when software depends on specific behaviors of an API, data structure, or system component that are not formally…
CWE-1038 Sibling
Insecure Automated Optimizations
This vulnerability occurs when software uses automated tools to optimize code for performance or efficiency, but those optimizations…
CWE-1102 Sibling
Reliance on Machine-Dependent Data Representation
This weakness occurs when software directly depends on how a specific machine, processor, or operating system represents data in memory.…
CWE-1103 Sibling
Use of Platform-Dependent Third Party Components
This weakness occurs when software depends on third-party libraries or components that behave differently or lack support across various…
CWE-1105 Sibling
Insufficient Encapsulation of Machine-Dependent Functionality
This weakness occurs when an application relies on hardware-specific or platform-dependent features but fails to isolate that code from…
CWE-562 Sibling
Return of Stack Variable Address
This vulnerability occurs when a function returns a pointer to its own local variable. Since that variable's memory is on the stack, the…
CWE-587 Sibling
Assignment of a Fixed Address to a Pointer
This vulnerability occurs when code explicitly assigns a hardcoded memory address to a pointer, instead of using a dynamic or null value.
CWE-588 Sibling
Attempt to Access Child of a Non-structure Pointer
This vulnerability occurs when code incorrectly treats a pointer to a basic data type (like an integer) as if it points to a structured…
CWE-589 Child
Call to Non-ubiquitous API
This vulnerability occurs when software relies on an operating system function that isn't available on all versions of the target…
Ressourcen
Further reading
- MITRE — offizielle CWE-474 https://cwe.mitre.org/data/definitions/474.html
- Seven Pernicious Kingdoms: A Taxonomy of Software Security Errors https://samate.nist.gov/SSATTM_Content/papers/Seven%20Pernicious%20Kingdoms%20-%20Taxonomy%20of%20Sw%20Security%20Errors%20-%20Tsipenyuk%20-%20Chess%20-%20McGraw.pdf
Bereit, das Wesentliche zu validieren?
Bereit zu validieren, was zählt.
Plexicus ist Proof-Driven AppSec: validierte Funde, kontextuelles Verständnis und geprüfte Remediation — in Evidenz verankert, mit Ihnen gescoped.