Szczegóły CWE-771

The product does not properly maintain a reference to a resource that has been allocated, which prevents the resource from being reclaimed.

Sposoby wprowadzenia

Implementation

Odpowiednie platformy

Język

Klasa: Not Language-Specific (Undetermined)

Typowe konsekwencje

Potencjalne środki zaradcze

Phases : Operation // Architecture and Design

Metody wykrywania

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

Uwagi dotyczące mapowania podatności

Uzasadnienie : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Komentarz : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.

Notatki

This weakness might not frequently apply to applications written in languages or frameworks that automatically perform garbage collection, since the removal of all references may act as a signal that the resource is ready to be reclaimed.

Zgłoszenie

Modyfikacje