Run static analysis (SAST) on the codebase looking for the unsafe pattern in the data flow.
CWE-582 Variant Draft
Array Declared Public, Final, and Static
This vulnerability occurs when an array is declared as public, final, and static, which does not protect the data inside the array from being altered.
Definition
What is CWE-582?
This vulnerability occurs when an array is declared as public, final, and static, which does not protect the data inside the array from being altered.
While the `final` keyword ensures the array reference itself cannot point to a new object, it does not lock the contents of the array. The array elements remain fully mutable, meaning their values can be changed, added, or removed.
Because the array is also declared `public`, any part of the code—including potentially untrusted or malicious components—can directly access and modify the array's data. This combination of public exposure with insufficient data protection typically represents a security flaw or design oversight that should be corrected.
Real-world impact
Real-world CVEs caused by CWE-582
No public CVE references are linked to this CWE in MITRE's catalog yet.
How attackers exploit it
Step-by-step attacker path
- 1
Identify a code path that handles untrusted input without validation.
- 2
Craft a payload that exercises the unsafe behavior — injection, traversal, overflow, or logic abuse.
- 3
Deliver the payload through a normal request and observe the application's reaction.
- 4
Iterate until the response leaks data, executes attacker code, or escalates privileges.
Vulnerable code example
Vulnerable Java
The following Java Applet code mistakenly declares an array public, final and static.
public final class urlTool extends Applet {
public final static URL[] urls;
...
} Secure code example
Secure pseudo
// Validate, sanitize, or use a safe API before reaching the sink.
function handleRequest(input) {
const safe = validateAndEscape(input);
return executeWithGuards(safe);
} What changed: the unsafe sink is replaced (or the input is validated/escaped) so the same payload no longer triggers the weakness.
Prevention checklist
How to prevent CWE-582
- Implementation In most situations the array should be made private.
Detection signals
How to detect CWE-582
Run dynamic application security testing against the live endpoint.
Watch runtime logs for unusual exception traces, malformed input, or authorization bypass attempts.
Code review: flag any new code that handles input from this surface without using the validated framework helpers.
CWE-582
Don't catalog this weakness. Prove it's reachable.
Plexicus turns CWE catalogs into evidence: every CWE-pattern is matched against your real code graph, reach is proven on a sandbox clone, and verified findings ship as reviewed PRs.
Frequently asked questions What is CWE-582?
How serious is CWE-582?
What languages or platforms are affected by CWE-582?
How can I prevent CWE-582?
How does Plexicus detect and fix CWE-582?
Where can I learn more about CWE-582?
Frequently asked questions
What is CWE-582?
This vulnerability occurs when an array is declared as public, final, and static, which does not protect the data inside the array from being altered.
How serious is CWE-582?
MITRE has not published a likelihood-of-exploit rating for this weakness. Treat it as medium-impact until your threat model proves otherwise.
What languages or platforms are affected by CWE-582?
MITRE lists the following affected platforms: Java.
How can I prevent CWE-582?
In most situations the array should be made private.
How does Plexicus detect and fix CWE-582?
Plexicus's SAST engine matches the data-flow signature for CWE-582 on every commit. When a match is found, our Codex Remedium agent opens a fix PR with the corrected code, tests, and a one-line summary for the reviewer.
Where can I learn more about CWE-582?
MITRE publishes the canonical definition at https://cwe.mitre.org/data/definitions/582.html. You can also reference OWASP and NIST documentation for adjacent guidance.
Related weaknesses
Weaknesses related to CWE-582
CWE-668 Parent
Exposure of Resource to Wrong Sphere
This vulnerability occurs when an application unintentionally makes a resource accessible to users or systems that should not have…
CWE-1189 Sibling
Improper Isolation of Shared Resources on System-on-a-Chip (SoC)
This vulnerability occurs when a System-on-a-Chip (SoC) fails to properly separate shared hardware resources between secure (trusted) and…
CWE-1282 Sibling
Assumed-Immutable Data is Stored in Writable Memory
This vulnerability occurs when data that should be permanent and unchangeable—like a bootloader, device IDs, or one-time configuration…
CWE-1327 Sibling
Binding to an Unrestricted IP Address
This vulnerability occurs when software or a service is configured to bind to the IP address 0.0.0.0 (or :: in IPv6), which acts as a…
CWE-1331 Sibling
Improper Isolation of Shared Resources in Network On Chip (NoC)
This vulnerability occurs when a Network on Chip (NoC) fails to properly separate its internal, shared resources—like buffers, switches,…
CWE-134 Sibling
Use of Externally-Controlled Format String
This vulnerability occurs when a program uses a format string from an untrusted, external source (like user input, a network packet, or a…
CWE-200 Sibling
Exposure of Sensitive Information to an Unauthorized Actor
This weakness occurs when an application unintentionally reveals sensitive data to someone who shouldn't have access to it.
CWE-374 Sibling
Passing Mutable Objects to an Untrusted Method
This vulnerability occurs when a function receives a direct reference to mutable data, such as an object or array, instead of a safe copy…
CWE-375 Sibling
Returning a Mutable Object to an Untrusted Caller
This vulnerability occurs when a method directly returns a reference to its internal mutable data, allowing untrusted calling code to…
Ready to validate what matters?
Ready to validate what matters?
Plexicus is Proof-Driven AppSec: validated findings, contextual understanding, and reviewed remediation — anchored in evidence, scoped with you.