Weakness (CWE)
CWE-128: Wrap-around Error
Wrap around errors occur whenever a value is incremented past the maximum value for its type and therefore "wraps around" to a very small, negative, or undefined value.
How to prevent it (3 mitigations)
-
Requirements specification: The choice could be made to use a language that is not susceptible to these issues.
-
Architecture and Design
Provide clear upper and lower bounds on the scale of any protocols designed.
-
Implementation
Perform validation on all incremented variables to ensure that they remain within reasonable bounds.
Source: MITRE CWE-128
5 results · Feed
-
Medium 5.8
Multiple Cisco Products Snort 3 Generic Routing Encapsulation Denial of Service Vulnerabilities
Multiple Cisco products are affected by a vulnerability in the Snort 3 Generic Routing Encapsulation (GRE) Detection Engine that could allow an unauthenticated, remote attacker to cause the Snort 3 Detection Engine to restart, resulting in an interruption of …
-
High 8.8
Vulnerabilities in IBM AIX and PowerVM VIOS
IBM AIX 7.2, and 7.3 and IBM PowerVM VIOS 4.1 could allow a remote attacker to execute arbitrary code due to an off-by-one error in bounds checking.
-
Low 2.0
concurrent-ruby: `ReentrantReadWriteLock` read-count overflow grants a write lock without exclusivity
concurrent-ruby is a modern concurrency tools for Ruby. Prior to 1.3.7, Concurrent::ReentrantReadWriteLock can incorrectly grant a write lock after one thread acquires the read lock 32,768 times. The lock stores a thread's local read and write hold counts in …
-
High 8.8
Wrap-around error in Linux kernel mode driver for some Intel(R) Ethernet Network Controllers and Adapters before versio…
-
Unscored —
An unauthenticated attacker can cause a denial-of-service to the following products: Ivanti Connect Secure (ICS) in ver…