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-40015 IMAP-hibernate越界读致进程崩溃 — OX Dovecot Pro 4.3 Medium 2026-08-28
CVE-2026-19315 Fireware OS Pre-Authentication Type Confusion in iked Allows Remote Code Execution — Fireware OS 9.3 Critical 2026-08-27
CVE-2026-19317 Fireware OS Pre-Authentication Out-of-Bounds Read in iked Allows Denial of Service (DoS) — Fireware OS 8.7 High 2026-08-27
CVE-2026-78009 Fireware OS Out-of-Bounds Read in iked Allows Unauthenticated Denial of Service (DoS) — Fireware OS 8.7 High 2026-08-27
CVE-2026-82072 Chrome 151 之前版本 V8 越界读取漏洞 — Chrome - - 2026-08-27
CVE-2026-34616 DNG SDK | Out-of-bounds Read (CWE-125) — Adobe DNG Software Development Kit (SDK) 5.5 Medium 2026-08-27
CVE-2026-71402 wicked: out-of-bounds read in the DHCPv4 option parser due to payload length taken from the IP total length — wicked 5.4 Medium 2026-08-27
CVE-2026-81334 darknet through 6.0 Out-of-Bounds Read and Write via Unchecked Layer Index in .cfg Parser — darknet 6.1 Medium 2026-08-27
CVE-2026-13481 Out-of-bounds read in PTP management TLV TIME parsing in Zephyr net PTP — zephyr 5.4 Medium 2026-08-26
CVE-2026-13479 Out-of-bounds read in LoRaWAN clock-sync AppTimeAns downlink handler — zephyr 3.1 Low 2026-08-26
CVE-2026-80101 Gimp: multiple heap out-of-bounds reads in xwd loader from unrelated width and bytes-per-line validation — GIMP 4.4 Medium 2026-08-25
CVE-2026-79112 Chrome<152.0.7977.65 Skia越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-79239 Chrome < 152.0.7977.65 Tint越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-79206 Chrome低于152.0.7977.65文件系统的越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-79004 Chrome<152.0.7977.65越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-78978 Chrome多个版本ANGLE越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-79241 Chrome <152.0.7977.65 GPU越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-79020 Chrome < 152.0.7977.65 Skia越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-78989 Chrome 152.0.7977.65前ANGLE越界读取漏洞 — Chrome - - 2026-08-25
CVE-2026-59981 OpenEXR: Heap OOB read in SampleCountChannel row when using nonzero dataWindow — openexr 7.1 High 2026-08-25
CVE-2026-61555 OpenEXR: Empty multiView viewFromChannelName file crash — openexr 5.5 Medium 2026-08-25
CVE-2026-59985 OpenEXR: Heap out-of-bounds read in OpenEXRCore RLE decoding on ILP32 — openexr 5.5 Medium 2026-08-25
CVE-2026-59983 OpenEXR: Out-of-bounds read in DeepTiledInputFile sample-count table decode on ILP32 — openexr 5.5 Medium 2026-08-25
CVE-2026-75752 Substance3D - Painter | Out-of-bounds Read (CWE-125) — Substance3D - Painter 5.5 Medium 2026-08-25
CVE-2026-71441 Illustrator | Out-of-bounds Read (CWE-125) — Illustrator Desktop 2026 5.5 Medium 2026-08-25
CVE-2026-59189 OpenEXR: Out-of-bounds read in DeepImageChannel::row() for non-zero dataWindow origin — openexr 7.1 High 2026-08-25
CVE-2026-64203 Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI — LabVIEW 7.8 High 2026-08-25
CVE-2026-64202 Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI — LabVIEW 7.8 High 2026-08-25
CVE-2026-64201 Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI — LabVIEW 7.8 High 2026-08-25
CVE-2026-16234 Out-of-Bounds Read Vulnerability in NI LabVIEW when loading VI — LabVIEW 7.8 High 2026-08-25

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