1013
Nature Type ID Name Page
ChildOf 672 Operation on a Resource after Expiration or Release 1479
Relevant to the view "CISQ Data Protection Measures" (CWE-1340)
Nature Type ID Name Page
ChildOf 672 Operation on a Resource after Expiration or Release 1479
Applicable Platforms
Language : C (Prevalence = Undetermined)
Language : C++ (Prevalence = Undetermined)
Alternate Terms
Dangling pointer :
Use-After-Free :
Likelihood Of Exploit
High
Common Consequences
Scope Impact Likelihood
Integrity Modify Memory
The use of previously freed memory may corrupt valid
data, if the memory area in question has been allocated
and used properly elsewhere.
Availability DoS: Crash, Exit, or Restart
If chunk consolidation occurs after the use of previously
freed data, the process may crash when invalid data is
used as chunk information.
Integrity
Confidentiality
Availability
Execute Unauthorized Code or Commands
If malicious data is entered before chunk consolidation can
take place, it may be possible to take advantage of a writewhat-
where primitive to execute arbitrary code.
Detection Methods
Fuzzing
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.
Effectiveness = High
Automated Static Analysis
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.)
Effectiveness = High
Potential Mitigations
Phase: Architecture and Design
CWE Version 4.14
CWE-416: Use After Free
CWE-416: Use After Free