Extended Description
Extended Description
Technical Details
- Structure
- Simple
- Vulnerability Mapping
- ALLOWED
Applicable To
Security Consequences
Scope
Impact
Mitigation Strategies
Phase
Description
Use the start() method instead of the run() method.
Detection Methods
No detection method information available for this CWE.
Code Examples & CVEs
No examples or observed CVEs available for this CWE.
CWE Relationships
No relationship information available for this CWE.
Frequently Asked Questions
What is CWE-572: CWE-572: Call to Thread run() instead of start()?+
CWE-572: CWE-572: Call to Thread run() instead of start() is a Common Weakness Enumeration (CWE) entry maintained by MITRE. Description Extended Description
What are the security consequences of CWE-572: Call to Thread run() instead of start()?+
If exploited, CWE-572 (CWE-572: Call to Thread run() instead of start()) it can compromise Quality Degradation and Varies by Context, leading to outcomes such as Scope: Other.
How do you prevent or mitigate CWE-572: Call to Thread run() instead of start()?+
Recommended mitigations for CWE-572 include: Use the start() method instead of the run() method.
Which programming languages are affected by CWE-572: Call to Thread run() instead of start()?+
CWE-572 commonly affects Languages. 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-572 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.