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

Goal: 1000 CNY · Raised: 1336 CNY

100%

CWE-125 (跨界内存读) — Vulnerability Class 3492

3492 vulnerabilities classified as CWE-125 (跨界内存读). AI Chinese analysis included.

CWE-125, Out-of-bounds Read, is a memory safety weakness where software accesses memory locations outside the designated buffer boundaries, either before its start or past its end. This vulnerability typically arises from insufficient bounds checking during array indexing or pointer arithmetic, allowing attackers to read sensitive data such as stack canaries, cryptographic keys, or internal application state. By leveraging this flaw, adversaries can achieve information disclosure or potentially facilitate further exploitation techniques like heap spraying. Developers mitigate this risk by implementing rigorous input validation, utilizing static analysis tools to detect unsafe memory access patterns, and adopting safer programming languages or libraries that enforce automatic bounds checking. Additionally, employing compiler protections like Address Sanitizer during development helps identify these errors early, ensuring that memory reads remain strictly within allocated limits to prevent unauthorized data exposure.

MITRE CWE Description
The product reads data past the end, or before the beginning, of the intended buffer.
Common Consequences (4)
Confidentiality Read Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
Confidentiality Bypass Protection Mechanism
Out-of-bounds memory could contain memory addresses or other information that can be used to bypass ASLR and other protection mechanisms in order to improve the reliability of exploiting a separate weakness for code execution.
Availability DoS: Crash, Exit, or Restart
An attacker could cause a segmentation fault or crash by causing memory to be read outside of the bounds of the buffer. This is especially likely when the code reads a variable amount of data and assumes that a sentinel exists to stop the read operation, such as a NUL in a string.
Other Varies by Context
The read operation could produce other undefined or unexpected results.
Mitigations (2)
Implementation Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. When performing input validation, consider all potentially relevant properties, including length, type of input, the full range…
Architecture and Design Use a language that provides appropriate memory abstractions.
Examples (2)
In the following code, the method retrieves a value from an array at a specific array index location that is given as an input parameter to the method
int getValueFromArray(int *array, int len, int index) { int value; // check that the array index is less than the maximum // length of the array if (index < len) { // get the value at the specified index of the array value = array[index]; } // if array index is invalid then output error message // and return value indicating error else { printf("Value is: %d\n", array[index]); value = -1; } return value; }
Bad · C
... // check that the array index is within the correct // range of values for the array if (index >= 0 && index < len) { ...
Good · C
In the following C/C++ example the method processMessageFromSocket() will get a message from a socket, placed into a buffer, and will parse the contents of the buffer into a structure that contains the message length and the message body. A for loop is used to copy the message body into a local character string which will be passed to another method for processing.
int processMessageFromSocket(int socket) { int success; char buffer[BUFFER_SIZE]; char message[MESSAGE_SIZE]; // get message from socket and store into buffer //Ignoring possibliity that buffer > BUFFER_SIZE if (getMessage(socket, buffer, BUFFER_SIZE) > 0) { // place contents of the buffer into message structure ExMessage *msg = recastBuffer(buffer); // copy message body into string for processing int index; for (index = 0; index < msg->msgLength; index++) { message[index] = msg->msgBody[index]; } message[index] = '\0'; // process message success = processMessage(message); } return success; }
Bad · C
CVE ID Title CVSS Severity Published
CVE-2026-20489 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset - - 2026-08-03
CVE-2026-20488 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset - - 2026-08-03
CVE-2026-20479 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset - - 2026-08-03
CVE-2026-10848 Out-of-bounds read in Zephyr OCPP 1.6 RPC message parser (parse_rpc_msg) — zephyr 7.0 High 2026-08-02
CVE-2026-67291 FreeRDP before 3.29.0 Heap Out-of-Bounds Read via GLYPH_FRAGMENT_ADD — FreeRDP 7.5 High 2026-08-01
CVE-2026-67306 FreeRDP before 3.29.0 Out-of-Bounds Read via Planar RLE — FreeRDP 5.4 Medium 2026-08-01
CVE-2026-66401 FreeRDP before 3.29.0 Out-of-Bounds Read via UVC H.264 — FreeRDP 2.1 Low 2026-08-01
CVE-2026-67301 FreeRDP before 3.29.0 Out-of-bounds Read via Polygon async message-proxy — FreeRDP 7.5 High 2026-08-01
CVE-2026-67290 FreeRDP before 3.29.0 Heap Out-of-Bounds Read via TSMF — FreeRDP 7.5 High 2026-08-01
CVE-2026-10773 Out-of-bounds read in DHCPv4 client message-type name lookup (net_dhcpv4_msg_type_name) — zephyr 5.4 Medium 2026-08-01
CVE-2026-62959 Coturn: Pre-authentication heap memory disclosure in ACME redirect (`try_acme_redirect`) — coturn 8.2 High 2026-07-31
CVE-2026-61893 MZ Automation lib60870 Out-of-bounds Read — lib60870 6.5 Medium 2026-07-30
CVE-2026-63033 MZ Automation lib60870 Out-of-bounds Read — lib60870 6.5 Medium 2026-07-30
CVE-2026-66720 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 6.5 Medium 2026-07-30
CVE-2026-66369 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 6.5 Medium 2026-07-30
CVE-2026-63550 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 6.5 Medium 2026-07-30
CVE-2026-65421 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 6.5 Medium 2026-07-30
CVE-2026-66364 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 6.5 Medium 2026-07-30
CVE-2026-66349 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 6.5 Medium 2026-07-30
CVE-2026-56758 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 6.5 Medium 2026-07-30
CVE-2026-66360 MZ Automation libiec61850 Out-of-bounds Read — libiec61850 7.5 High 2026-07-30
CVE-2026-55777 GoAccess: Out-of-bounds heap read in parse_ios() via crafted User-Agent leads to remote crash/DoS — goaccess 5.3 Medium 2026-07-30
CVE-2026-67550 re2: Out-of-bounds heap read in `exec`/`test`/`match` via attacker-influenced `lastIndex` on a non-ASCII subject → uncatchable process crash (DoS) — node-re2 5.7 Medium 2026-07-30
CVE-2026-58216 Samba: kpasswd service: kpasswd packet that contains malformed asn.1 might cause the server to access 6 bytes of unallocated memory leading server to crash — Red Hat Enterprise Linux 10 5.3 Medium 2026-07-30
CVE-2026-41703 Out-of-bounds read vulnerability — Cloud Foundation 7.6 High 2026-07-30
CVE-2026-16530 Pcp: pcp: remote denial of service and information leakage — Red Hat Enterprise Linux 10 6.5 Medium 2026-07-30
CVE-2026-17995 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-30
CVE-2026-17869 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-30
CVE-2026-17772 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-30
CVE-2026-17770 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-30

Vulnerabilities classified as CWE-125 (跨界内存读) represent 3492 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.