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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

3513 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-85769 Libtpms: libtpms: heap out-of-bounds read in tpm2 state unmarshalling via unchecked block_skip_read() blocksize — Red Hat Enterprise Linux 10 6.5 Medium 2026-09-04
CVE-2026-16660 IBM Db2 Mirror for i is affected by multiple vulnerabilities [, , ] — Db2 Mirror for i 5.3 Medium 2026-09-04
CVE-2026-85698 Turso through 0.8.0-pre.8 Out-of-Bounds Read Denial of Service — turso 5.5 Medium 2026-09-04
CVE-2026-85522 valkey-io valkey Slot Migration cluster_migrateslots.c createSlotImportJob out-of-bounds — valkey 5.3 Medium 2026-09-04
CVE-2026-85505 FreeIPMI 1.6.19前ipmi-oem栈缓冲区越界读 — FreeIPMI 7.5 High 2026-09-04
CVE-2026-49509 SAMSUNG rlottie 缓冲区错误漏洞 — rLottie 4.4 Medium 2026-09-03
CVE-2026-85455 MOOS core-moos through 10.4.0 MOOSDB Out-of-Bounds Read via Short Packet — core-moos 8.2 High 2026-09-03
CVE-2026-85444 MOOS-IvP through 24.8.1 Out-of-Bounds Read in isBraced, isQuoted and isChevroned — moos-ivp 7.5 High 2026-09-03
CVE-2026-64200 Out Of Bounds Read in during string conversionwhen parsing a .DSB file in DASYLab — DASYLab 7.8 High 2026-09-03
CVE-2026-64199 Out Of Bounds Read outside the bounds of an allocated data structure when parsing a .DSB file in DASYLab — DASYLab 7.8 High 2026-09-03
CVE-2026-64198 Out Of Bounds Read in file handling when parsing a .DSB file in DASYLab — DASYLab 7.8 High 2026-09-03
CVE-2026-85052 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-09-03
CVE-2026-84968 Heap out-of-bounds read via corrupt nested BSON in field path error message — PHP Driver 5.3 Medium 2026-09-03
CVE-2026-71222 Gfs2-utils: gfs2-utils: heap out-of-bounds read via unchecked ea_num_ptrs in extended attribute processing — Red Hat Enterprise Linux 7 5.3 Medium 2026-09-03
CVE-2026-85090 FreeRDP before 3.31.0 Heap Out-of-Bounds Read via AVC444 — FreeRDP 5.4 Medium 2026-09-03
CVE-2026-84484 ION-DTN before 4.2.0 Out-of-Bounds Read via decodeSdnv — ION-DTN 7.5 High 2026-09-02
CVE-2026-84270 Gvfs: mtp: out-of-bounds read in do_read() — gvfs 4.3 Medium 2026-09-01
CVE-2026-82618 Systerel S2OPC String Array Range Writing sopc_builtintypes.c set_range_matrix_on_string_array out-of-bounds — S2OPC 4.3 Medium 2026-08-31
CVE-2026-82608 Kamailio AVP cxdx_avp.c get_4bytes out-of-bounds — Kamailio 7.4 High 2026-08-31
CVE-2026-82330 Gimp: heap out-of-bounds read in pvr vq (compressed) decoder due to missing bounds check — GIMP 6.1 Medium 2026-08-28
CVE-2026-82328 Gimp: heap out-of-bounds read in ico loader via unvalidated used_clrs palette count — GIMP 6.1 Medium 2026-08-28
CVE-2026-82324 Gimp: heap out-of-bounds reads in iff/ilbm loader from ham row size mismatch and nplanes=0 — GIMP 6.1 Medium 2026-08-28
CVE-2026-40015 Open-Xchange Dovecot Pro 缓冲区错误漏洞 — OX Dovecot Pro 4.3 Medium 2026-08-28
CVE-2026-19315 Fireware OS Pre-Authentication Type Confusion in iked Allows Remote Code Execution — Fireware OS 9.3 Critical 2026-08-27
CVE-2026-19317 Fireware OS Pre-Authentication Out-of-Bounds Read in iked Allows Denial of Service (DoS) — Fireware OS 8.7 High 2026-08-27
CVE-2026-78009 Fireware OS Out-of-Bounds Read in iked Allows Unauthenticated Denial of Service (DoS) — Fireware OS 8.7 High 2026-08-27
CVE-2026-82072 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-08-27
CVE-2026-34616 DNG SDK | Out-of-bounds Read (CWE-125) — Adobe DNG Software Development Kit (SDK) 5.5 Medium 2026-08-27
CVE-2026-71402 wicked: out-of-bounds read in the DHCPv4 option parser due to payload length taken from the IP total length — wicked 5.4 Medium 2026-08-27
CVE-2026-81334 darknet through 6.0 Out-of-Bounds Read and Write via Unchecked Layer Index in .cfg Parser — darknet 6.1 Medium 2026-08-27

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