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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

4337 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-111142 Zziplib through 0.13.80 Out-of-Bounds Read via zzip_disk_findfirst — zziplib 5.5 Medium 2026-10-15
CVE-2026-111141 zziplib through 0.13.80 Out-of-Bounds Read via __zzip_parse_root_directory ZIP64 Parsing — zziplib 4.7 Medium 2026-10-15
CVE-2026-111140 libregf through 20260526 Heap Out-of-Bounds Read via libregf_value_item_read_value_data — libregf 6.1 Medium 2026-10-15
CVE-2026-111139 NetSurf libnsbmp through 0.1.7 Out-of-Bounds Read via bmp_decode_mask — libnsbmp 5.5 Medium 2026-10-15
CVE-2026-111138 NetSurf libnsbmp through 0.1.7 Out-of-Bounds Read in RLE8 and RLE4 Decoders — libnsbmp 5.5 Medium 2026-10-15
CVE-2026-111135 libfwsi through 20260522 Heap Out-of-Bounds Read via libfwsi_mtp_volume_values_read_data — libfwsi 6.1 Medium 2026-10-15
CVE-2026-111133 libfsapfs through 20260921 Heap Out-of-Bounds Read via libfsapfs_key_encrypted_key_read_data — libfsapfs 6.1 Medium 2026-10-15
CVE-2026-111134 libfwsi through 20260522 Heap Out-of-Bounds Read via libfwsi_mtp_file_entry_values_read_data — libfwsi 6.1 Medium 2026-10-15
CVE-2026-111132 GNOME libgxps through 0.3.2 Heap Out-of-Bounds Read via path_geometry_start_element — libgxps 6.1 Medium 2026-10-15
CVE-2026-111130 OpenSlide through 4.0.1 Heap Out-of-Bounds Read via MIRAX get_tile_position — openslide 6.1 Medium 2026-10-15
CVE-2026-111131 libxmp through 4.7.4 Stack Out-of-Bounds Read via P61A Depacker — libxmp 6.1 Medium 2026-10-15
CVE-2026-111127 catdoc through 0.95 Out-of-Bounds Read via xls2csv copy_unicode_string — catdoc 6.1 Medium 2026-10-15
CVE-2026-111126 catdoc through 0.95 Out-of-Bounds Read in xls2csv MULRK Record Handler — catdoc 6.1 Medium 2026-10-15
CVE-2026-111125 CFITSIO through 4.7.0 Heap Out-of-Bounds Read via HCOMPRESS input_nnybble — cfitsio 6.1 Medium 2026-10-15
CVE-2026-111124 CFITSIO through 4.7.0 Heap Out-of-Bounds Read via Negative ZDITHER0 Seed — cfitsio 6.1 Medium 2026-10-15
CVE-2026-110876 AdPlug through 2.4 Out-of-Bounds Read via CxsmPlayer::play_note in XSM Files — adplug 5.5 Medium 2026-10-15
CVE-2026-110877 AdPlug through 2.4 Heap Out-of-Bounds Read via CdmoLoader::load — adplug 5.5 Medium 2026-10-15
CVE-2026-79843 HPE NonStop SQL/MX EXE - out-of-bounds read vulnerability — HPE NonStop SQL/MX EXE 6.5 Medium 2026-10-15
CVE-2026-101290 CVE-2026-101290 — Sick_Safetyscanners_Base CPP Driver 7.5 High 2026-10-15
CVE-2026-76667 HPE NonStop EXPAND - Out-of-Bounds memory read vulnerability — HPE NonStop EXPAND 5.7 Medium 2026-10-15
CVE-2026-76666 HPE NonStop EXPAND - Out-of-Bounds memory read — HPE NonStop EXPAND 4.7 Medium 2026-10-15
CVE-2026-76665 HPE NonStop EXPAND - Buffer Overflow vulnerability — HPE NonStop EXPAND 7.1 High 2026-10-15
CVE-2026-76664 HPE NonStop EXPAND - Out-of-Bounds memory read/write — HPE NonStop EXPAND 6.4 Medium 2026-10-15
CVE-2026-110810 ggml-org whisper.cpp Model Loader whisper_model_load out-of-bounds — whisper.cpp 2.8 Low 2026-10-15
CVE-2026-110694 OAID Tengine tmfile Model Loader tm2_serializer.c get_tm_file_model out-of-bounds — Tengine 6.3 Medium 2026-10-14
CVE-2026-110679 OpenSIPS rtpproxy rtpproxy_answer out-of-bounds — OpenSIPS 7.3 High 2026-10-14
CVE-2026-73260 Mongoose: Out-of-bounds Read via length-counter underflow in built-in TLS X.509 DER parser — mongoose 7.5 High 2026-10-14
CVE-2026-106464 VxWorks 库TLS空签名解析致越界 — NetX Duo 8.7 High 2026-10-14
CVE-2026-102056 Junos OS and Junos OS Evolved: An attacker causes denial of service and information disclosure when Ethernet CFM is enabled — Junos OS 7.1 High 2026-10-14
CVE-2026-75085 Out-of-bounds read from received-frame length underflow in the STM32WBA IEEE 802.15.4 driver — zephyr 4.2 Medium 2026-10-14

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