563
When resources are released, they can be made available for reuse. For example, after memory
is de-allocated, an operating system may make the memory available to another process, or
disk space may be reallocated when a file is deleted. As removing information requires time and
additional resources, operating systems do not usually clear the previously written information.
Even when the resource is reused by the same process, this weakness can arise when new data is
not as large as the old data, which leaves portions of the old data still available. Equivalent errors
can occur in other situations where the length of data is variable but the associated data structure
is not. If memory is not cleared after use, the information may be read by less trustworthy parties
when the memory is reallocated.
This weakness can apply in hardware, such as when a device or system switches between power,
sleep, or debug states during normal operation, or when execution changes to different users or
privilege levels.
Relationships
The table(s) below shows the weaknesses and high level categories that are related to this
weakness. These relationships are defined as ChildOf, ParentOf, MemberOr and give insight to
similar items that may exist at higher and lower levels of abstraction. In addition, relationships such
as PeerOf and CanAlsoBe are defined to show similar weaknesses that may want to be explored.
Relevant to the view "Research Concepts" (CWE-1000)
Nature Type ID Name Page
ChildOf 212 Improper Removal of Sensitive Information Before Storage
or Transfer