CWE-562 Base Borrador

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 pointer becomes invalid as soon as the function finishes,…

Definición

What is CWE-562?

This vulnerability occurs when a function returns a pointer to its own local variable. Since that variable's memory is on the stack, the pointer becomes invalid as soon as the function finishes, leading to crashes or unpredictable behavior.
When a function declares a local variable, it's stored in a temporary memory region called the stack. This stack space is only reserved for the lifetime of that function call. Once the function returns, its stack frame is cleared and that memory is marked as available for the next function call. If you return a pointer to this now-freed location, you're handing the calling code a 'dangling pointer' to a memory address that is no longer guaranteed to hold your intended data. The program may continue to run, but the next function that executes will likely reuse that same stack address for its own local variables, overwriting whatever value was there. Any subsequent attempt to read or write through the old pointer will access this new, unrelated data, causing corruption, logic errors, or most commonly, a sudden segmentation fault when the program tries to dereference the invalid pointer.
Impacto en el mundo real

Real-world CVEs caused by CWE-562

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 C

The following function returns a stack address.

Vulnerable C 
char* getName() {
  	char name[STR_MAX];
  	fillInName(name);
  	return name;
  }
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-562

  • Testing Use static analysis tools to spot return of the address of a stack variable.
Señales de detección

How to detect CWE-562

Fuzzing High

Fuzz testing (fuzzing) is a powerful technique for generating large numbers of diverse inputs - either randomly or algorithmically - and dynamically invoking the code with those inputs. Even with random inputs, it is often capable of generating unexpected results such as crashes, memory corruption, or resource consumption. Fuzzing effectively produces repeatable test cases that clearly indicate bugs, which helps developers to diagnose the issues.

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-562 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-562?

This vulnerability occurs when a function returns a pointer to its own local variable. Since that variable's memory is on the stack, the pointer becomes invalid as soon as the function finishes, leading to crashes or unpredictable behavior.

¿Qué gravedad tiene CWE-562?

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-562?

MITRE lists the following affected platforms: C, C++.

¿Cómo puedo prevenir CWE-562?

Use static analysis tools to spot return of the address of a stack variable.

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

El motor SAST de Plexicus detecta la firma de flujo de datos para CWE-562 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-562?

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

Debilidades relacionadas

Weaknesses related to CWE-562

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-474 Hermano

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…

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-672 Puede preceder

Operation on a Resource after Expiration or Release

This vulnerability occurs when a program continues to use a resource—like memory, a file handle, or a network connection—after it has been…

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