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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

4338 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-102714 CVE-2026-102714 — NetX Duo 7.1 High 2026-09-29
CVE-2026-102713 CVE-2026-102713 — NetX Duo 8.8 High 2026-09-29
CVE-2026-102712 OpenSSL DTLS 越界读致内存泄露 — NetX Duo 8.8 High 2026-09-29
CVE-2026-102711 ThreadX加载器堆越界读及完整性校验缺失漏洞 — `eclipse-threadx/threadx` (module manager / loadable-module loader) 5.6 Medium 2026-09-29
CVE-2026-102757 ThreadX模块权限提升漏洞 — ThreadX 8.5 High 2026-09-29
CVE-2026-102560 Libsoup: libsoup: heap buffer overflow during outgoing permessage-deflate buffer growth — Red Hat Enterprise Linux 10 8.6 High 2026-09-29
CVE-2026-102559 Libsoup: libsoup: heap buffer overflow during websocket client-frame masking — Red Hat Enterprise Linux 10 8.6 High 2026-09-29
CVE-2026-102558 Libsoup: libsoup: heap buffer overflow during websocket receive-buffer growth — Red Hat Enterprise Linux 10 8.6 High 2026-09-29
CVE-2026-102555 Libsoup: libsoup: heap buffer overflow via uninitialized length in data-uri base64 decoding — Red Hat Enterprise Linux 10 8.2 High 2026-09-29
CVE-2026-102557 Libsoup: libsoup: heap buffer overflow during websocket message reassembly — Red Hat Enterprise Linux 10 8.6 High 2026-09-29
CVE-2026-84782 DTLS Retransmits Handshake Messages From a Stale Buffer Offset — OpenSSL - - 2026-09-29
CVE-2026-102567 CTranslate2 before 4.8.1 Out-of-Bounds Read via Model Deserialization — CTranslate2 6.1 Medium 2026-09-29
CVE-2026-102521 lib0 `readFromDataView` out-of-bounds read — lib0 8.6 High 2026-09-29
CVE-2026-102360 lib0 `readUint8Array` performs an unbounded read past the end of the decoder’s view, disclosing adjacent process memory — lib0 8.6 High 2026-09-29
CVE-2026-102507 Sliver 1.7.7 Denial of Service via PE Parser Slice Bounds in Operator RPC — sliver 5.7 Medium 2026-09-29
CVE-2026-95509 Out-of-bounds read vulnerability in string formatting impacts Qt for MCUs — Qt for MCUs 8.8 High 2026-09-29
CVE-2026-18747 Integer underflow of net_buf length in the MCUmgr serial (SMP over console) transport leads to out-of-bounds read — zephyr 6.8 Medium 2026-09-28
CVE-2026-101205 FastStone Image Viewer PCX Decoder out-of-bounds — Image Viewer 6.3 Medium 2026-09-28
CVE-2026-101204 FastStone Image Viewer TGA Image FSViewer.exe out-of-bounds — Image Viewer 6.3 Medium 2026-09-28
CVE-2026-18416 Out-of-bounds read in CoAP well-known-core Uri-Query href matching (match_path_uri) — zephyr 3.7 Low 2026-09-28
CVE-2026-94285 Out-of-bounds read in libX11's byte-oriented codeset parser — libX11 5.1 Medium 2026-09-28
CVE-2026-94284 Out-of-bounds read vulnerability in libX11's XIM trigger-keyregistration parser.registration parser — libX11 5.5 Medium 2026-09-28
CVE-2026-94283 Out-of-bounds read vulnerability in libX11's XIM (X Input Method) attribute parser — libX11 6.5 Medium 2026-09-28
CVE-2026-94282 Out-of-bounds read in libXi's XI2 enter/leave/focus cookie conversion — libXi 5.6 Medium 2026-09-28
CVE-2026-100505 Ghidra 9.2 through 12.1.4 Heap Out-of-Bounds Read via StringManager — ghidra 4.4 Medium 2026-09-26
CVE-2026-100387 pgPointcloud through 1.2.5 heap out-of-bounds read via WKB deserialization — pointcloud 8.1 High 2026-09-25
CVE-2026-93682 Out-of-bounds read in the HTTP stream wrapper when following a redirect with an empty Location header — PHP 5.8 Medium 2026-09-25
CVE-2026-93306 This Power System update is being released to address — Server Firmware 7.1 High 2026-09-25
CVE-2026-81508 ESF-IDF: Heap Out-of-Bounds Read in Bluedroid A2DP Sink Media Packet Processing — esp-idf 4.3 Medium 2026-09-24
CVE-2026-26054 SumatraPDF: Heap out-of-bounds read in MOBI header parser. — sumatrapdf 6.8 Medium 2026-09-24

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