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.
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| ChildOf | Allowed-with-Review | C | 506 | Embedded Malicious Code |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 904 | SFP Primary Cluster: Malware |
| MemberOf | Prohibited | C | 1412 | Comprehensive Categorization: Poor Coding Practices |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | BS | BOSS-294 | Not Language-Specific Weaknesses |
| MemberOf | Prohibited | BS | BOSS-306 | Mobile (technology class) Weaknesses |
| MemberOf | Prohibited | BS | BOSS-326 | Varies by Context (impact) |
| MemberOf | Prohibited | BS | BOSS-330 | Alter Execution Logic (impact) |
| Nature | Mapping | Type | ID | Name |
|---|---|---|---|---|
| MemberOf | Prohibited | C | 904 | SFP Primary Cluster: Malware |
| Scope | Likelihood | Impact | Note |
|---|---|---|---|
| OtherIntegrity | N/A | Varies by ContextAlter Execution Logic | N/A |
Always verify the integrity of the product that is being installed.
Conduct a code coverage analysis using live testing, then closely inspect any code that is not covered.
N/A
N/A
Typical examples of triggers include system date or time mechanisms, random number generators, and counters that wait for an opportunity to launch their payload. When triggered, a time-bomb may deny service by crashing the system, deleting files, or degrading system response-time.
| Reference | Description |
|---|
| Ordinality | Description |
|---|
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.
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.
| Taxonomy Name | Entry ID | Fit | Entry Name |
|---|---|---|---|
| Landwehr | N/A | N/A | Logic/Time Bomb |
| ID | Name |
|---|