CWE-583: finalize() Method Declared Public
The product violates secure coding principles for mobile code by declaring a finalize() method public.
How it's found
finalize() Method Declared Public is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
A product should never call finalize explicitly, except to call super.finalize() inside an implementation of finalize(). In mobile code situations, the otherwise error prone practice of manual garbage collection can become a security threat if an attacker can maliciously invoke a finalize() method because it is declared with public access.
Consequences
- Alter Execution Logic, Execute Unauthorized Code or Commands, Modify Application Data
Mitigations
- Implementation: If you are using finalize() as it was designed, there is no reason to declare finalize() with anything other than protected access.
Where this fits in a TurboPentest engagement
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Frequently asked questions
What is CWE-583?
The product violates secure coding principles for mobile code by declaring a finalize() method public.
How do you find finalize() Method Declared Public?
finalize() Method Declared Public is a specific, narrowly defined instance of a broader pattern. Testers confirm it with targeted code review and a proof-of-concept input that exercises the exact code path this weakness describes.
What is the impact of CWE-583?
Alter Execution Logic, Execute Unauthorized Code or Commands, Modify Application Data
Does TurboPentest test for finalize() Method Declared Public?
This weakness is not covered by the automated black-box pentest. IntegSec pentesters cover it in a manual engagement.
Related CWEs
Written and reviewed by
Michel Chamberland - Founder & CEO, IntegSec
CISSP, OSCP, OSCE, CEH, GIAC, CCSK · 20+ years in offensive security
Michel has spent 20+ years on offensive security teams including IBM X-Force Red and Trustwave SpiderLabs, leading penetration tests, red team engagements, and breach response for Fortune 500 customers. He is the founder of IntegSec and the architect of TurboPentest.
Find these issues before an attacker does
TurboPentest runs an agentic AI pentest against your target and reports findings with proof, from $99 per target.
Start a pentest