CWE-562 Base Brouillon

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,…

Définition

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.

Impact réel

Real-world CVEs caused by CWE-562

Aucune référence CVE publique n'est liée à ce CWE dans le catalogue MITRE pour le moment.

Comment les attaquants l'exploitent

Parcours de l'attaquant étape par étape

1
Identifier un chemin de code qui traite des entrées non fiables sans validation.
2
Élaborer une charge utile qui exploite le comportement non sécurisé — injection, traversal, débordement ou abus de logique.
3
Délivrer la charge utile via une requête normale et observer la réaction de l'application.
4
Itérer jusqu'à ce que la réponse divulgue des données, exécute le code de l'attaquant ou élève les privilèges.

Exemple de code vulnérable

Vulnerable C

The following function returns a stack address.

Vulnérable C

char* getName() {
  	char name[STR_MAX];
  	fillInName(name);
  	return name;
  }

Exemple de code sécurisé

Secure pseudo

Sécurisé 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-562

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

Signaux de détection

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

Correction automatique Plexicus

Plexicus détecte automatiquement CWE-562 et ouvre une PR de correction en moins de 60 secondes.

Codex Remedium analyse chaque commit, identifie cette faiblesse précise et livre une pull request prête à être relue avec le correctif. Pas de tickets. Pas de transferts.

Obtenir une démo Essayer Plexicus gratuitement

Questions fréquentes

Frequently asked questions

Qu'est-ce que CWE-562 ?

Quelle est la gravité de CWE-562 ?

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

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

Comment puis-je prévenir CWE-562 ?

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

Comment Plexicus détecte et corrige CWE-562 ?

Le moteur SAST de Plexicus reconnaît la signature de flux de données de CWE-562 à 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-562 ?

MITRE publie la définition canonique à https://cwe.mitre.org/data/definitions/562.html. Vous pouvez également consulter la documentation OWASP et NIST pour des conseils adjacents.

Faiblesses associées

Weaknesses related to CWE-562

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 Frère

Insecure Automated Optimizations

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

CWE-1102 Frère

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 Frère

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 Frère

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 Frère

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 Frère

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 Frère

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 Peut précéder

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…

Ressources

Arrêtez de payer par développeur.
Commencez à fermer la boucle.

Plexicus est l'ASPM natif IA qui scanne, filtre, corrige, penteste et explique — de façon autonome. Développeurs illimités, dépôts illimités, actions IA à usage équitable. Vrai niveau gratuit, €269/mo annuel quand vous êtes prêt.

Commencer gratuitement Réserver une démo