CWE-586: CWE-586: Explicit Call to Finalize()

BaseStable

Description

View on MITRE
Back to CWE Lookup

Extended Description

Extended Description

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Languages
Platforms
Languages

Frequently Asked Questions

What is CWE-586: CWE-586: Explicit Call to Finalize()?+

CWE-586: CWE-586: Explicit Call to Finalize() is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Description Extended Description

What are the security consequences of CWE-586: Explicit Call to Finalize()?+

If exploited, CWE-586 (CWE-586: Explicit Call to Finalize()) it can compromise Unexpected State and Quality Degradation, leading to outcomes such as Scope: Integrity and Other.

How do you prevent or mitigate CWE-586: Explicit Call to Finalize()?+

Recommended mitigations for CWE-586 include: Do not make explicit calls to finalize(). Use static analysis tools to spot such instances.

Which programming languages are affected by CWE-586: Explicit Call to Finalize()?+

CWE-586 commonly affects Languages. Note that weaknesses are often language-agnostic patterns, so secure coding practices apply broadly.

What is the difference between a CWE and a CVE?+

A CWE (Common Weakness Enumeration) like CWE-586 describes a category of software weakness — the underlying flaw type. A CVE (Common Vulnerabilities and Exposures) identifies a specific, real-world vulnerability in a particular product. In short, a CWE is the kind of mistake, and a CVE is an instance of that mistake being found in software.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-586

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references