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-13705 Imager versions before 1.032 for Perl have a heap out-of-bounds read in the bundled Imager::File::SGI reader via a 16-bit RLE literal run in read_rgb_16_rle — Imager - - 2026-07-06
CVE-2026-10657 Out-of-bounds read in Zephyr DNS resolver mDNS suffix check (memcmp past string NUL) — zephyr 3.7 Low 2026-07-05
CVE-2026-14647 onnx onnxruntime old.cc convPoolShapeInference_opset19 out-of-bounds — onnx 4.3 Medium 2026-07-04
CVE-2026-56015 Net::IP::LPM versions through 1.10 for Perl allow a heap out-of-bounds read via an unbounded prefix length — Net::IP::LPM - - 2026-07-03
CVE-2026-14406 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-01
CVE-2026-14388 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-01
CVE-2026-14416 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-01
CVE-2026-14386 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-01
CVE-2026-14384 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-01
CVE-2026-14396 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-07-01
CVE-2026-54908 Pion DTLS: Denial of service via panic while parsing a crafted ECDHE_PSK ServerKeyExchange message — dtls - - 2026-07-01
CVE-2026-44041 UltraVNC vncWc2Mb calls wcslen() before validating that the wide string is NUL-terminated — UltraVNC 4.3 Medium 2026-07-01
CVE-2026-54592 Oj: Stack Buffer Overflow in Oj::Doc#each_child via Deeply Nested Input — oj 7.5 High 2026-06-30
CVE-2026-54500 Oj: intern.c form_attr has an uninitialized stack read — oj 5.3 Medium 2026-06-30
CVE-2026-14090 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-14011 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-13975 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-13906 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-13890 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-13858 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-13819 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-13820 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-30
CVE-2026-56361 ImageMagick - Heap Buffer Overflow via Off-by-One in Morphology Processing — ImageMagick 3.3 Low 2026-06-30
CVE-2026-9263 Out-of-bounds read in Bluetooth Controller ISOAL framed RX reassembly leaks adjacent memory into host HCI ISO packets — zephyr 6.5 Medium 2026-06-30
CVE-2026-10652 Out-of-bounds read in Zephyr DNS resolver TXT/SRV record parsing (unvalidated `rdlength`) — zephyr 4.8 Medium 2026-06-30
CVE-2026-10817 Insufficient input validation leading to memory overread — ADC - - 2026-06-30
CVE-2026-58011 Glib: out-of-bounds read in glib/gdatetime.c:g_date_time_get_ymd via invalid gdatetime — GLib 6.5 Medium 2026-06-30
CVE-2026-9267 Eclipse tinydtls 缓冲区错误漏洞 — Eclipse tinydtls - - 2026-06-29
CVE-2026-13522 Investintech SlimPDFReader PDF File SlimPDFReader.exe TeighaDo+0x25cde0 out-of-bounds — SlimPDFReader 4.3 Medium 2026-06-29
CVE-2026-45258 Multiple vulnerabilities in the sound(4) mmap path — FreeBSD - - 2026-06-27

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