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-20534 高通调制解调器越界读取漏洞 — MediaTek chipset - - 2026-10-05
CVE-2026-105164 NASA cFS cfe_fs_api.c CFE_FS_ParseInputFileNameEx out-of-bounds — cFS 2.7 Low 2026-10-04
CVE-2026-104433 Mooncake before 0.3.12 Out-of-Bounds Read via P2P Handshake readString — Mooncake 7.5 High 2026-10-02
CVE-2026-79896 Fortra BoKS Manager boks_portmux TLS ClientHello out-of-bounds read vulnerability — BoKS Manager 7.5 High 2026-10-01
CVE-2026-103678 Tnef: heap out-of-bounds read in get_rtf_data_from_buf() via uncompressed rtf mapi value 5.4 Medium 2026-10-01
CVE-2026-103641 Gegl: gegl04: gegl: out-of-bounds read in the radiance hdr uncompressed scanline decoder — Red Hat Enterprise Linux 10 5.5 Medium 2026-10-01
CVE-2026-47544 NVIDIA vGPU Linux越界读取致代码执行漏洞 — Virtual GPU Manager 7.8 Medium 2026-09-30
CVE-2026-47536 NVIDIA vGPU Linux越界读取致代码执行漏洞 — Virtual GPU Manager 7.8 High 2026-09-30
CVE-2026-47535 NVIDIA vGPU Linux固件越界读取漏洞 — Virtual GPU Manager 7.8 High 2026-09-30
CVE-2026-47521 NVIDIA vGPU Linux越界读取致代码执行漏洞 — Virtual GPU Manager 7.8 High 2026-09-30
CVE-2026-47520 NVIDIA vGPU Linux内核越界读取漏洞 — Guest driver 7.8 High 2026-09-30
CVE-2026-47519 NVIDIA vGPU Linux越界读取致代码执行漏洞 — Guest driver 7.8 High 2026-09-30
CVE-2026-47499 NVIDIA vGPU管理器越界读取致代码执行漏洞 — Virtual GPU Manager 7.8 High 2026-09-30
CVE-2026-47527 NVIDIA GPU驱动固件越界读取漏洞 — GeForce 6.7 Medium 2026-09-30
CVE-2026-47524 NVIDIA驱动越界读取致代码执行漏洞 — GeForce 6.7 Medium 2026-09-30
CVE-2026-47515 NVIDIA驱动内核越界读取致代码执行漏洞 — GeForce 6.7 Medium 2026-09-30
CVE-2026-47576 NVIDIA Windows驱动越界读取致拒绝服务与信息泄露 — GeForce 7.7 High 2026-09-30
CVE-2026-47592 NVIDIA驱动越界读取致代码执行漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-47545 NVIDIA驱动越界读取致代码执行漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-47513 NVIDIA驱动内核越界读取致代码执行漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-47512 NVIDIA驱动内核越界读致信息泄露漏洞 — GeForce 7.8 High 2026-09-30
CVE-2026-80490 Algorithm::AhoCorasick::XS versions through 0.04 for Perl read the haystack string length before the scalar is stringified - - 2026-09-30
CVE-2026-102717 MQTT WebSocket setter ABI mismatch may disclose memory or cause a crash — NetX Duo - - 2026-09-30
CVE-2026-102318 Chrome 154 WebGL越界读取漏洞 — Chrome - - 2026-09-29
CVE-2026-102820 pageant: Out-of-bounds read / oversized allocation in `pageant` MemoryMap::read via a malicious Pageant agent (Windows) — russh 6.2 Medium 2026-09-29
CVE-2026-102726 PPP IPCP无界选项解析致越界读漏洞 — NetX Duo 6.0 Medium 2026-09-29
CVE-2026-102725 MSRP属性列表长度校验缺失致越界读取 — NetX Duo 6.0 Medium 2026-09-29
CVE-2026-102721 CVE-2026-102721 — NetX Duo 6.9 Medium 2026-09-29
CVE-2026-102720 CVE-2026-102720 — eclipse-threadx/netxduo 5.3 Medium 2026-09-29
CVE-2026-102718 NetX Duo SNMP越界读致拒绝服务 — NetX Duo 8.7 High 2026-09-29

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