CWE-416 Variant Stable High likelihood

Use After Free

Use After Free happens when a program continues to use a pointer to a memory location after that memory has been freed. This can lead to unpredictable behavior, crashes, or security vulnerabilities…

Definition

What is CWE-416?

Use After Free happens when a program continues to use a pointer to a memory location after that memory has been freed. This can lead to unpredictable behavior, crashes, or security vulnerabilities because the freed memory may have been reallocated for a different purpose.
This vulnerability occurs because the pointer isn't invalidated after `free()` is called. The memory manager can then reassign that same memory block to a different part of the program, perhaps for storing unrelated data. When the original, now 'dangling' pointer is used again, it reads or writes to this new data, corrupting it and leading to instability or exploitable conditions like arbitrary code execution. Detecting use-after-free bugs manually is challenging as they often depend on complex, state-specific execution paths. While SAST tools can flag the dangerous pattern, Plexicus uses AI to analyze context and suggest precise code fixes—such as nullifying pointers or reordering logic—saving developers hours of manual debugging and helping secure the entire application lifecycle.
Vulnerability Diagram CWE-416
Use After Free malloc → p free(p) p still held attacker malloc reclaims slot use *p (vtable call) jumps to attacker data A freed pointer is reused after the slot is owned by attacker data.
Auswirkungen in der Praxis

Real-world CVEs caused by CWE-416

  • CVE-2022-20141

    Chain: an operating system kernel has insufficent resource locking (CWE-413) leading to a use after free (CWE-416).

  • CVE-2022-2621

    Chain: two threads in a web browser use the same resource (CWE-366), but one of those threads can destroy the resource before the other has completed (CWE-416).

  • CVE-2021-0920

    Chain: mobile platform race condition (CWE-362) leading to use-after-free (CWE-416), as exploited in the wild per CISA KEV.

  • CVE-2020-6819

    Chain: race condition (CWE-362) leads to use-after-free (CWE-416), as exploited in the wild per CISA KEV.

  • CVE-2010-4168

    Use-after-free triggered by closing a connection while data is still being transmitted.

  • CVE-2010-2941

    Improper allocation for invalid data leads to use-after-free.

  • CVE-2010-2547

    certificate with a large number of Subject Alternate Names not properly handled in realloc, leading to use-after-free

  • CVE-2010-1772

    Timers are not disabled when a related object is deleted

Wie Angreifer es ausnutzen

Angreiferpfad Schritt für Schritt

  1. 1

    The following example demonstrates the weakness.

  2. 2

    The following code illustrates a use after free error:

  3. 3

    When an error occurs, the pointer is immediately freed. However, this pointer is later incorrectly used in the logError function.

Verwundbares Codebeispiel

Vulnerable C

The following example demonstrates the weakness.

Verwundbar C 
#include <stdio.h>
  #include <unistd.h>
  #define BUFSIZER1 512
  #define BUFSIZER2 ((BUFSIZER1/2) - 8)
  int main(int argc, char **argv) {
  	char *buf1R1;
  	char *buf2R1;
  	char *buf2R2;
  	char *buf3R2;
  	buf1R1 = (char *) malloc(BUFSIZER1);
  	buf2R1 = (char *) malloc(BUFSIZER1);
  	free(buf2R1);
  	buf2R2 = (char *) malloc(BUFSIZER2);
  	buf3R2 = (char *) malloc(BUFSIZER2);
  	strncpy(buf2R1, argv[1], BUFSIZER1-1);
  	free(buf1R1);
  	free(buf2R2);
  	free(buf3R2);
  }
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-416

  • Architecture and Design Choose a language that provides automatic memory management.
  • Implementation When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.
Erkennungssignale

How to detect CWE-416

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

Plexicus Auto-Fix

Plexicus erkennt CWE-416 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-416?

Use After Free happens when a program continues to use a pointer to a memory location after that memory has been freed. This can lead to unpredictable behavior, crashes, or security vulnerabilities because the freed memory may have been reallocated for a different purpose.

Wie gravierend ist CWE-416?

MITRE stuft die Exploit-Wahrscheinlichkeit als hoch ein — diese Schwachstelle wird aktiv in freier Wildbahn ausgenutzt und sollte priorisiert behoben werden.

Welche Sprachen oder Plattformen sind von CWE-416 betroffen?

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

Wie kann ich CWE-416 verhindern?

Choose a language that provides automatic memory management. When freeing pointers, be sure to set them to NULL once they are freed. However, the utilization of multiple or complex data structures may lower the usefulness of this strategy.

Wie erkennt und behebt Plexicus CWE-416?

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

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

Verwandte Schwachstellen

Weaknesses related to CWE-416

CWE-825 Parent

Expired Pointer Dereference

This vulnerability occurs when a program tries to use a pointer that still points to a memory location that has already been freed or…

CWE-415 Sibling

Double Free

A double free vulnerability occurs when a program mistakenly calls the 'free()' function twice on the same block of memory.

CWE-120 Kann vorausgehen

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

This vulnerability occurs when a program copies data from one memory location to another without first verifying that the source data will…

CWE-123 Kann vorausgehen

Write-what-where Condition

A write-what-where condition occurs when an attacker can control both the data written and the exact memory location where it's written,…

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