CWE-474 Base Borrador

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…

Definición

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.
Impacto en el mundo real

Real-world CVEs caused by CWE-474

Todavía no hay CVEs públicos enlazados a esta CWE en el catálogo de MITRE.

Cómo lo explotan los atacantes

Ruta del atacante paso a paso

  1. 1

    Identifica una ruta de código que maneje entrada no confiable sin validación.

  2. 2

    Crea un payload que ejercite el comportamiento inseguro — inyección, traversal, overflow o abuso de lógica.

  3. 3

    Envía el payload a través de una solicitud normal y observa la reacción de la aplicación.

  4. 4

    Itera hasta que la respuesta filtre datos, ejecute código del atacante o escale privilegios.

Ejemplo de código vulnerable

Vulnerable pseudo

MITRE no ha publicado un ejemplo de código para esta CWE. El patrón siguiente es ilustrativo — consulta Recursos para referencias canónicas.

Vulnerable pseudo 
// Example pattern — see MITRE for the canonical references.
function handleRequest(input) {
  // Untrusted input flows directly into the sensitive sink.
  return executeUnsafe(input);
}
Ejemplo de código seguro

Secure pseudo

Seguro 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.
Lista de prevención

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.
Señales de detección

How to detect CWE-474

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

Auto-corrección de Plexicus

Plexicus detecta automáticamente CWE-474 y abre un PR de corrección en menos de 60 segundos.

Codex Remedium escanea cada commit, identifica esta debilidad concreta y entrega un pull request listo para revisión con el parche. Sin tickets. Sin traspasos.

Solicitar demo Probar Plexicus gratis
Preguntas frecuentes

Frequently asked questions

¿Qué es 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.

¿Qué gravedad tiene CWE-474?

MITRE no ha publicado una calificación de probabilidad de explotación para esta debilidad. Trátala como de impacto medio hasta que tu modelo de amenazas demuestre lo contrario.

¿Qué lenguajes o plataformas se ven afectados por CWE-474?

MITRE lists the following affected platforms: C, PHP.

¿Cómo puedo prevenir CWE-474?

Do not accept inconsistent behavior from the API specifications when the deviant behavior increase the risk level.

¿Cómo detecta y corrige Plexicus CWE-474?

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-474 en cada commit. Cuando hay coincidencia, nuestro agente Codex Remedium abre un PR de corrección con el código corregido, las pruebas y un resumen de una línea para el revisor.

¿Dónde puedo aprender más sobre CWE-474?

MITRE publica la definición canónica en https://cwe.mitre.org/data/definitions/474.html. También puedes consultar la documentación de OWASP y NIST para guías relacionadas.

Debilidades relacionadas

Weaknesses related to CWE-474

CWE-758 Padre

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 Hermano

Insecure Automated Optimizations

This vulnerability occurs when software uses automated tools to optimize code for performance or efficiency, but those optimizations…

CWE-1102 Hermano

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 Hermano

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 Hermano

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 Hermano

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 Hermano

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 Hermano

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 Hijo

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…

Recursos

Further reading

Listo cuando tú lo estés

Deja de pagar por desarrollador.
Empieza a cerrar el bucle.

Plexicus es el ASPM nativo de IA que escanea, filtra, corrige, pentestea y explica — de forma autónoma. Desarrolladores ilimitados, repos ilimitados, acciones de IA de uso justo. Nivel gratuito real, €269/mo anual cuando estés listo.

Comenzar gratis Reservar una demo