CWE-1058: Invokable Control Element in Multi-Thread… | Glexia
CWE-1058 (Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element) weakness overview with consequences, detection…
Glexia's Take · Automated analysis
CWE-1058: Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Executive Impact
- Other: Reduce Reliability: This issue can prevent the product from running reliably. If the relevant code is reachable by an attacker, then this reliability problem might introduce a vulnerability.
Developer Pattern
CWE-1058 is the kind of defect developers can usually prevent with explicit validation, safer framework defaults, and tests that exercise hostile input or unsafe state transitions.
Automation confidence
high confidence from CWE-1058, 4.20.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Official CWE Definition
CWE-1058: Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
The code contains a function or method that operates in a multi-threaded environment but owns an unsafe non-final static storable or member data element.
Developer And Remediation Guidance
How teams prevent and detect this weakness
Causes
- Missing validation
- Unsafe defaults
- Insufficient authorization or memory-safety invariant
Remediation
- Use safe APIs
- Centralize the control
- Add regression tests
- Review logs and telemetry for attempted abuse
Detection
- Code review
- SAST
- DAST
- Focused regression tests
Mappings
Related CVEs, CWEs, and ATT&CK context
Related CWEs
ATT&CK Relevance
ATT&CK relevance is shown only when reviewed or responsibly inferred.