CWE-572: Call to Thread run() instead of start()

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-572 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-572, Call to Thread run() instead of start(), 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 Call to Thread run() instead of start() during Implementation

MITRE associates mitigation with Implementation; documented detection approaches include Automated Static Analysis; recorded impacts include Quality Degradation, and Varies by Context. Use these source-defined anchors to turn CWE-572 into implementation, review, and verification checks for the affected component.

CWE-572: Call to Thread run() instead of start() — MITRE CWE

Triage CWE-572 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-572, Call to Thread run() instead of start(), 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-572

Apply MITRE's full root-cause mapping guidance when using CWE-572, Call to Thread run() instead of start(). 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-572 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-572, Call to Thread run() instead of start(). 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-572: Call to Thread run() instead of start()?+

CWE-572: Call to Thread run() instead of start() is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product calls a thread's run() method instead of calling start(), which causes the code to run in the thread of the caller instead of the callee. In most cases a direct call to a Thread object's run() method is a bug. The programmer intended to begin a new thread of control, but accidentally called run() instead of start(), so the run() method will execute in the caller's thread of control.

What are the security consequences of Call to Thread run() instead of start()?+

If exploited, CWE-572 (Call to Thread run() instead of start()) it can compromise Other, leading to outcomes such as Quality Degradation and Varies by Context.

How do you prevent or mitigate 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 Call to Thread run() instead of start()?+

CWE-572 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-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.

CWE-572: Call to Thread run() instead of start()

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