CWE-582: Array Declared Public, Final, and Static

Extended Description

Because arrays are mutable objects, the final constraint requires that the array object itself be assigned only once, but makes no guarantees about the values of the array elements. Since the array is public, a malicious program can change the values stored in the array. As such, in most cases an array declared public, final and static is a bug.

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-582 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-582, Array Declared Public, Final, and Static, throughout the product lifecycle. Derive review questions, static or dynamic checks, and negative tests from the CWE's causal behavior; define the components and lifecycle stages each check covers; and retain findings with enough evidence to distinguish the root cause from symptoms and impacts. Track escapes and false negatives, then improve the verification plan after every confirmed occurrence.

NIST SP 800-218 Secure Software Development Framework — National Institute of Standards and Technology

Address Array Declared Public, Final, and Static during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include Modify Application Data. Use these source-defined anchors to turn CWE-582 into implementation, review, and verification checks for the affected component.

CWE-582: Array Declared Public, Final, and Static — MITRE CWE

Triage CWE-582 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-582, Array Declared Public, Final, and Static, has evidence of exploitation in the wild. Confirm the CVE-to-CWE root-cause mapping independently before attaching the example, then capture the affected product, required action, and remediation deadline. A missing KEV match is not evidence that the weakness is unexploited, and a KEV entry must not be generalized to every occurrence of this CWE.

Known Exploited Vulnerabilities Catalog — Cybersecurity and Infrastructure Security Agency

Apply precise root-cause mapping to CWE-582

Apply MITRE's full root-cause mapping guidance when using CWE-582, Array Declared Public, Final, and Static. Separate weakness language from attacker prerequisites and technical impact, check the entry's abstraction and vulnerability-mapping notes, and prefer the most specific Base or Variant supported by the evidence. Record the rejected alternatives and require an independent review before the mapping is used for remediation trends or program metrics.

CVE to CWE Root Cause Mapping Guidance — MITRE CWE

Validate CWE-582 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-582, Array Declared Public, Final, and Static. Confirm the finding describes the causal weakness rather than an impact or attack pattern, compare the abstraction and mapping notes with plausible alternatives, and have a second reviewer challenge the selection. Preserve the evidence and reasoning so recurring defects can be measured against one consistent identifier.

CVE to CWE Root Cause Mapping Quick Tips — MITRE CWE

Frequently Asked Questions

What is CWE-582: Array Declared Public, Final, and Static?+

CWE-582: Array Declared Public, Final, and Static is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product declares an array public, final, and static, which is not sufficient to prevent the array's contents from being modified. Because arrays are mutable objects, the final constraint requires that the array object itself be assigned only once, but makes no guarantees about the values of the array elements. Since the array is public, a malicious program can change the values stored in the array. As such, in most cases an array declared public, final and static is a bug.

What are the security consequences of Array Declared Public, Final, and Static?+

If exploited, CWE-582 (Array Declared Public, Final, and Static) it can compromise Integrity, leading to outcomes such as Modify Application Data.

How do you prevent or mitigate Array Declared Public, Final, and Static?+

Recommended mitigations for CWE-582 include: In most situations the array should be made private.

Which programming languages are affected by Array Declared Public, Final, and Static?+

CWE-582 commonly affects Java. 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-582 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.

CWE-582: Array Declared Public, Final, and Static

Extended Description

Technical Details

Applicable To

Security Consequences

Scope

Impact

Mitigation Strategies

Phase

Description

Detection Methods

Code Examples & CVEs

Demonstrative Examples

CWE Relationships

Parent Weaknesses