CWE-1058
Invokable Control Element in Multi-Thread Context with non-Final Static Storable or Member Element
Incomplete
2019-01-03 00:00 +00:00
2023-06-29 00:00 +00:00
Alerte pour un CWE
Restez informé de toutes modifications pour un CWE spécifique.
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.
Extended Description
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.
Informations
Common Consequences
| Scope | Impact | Likelihood |
|---|---|---|
| Other | Reduce Reliability |
Vulnerability Mapping Notes
Rationale : This CWE entry is at the Base level of abstraction, which is a preferred level of abstraction for mapping to the root causes of vulnerabilities.Comments : Carefully read both the name and description to ensure that this mapping is an appropriate fit. Do not try to 'force' a mapping to a lower-level Base/Variant simply to comply with this preferred level of abstraction.
References
REF-961
Automated Source Code Reliability Measure (ASCRM)Object Management Group (OMG).
http://www.omg.org/spec/ASCRM/1.0/
Submission
| Name | Organization | Date | Date Release | Version |
|---|---|---|---|---|
| CWE Content Team | MITRE | 3.2 |
Modifications
| Name | Organization | Date | Comment |
|---|---|---|---|
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Description | |
| CWE Content Team | MITRE | updated Relationships | |
| CWE Content Team | MITRE | updated Mapping_Notes |
2024©
tesweb SA
