CWE-511: Logic/Time Bomb

BaseIncomplete

The product contains code that is designed to disrupt the legitimate operation of the product (or its environment) when a certain time passes, or when a certain logical condition is met.

View on MITRE
Back to CWE Lookup

Extended Description

When the time bomb or logic bomb is detonated, it may perform a denial of service such as crashing the system, deleting critical data, or degrading system response time. This bomb might be placed within either a replicating or non-replicating Trojan horse.

Technical Details

Structure
Simple
Vulnerability Mapping
ALLOWED

Applicable To

Languages
Not Language-Specific
Platforms

Source-backed guidance

Additional facts reviewed against primary or authoritative security sources.

Verify controls for CWE-511 with SSDF evidence

Use NIST SSDF verification and vulnerability-response practices to detect CWE-511, Logic/Time Bomb, 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 Logic/Time Bomb during Installation

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

CWE-511: Logic/Time Bomb — MITRE CWE

Triage CWE-511 against known exploitation evidence

Use CISA's Known Exploited Vulnerabilities catalog to test whether a vulnerability mapped to CWE-511, Logic/Time Bomb, 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-511

Apply MITRE's full root-cause mapping guidance when using CWE-511, Logic/Time Bomb. 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-511 with root-cause mapping checks

Apply MITRE's root-cause mapping quick tips to CWE-511, Logic/Time Bomb. 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-511: Logic/Time Bomb?+

CWE-511: Logic/Time Bomb is a Common Weakness Enumeration (CWE) entry maintained by MITRE. The product contains code that is designed to disrupt the legitimate operation of the product (or its environment) when a certain time passes, or when a certain logical condition is met. When the time bomb or logic bomb is detonated, it may perform a denial of service such as crashing the system, deleting critical data, or degrading system response time. This bomb might be placed within either a replicating or non-replicating Trojan horse.

What are the security consequences of Logic/Time Bomb?+

If exploited, CWE-511 (Logic/Time Bomb) it can compromise Other and Integrity, leading to outcomes such as Varies by Context and Alter Execution Logic.

How do you prevent or mitigate Logic/Time Bomb?+

Recommended mitigations for CWE-511 include: Always verify the integrity of the product that is being installed.

How is Logic/Time Bomb detected?+

CWE-511 can be detected using Automated Static Analysis. Combining automated tooling with manual review typically yields the best coverage.

Which programming languages are affected by Logic/Time Bomb?+

CWE-511 commonly affects Not Language-Specific. 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-511 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.

Learn More

Find Related CVEs

Search for vulnerabilities that exploit CWE-511

CVE vs CWE: What's the Difference?

Understanding vulnerabilities vs weaknesses

Understanding CVSS Scoring

How vulnerability severity is measured

View Full MITRE Entry

Complete technical details and references

Advertisement