Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

CWE-190 (整数溢出或超界折返) — Vulnerability Class 817

817 vulnerabilities classified as CWE-190 (整数溢出或超界折返). AI Chinese analysis included.

CWE-190 represents a critical logic flaw where arithmetic operations exceed the maximum capacity of the assigned integer data type, causing the value to wrap around to a negative number or zero. Attackers typically exploit this vulnerability by manipulating input values to trigger the overflow, thereby bypassing security checks that assume the resulting number remains positive or within expected bounds. This often leads to severe consequences such as buffer overflows, memory corruption, or unauthorized access. To prevent such issues, developers must implement rigorous input validation and use safe arithmetic libraries that detect potential overflows before execution. Additionally, employing static analysis tools and adhering to secure coding standards ensures that integer calculations are handled with appropriate bounds checking, effectively mitigating the risk of wraparound errors in production environments.

MITRE CWE Description
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Common Consequences (5)
AvailabilityDoS: Crash, Exit, or Restart, DoS: Resource Consumption (Memory), DoS: Instability
This weakness can generally lead to undefined behavior and therefore crashes. When the calculated result is used for resource allocation, this weakness can cause too many (or too few) resources to be allocated, possibly enabling crashes if the product requests more resources than can be provided.
IntegrityModify Memory
If the value in question is important to data (as opposed to flow), simple data corruption has occurred. Also, if the overflow/wraparound results in other conditions such as buffer overflows, further memory corruption may occur.
Confidentiality, Availability, Access ControlExecute Unauthorized Code or Commands, Bypass Protection Mechanism
This weakness can sometimes trigger buffer overflows, which can be used to execute arbitrary code. This is usually outside the scope of the product's implicit security policy.
Availability, OtherAlter Execution Logic, DoS: Crash, Exit, or Restart, DoS: Resource Consumption (CPU)
If the overflow/wraparound occurs in a loop index variable, this could cause the loop to terminate at the wrong time - too early, too late, or not at all (i.e., infinite loops). With too many iterations, some loops could consume too many resources such as memory, file handles, etc., possibly leading…
Access ControlBypass Protection Mechanism
If integer values are used in security-critical decisions, such as calculating quotas or allocation limits, integer overflows can be used to cause an incorrect security decision.
Mitigations (5)
RequirementsEnsure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
RequirementsUse a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482]. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
ImplementationPerform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range. Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum…
ImplementationUnderstand the programming language's underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, "not-a-number" calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]…
Examples (2)
The following image processing code allocates a table for images.
img_t table_ptr; /*struct containing img data, 10kB each*/ int num_imgs; ... num_imgs = get_num_imgs(); table_ptr = (img_t*)malloc(sizeof(img_t)*num_imgs); ...
Bad · C
The following code excerpt from OpenSSH 3.3 demonstrates a classic case of integer overflow:
nresp = packet_get_int(); if (nresp > 0) { response = xmalloc(nresp*sizeof(char*)); for (i = 0; i < nresp; i++) response[i] = packet_get_string(NULL); }
Bad · C
CVE IDTitleCVSSSeverityPublished
CVE-2023-4398 Zyxel ATP 输入验证错误漏洞 — ATP series firmware 7.5 High2023-11-28
CVE-2021-27504 Texas Instruments FREERTOS Integer Overflow or Wraparound — CC32XX 7.4 High2023-11-21
CVE-2021-27502 Texas Instruments TI-RTOS Integer Overflow or Wraparound — CC32XX 7.4 High2023-11-21
CVE-2023-4424 bt: hci: DoS and possible RCE — Zephyr 8.3 High2023-11-21
CVE-2021-22636 Texas Instruments TI-RTOS Integer Overflow or Wraparound — CC32XX 7.4 High2023-11-20
CVE-2021-27429 Texas Instruments TI-RTOS Integer Overflow or Wraparound — CC32XX 7.4 High2023-11-20
CVE-2023-48233 overflow with count for :s command in vim — vim 2.8 Low2023-11-16
CVE-2023-48234 overflow in nv_z_get_count in vim — vim 2.8 Low2023-11-16
CVE-2023-48235 overflow in ex address parsing in vim — vim 2.8 Low2023-11-16
CVE-2023-48236 overflow in get_number in vim — vim 2.8 Low2023-11-16
CVE-2023-48237 overflow in shift_line in vim — vim 2.8 Low2023-11-16
CVE-2023-36395 Windows Deployment Services Denial of Service Vulnerability — Windows Server 2019 7.5 High2023-11-14
CVE-2023-36401 Microsoft Remote Registry Service Remote Code Execution Vulnerability — Windows 10 Version 1809 7.2 High2023-11-14
CVE-2023-4295 Mali GPU Kernel Driver allows improper GPU memory processing operations — Valhall GPU Kernel Driver 7.8 -2023-11-07
CVE-2023-38127 JustSystems Ichitaro 输入验证错误漏洞 — Ichitaro 2023 7.8 High2023-10-19
CVE-2023-42752 Kernel: integer overflow in igmpv3_newpack leading to exploitable memory access — Kernel 5.5 Medium2023-10-13
CVE-2023-35966 Yifan YF325 缓冲区错误漏洞 — YF325 9.8 Critical2023-10-11
CVE-2023-35968 Yifan YF325 缓冲区错误漏洞 — YF325 9.8 Critical2023-10-11
CVE-2023-35967 Yifan YF325 缓冲区错误漏洞 — YF325 9.8 Critical2023-10-11
CVE-2023-35965 Yifan YF325 缓冲区错误漏洞 — YF325 9.8 Critical2023-10-11
CVE-2023-36576 Windows Kernel Information Disclosure Vulnerability — Windows 10 Version 1809 5.5 Medium2023-10-10
CVE-2023-36582 Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability — Windows 10 Version 1809 7.3 High2023-10-10
CVE-2023-36593 Microsoft Message Queuing (MSMQ) Remote Code Execution Vulnerability — Windows 10 Version 1809 7.8 High2023-10-10
CVE-2023-36478 HTTP/2 HPACK integer overflow and buffer allocation — jetty.project 7.5 High2023-10-10
CVE-2023-41175 Libtiff: potential integer overflow in raw2tiff.c 6.5 Medium2023-10-05
CVE-2023-40745 Libtiff: integer overflow in tiffcp.c 6.5 Medium2023-10-05
CVE-2023-36792 Visual Studio Remote Code Execution Vulnerability — Microsoft Visual Studio 2017 version 15.9 (includes 15.0 - 15.8) 7.8 High2023-09-12
CVE-2023-38142 Windows Kernel Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2023-09-12
CVE-2023-38150 Windows Kernel Elevation of Privilege Vulnerability — Windows 11 version 21H2 7.8 High2023-09-12
CVE-2023-28831 SIMATIC Cloud Connect 输入验证错误漏洞 — SIMATIC BRAUMAT 7.5 High2023-09-12

Vulnerabilities classified as CWE-190 (整数溢出或超界折返) represent 817 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.