Detail CWE-583

The product violates secure coding principles for mobile code by declaring a finalize() method public.

Mode Pengenalan

Implementation

Platform yang Berlaku

Bahasa

Nama: Java (Undetermined)

Konsekuensi Umum

Mitigasi yang Memungkinkan

Phases : Implementation
A product should never call finalize explicitly, except to call super.finalize() inside an implementation of finalize(). If you are using finalize() as it was designed, there is no reason to declare finalize() with anything other than protected access.

Metode Deteksi

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.)
Efektivitas : High

Catatan Pemetaan Kerentanan

Justifikasi : This CWE entry is at the Variant level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.
Komentar : 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.

Pengajuan

Modifikasi