Applicable Platforms
Language
Class: Not Language-Specific (Undetermined)
Common Consequences
Scope |
Impact |
Likelihood |
Availability | DoS: Resource Consumption (CPU), DoS: Resource Consumption (Memory), DoS: Amplification
Note: An infinite loop will cause unexpected consumption of resources, such as CPU cycles or memory. The software's operation may slow down, or cause a long time to respond. | |
Observed Examples
References |
Description |
| Chain: an operating system does not properly process malformed Open Shortest Path First (OSPF) Type/Length/Value Identifiers (TLV) (CWE-703), which can cause the process to enter an infinite loop (CWE-835) |
| A Python machine communication platform did not account for receiving a malformed packet with a null size, causing the receiving function to never update the message buffer and be caught in an infinite loop. |
| Chain: off-by-one error (CWE-193) leads to infinite loop (CWE-835) using invalid hex-encoded characters. |
| Chain: self-referential values in recursive definitions lead to infinite loop. |
| NULL UDP packet is never cleared from a queue, leading to infinite loop. |
| Chain: web browser crashes due to infinite loop - "bad
looping logic [that relies on] floating point math [CWE-1339] to exit
the loop [CWE-835]" |
| Floating point conversion routine cycles back and forth between two different values. |
| Floating point conversion routine cycles back and forth between two different values. |
| Chain: improperly clearing a pointer in a linked list leads to infinite loop. |
| Chain: an integer overflow (CWE-190) in the image size calculation causes an infinite loop (CWE-835) which sequentially allocates buffers without limits (CWE-1325) until the stack is full. |
| Chain: A denial of service may be caused by an uninitialized variable (CWE-457) allowing an infinite loop (CWE-835) resulting from a connection to an unresponsive server. |
Vulnerability Mapping Notes
Justification : 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.
Comment : 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-62
The Art of Software Security Assessment
Mark Dowd, John McDonald, Justin Schuh.
REF-962
Automated Source Code Security Measure (ASCSM)
Object Management Group (OMG).
http://www.omg.org/spec/ASCSM/1.0/
Submission
Name |
Organization |
Date |
Date release |
Version |
CWE Content Team |
MITRE |
2011-03-22 +00:00 |
2011-03-30 +00:00 |
1.12 |
Modifications
Name |
Organization |
Date |
Comment |
CWE Content Team |
MITRE |
2011-06-01 +00:00 |
updated Common_Consequences, Relationships, Taxonomy_Mappings |
CWE Content Team |
MITRE |
2012-05-11 +00:00 |
updated Demonstrative_Examples, References, Relationships, Taxonomy_Mappings |
CWE Content Team |
MITRE |
2017-11-08 +00:00 |
updated Demonstrative_Examples |
CWE Content Team |
MITRE |
2019-01-03 +00:00 |
updated References, Relationships, Taxonomy_Mappings |
CWE Content Team |
MITRE |
2019-06-20 +00:00 |
updated Relationships |
CWE Content Team |
MITRE |
2020-02-24 +00:00 |
updated Relationships |
CWE Content Team |
MITRE |
2020-08-20 +00:00 |
updated Relationships |
CWE Content Team |
MITRE |
2020-12-10 +00:00 |
updated Observed_Examples, Relationships |
CWE Content Team |
MITRE |
2021-03-15 +00:00 |
updated Observed_Examples |
CWE Content Team |
MITRE |
2021-07-20 +00:00 |
updated Observed_Examples |
CWE Content Team |
MITRE |
2023-01-31 +00:00 |
updated Description, Observed_Examples |
CWE Content Team |
MITRE |
2023-04-27 +00:00 |
updated Relationships |
CWE Content Team |
MITRE |
2023-06-29 +00:00 |
updated Mapping_Notes |
CWE Content Team |
MITRE |
2023-10-26 +00:00 |
updated Observed_Examples |
CWE Content Team |
MITRE |
2024-02-29 +00:00 |
updated Demonstrative_Examples |
CWE Content Team |
MITRE |
2024-11-19 +00:00 |
updated Description, Diagram |