CWE-839
Numeric Range Comparison Without Minimum Check
Description
The product checks a value to ensure that it is less than or equal to a maximum, but it does not also verify that the value is greater than or equal to the minimum.
{"xhtml:p":["Some products use signed integers or floats even when their values are only expected to be positive or 0. An input validation check might assume that the value is positive, and only check for the maximum value. If the value is negative, but the code assumes that the value is positive, this can produce an error. The error may have security consequences if the negative value is used for memory allocation, array access, buffer access, etc. Ultimately, the error could lead to a buffer overflow or other type of memory corruption.","The use of a negative number in a positive-only context could have security implications for other types of resources. For example, a shopping cart might check that the user is not requesting more than 10 items, but a request for -3 items could cause the application to calculate a negative price and credit the attacker's account."]}
Parent Weaknesses (ChildOf)
Common Consequences
Scope
Impact
Modify Application Data, Execute Unauthorized Code or Commands
Scope
Impact
DoS: Resource Consumption (Other)
Scope
Impact
Modify Memory, Read Memory
Potential Mitigations
If the number to be used is always expected to be positive, change the variable type from signed to unsigned or size_t.
If the number to be used could have a negative value based on the specification (thus requiring a signed value), but the number should only be positive to preserve code correctness, then include a check to ensure that the value is positive.
CVE-2010-1866Chain: integer overflow (CWE-190) causes a negative signed value, which later bypasses a maximum-only check (CWE-839), leading to heap-based buffer overflow (CWE-122).
CVE-2009-1099Chain: 16-bit counter can be interpreted as a negative value, compared to a 32-bit maximum value, leading to buffer under-write.
CVE-2011-0521Chain: kernel's lack of a check for a negative value leads to memory corruption.
CVE-2010-3704Chain: parser uses atoi() but does not check for a negative value, which can happen on some platforms, leading to buffer under-write.
CVE-2010-2530Chain: Negative value stored in an int bypasses a size check and causes allocation of large amounts of memory.
CVE-2009-3080Chain: negative offset value to IOCTL bypasses check for maximum index, then used as an array index for buffer under-read.
CVE-2008-6393chain: file transfer client performs signed comparison, leading to integer overflow and heap-based buffer overflow.
CVE-2008-4558chain: negative ID in media player bypasses check for maximum index, then used as an array index for buffer under-read.
Applicable Platforms
Security Training
Train your team to recognize and prevent security threats with our comprehensive security awareness program.
Start TrainingVulnerability Scanning
Discover vulnerabilities in your applications and infrastructure before attackers do.
Scan Now