CWEweakness

CWE-1091 Use of Object without Invoking Destructor Method

Official page ↗
Abstraction
Base
Structure
Simple
Status
Incomplete
Languages
Object-Oriented
CWE version
5.0

Description

The product contains a method that accesses an object but does not later invoke the element's associated finalize/destructor method.

Common consequences

• Other: Reduce Performance — This issue can make the product perform more slowly by retaining memory and/or other resources longer than necessary. If the relevant code is reachable by an attacker, then this performance problem might introduce a vulnerability.

Detection methods

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

Related

Child of · CWE (2)

  • CWE-1076 Insufficient Adherence to Expected Conventions weakness
  • CWE-772 Missing Release of Resource after Effective Lifetime weakness

Referenced by CVE · weakness (1)

  • CVE-2026-3537 Object lifecycle issue in PowerVR in Google Chrome on Android prior to 145.0.7632.159 allowed a remote attacker to potentially exploit heap… vulnerability