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-17745 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-30
CVE-2026-17701 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-30
CVE-2026-17678 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-30
CVE-2026-64685 ImageMagick: Heap Buffer Over-Read in BGR decoder due to mising end-of-file check — ImageMagick 5.3 Medium 2026-07-29
CVE-2026-10684 Out-of-bounds read in coredump shell when printing stored-dump target code — zephyr 3.0 Low 2026-07-29
CVE-2026-17550 DWG or DXF File Parsing Out-of-Bounds Read in Autodesk AutoCAD — AutoCAD 5.5 Medium 2026-07-29
CVE-2026-16465 DWG or DXF File Parsing Out-of-Bounds Read in Autodesk AutoCAD — AutoCAD 6.1 Medium 2026-07-29
CVE-2026-58160 Apache Traffic Server: Out-of-bounds reads while parsing DNS responses — Apache Traffic Server 6.5 Medium 2026-07-29
CVE-2026-50735 EnterpriseDB pglogical 缓冲区错误漏洞 — pglogical 6.1 Medium 2026-07-28
CVE-2026-17072 Gstreamer1-plugins-good: gst-plugins-good: 4-byte heap over-read in gst_matroska_parse_flac_stream_headers when parsing flac codec data in matroska containers — Red Hat Enterprise Linux 10 3.3 Low 2026-07-28
CVE-2026-66759 Gimp: out-of-bounds read in file-icns plugin causes information disclosure or crash on crafted icns images — GIMP 7.1 High 2026-07-27
CVE-2026-66731 facil.io 0.7.5 - 0.7.6 HTTP/1.1 Chunked Transfer Encoding Parser Crash DoS — facil.io 7.5 High 2026-07-27
CVE-2026-66729 facil.io 0.6.0 - 0.7.6 Integer Underflow DoS via Multipart MIME Body Parser — facil.io 7.5 High 2026-07-27
CVE-2026-17572 HDF5 SOHM List Index Heap Buffer Overflow — HDF5 5.5 Medium 2026-07-27
CVE-2026-15003 Binutils: gnu binutils: heap-buffer-overflow in linker leads to information disclosure and denial of service — Red Hat Hardened Images 5.6 Medium 2026-07-27
CVE-2026-17512 ggml-org whisper.cpp log_mel_spectrogram out-of-bounds — whisper.cpp 3.3 Low 2026-07-27
CVE-2026-58023 Apache Thrift: c_glib heap out-of-bounds read in transport leftover-bytes path — Apache Thrift 6.9 Medium 2026-07-27
CVE-2026-66337 Libsoup: libsoup: heap buffer over-read via integer underflow in soup_filter_input_stream_read_until() — Red Hat Enterprise Linux 10 6.5 Medium 2026-07-24
CVE-2026-66034 libssh2 Heap Out-of-Bounds Read via publickey subsystem — libssh2 7.5 High 2026-07-24
CVE-2026-55732 Loytec LINX firmware: Out-of-bounds Read in BACnet packet parsing (bacdt_datetime_to_tod) — LIP-ME20xC 8.7 High 2026-07-24
CVE-2026-56391 Out‑of‑bounds Read in GNU coreutils — coreutils 4.6 Medium 2026-07-24
CVE-2026-16002 Out-of-bounds Read in MZ Automation lib60870 — lib60870 8.2 High 2026-07-23
CVE-2026-65918 PyTorch torchvision GIF Decoder Out-of-bounds Heap Read — vision 7.1 High 2026-07-23
CVE-2026-16768 Gdk-pixbuf: out-of-bounds read in ico parser — gdk-pixbuf 5.3 Medium 2026-07-23
CVE-2026-13077 Out-of-Bounds Heap Read in BSON CodeWScope Element Parsing via Malformed BSONColumn Data — MongoDB Server 7.1 High 2026-07-22
CVE-2026-64833 FFmpeg 0.7.1 - 8.1.2 Out-of-Bounds Read via S/PDIF Muxer spdifenc.c — FFmpeg 7.1 High 2026-07-22
CVE-2026-48029 libheif: heap OOB read in ImageItem_Grid::decode_grid_tile via irot-induced tile-coordinate underflow — libheif 7.1 High 2026-07-22
CVE-2026-16473 Sbc: sbc: heap out-of-bounds read via crafted sbc audio frame — Red Hat Enterprise Linux 10 4.3 Medium 2026-07-22
CVE-2026-10680 Out-of-bounds access in Zephyr BR/EDR L2CAP configuration request handling via `uint16_t` length underflow — zephyr 7.6 High 2026-07-21
CVE-2026-47254 libheif Has Heap Buffer Overflow in `Track::get_next_sample_raw_data()` -- OOB Chunk Vector Access — libheif 6.1 Medium 2026-07-21

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