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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

4337 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-19673 Out-of-bounds read and net_buf length underflow in Zephyr Ethernet L2 when parsing a truncated VLAN header — zephyr 7.1 High 2026-10-14
CVE-2026-101946 Junos OS and Junos OS Evolved: An attacker causes rpd process memory disclosure when IPv6 LDP is used — Junos OS 3.5 Low 2026-10-14
CVE-2026-110716 unshield through 1.6.2 Heap Out-of-Bounds Read via unshield_get_file_table — unshield 5.5 Medium 2026-10-14
CVE-2026-110712 libsmb2 through 6.2 Heap Out-of-Bounds Read via smb2_decode_file_all_info — libsmb2 6.5 Medium 2026-10-14
CVE-2026-110713 libsmb2 through 6.2 Heap Out-of-Bounds Read via File System Info Decoders — libsmb2 6.5 Medium 2026-10-14
CVE-2026-110661 CGNS through 4.5.2 Stack Out-of-Bounds Read via ADFI_read_node_header — CGNS 3.3 Low 2026-10-14
CVE-2026-110660 vgmstream through r2117 Stack Out-of-Bounds Read via G.722.1/Siren14 Decoder — vgmstream 3.3 Low 2026-10-14
CVE-2026-110658 Sofia-SIP through 1.13.18 Heap Out-of-Bounds Read via msg_multipart_parse — sofia-sip 5.3 Medium 2026-10-14
CVE-2026-110656 miniupnpc through 2.3.3 Heap Out-of-Bounds Read via minixml parseelt — miniupnpc 3.1 Low 2026-10-14
CVE-2026-110655 miniupnpc through 2.3.3 Heap Out-of-Bounds Read via minixml parseatt — miniupnpc 3.1 Low 2026-10-14
CVE-2026-110606 LibreCAD libdxfrw through LC2.2.0 Stack Out-of-Bounds Read via dwgReader18::readFileHeader — libdxfrw 3.3 Low 2026-10-14
CVE-2026-110598 Libyal libpff through 20260926 heap out-of-bounds read via libpff_record_entry_get_multi_value — libpff 6.1 Medium 2026-10-14
CVE-2026-110597 Tinyexr through 3.2.0 Heap Out-of-Bounds Read via ParseEXRMultipartHeaderFromMemory — tinyexr 6.1 Medium 2026-10-14
CVE-2024-58392 PhysicsFS through 3.2.0 Out-of-Bounds Read via __PHYSFS_utf8codepoint — PhysicsFS 3.3 Low 2026-10-14
CVE-2026-88842 Busybox: busybox: dpkg stale field_start pointer causes out-of-bounds read and status file corruption — Red Hat Hardened Images 3.3 Low 2026-10-14
CVE-2026-84420 Out-of-Bounds Write and Out-of-Bounds Read — Citrix Workspace app for Windows 5.8 Medium 2026-10-13
CVE-2026-100126 Bridge | Out-of-bounds Read (CWE-125) — Adobe Bridge 5.5 Medium 2026-10-13
CVE-2026-88086 Microsoft SQL Server Information Disclosure Vulnerability — Microsoft SQL Server 2019 (GDR) 5.3 Medium 2026-10-13
CVE-2026-88081 Microsoft SQL Server Information Disclosure Vulnerability — Microsoft SQL Server 2017 (GDR) 7.7 High 2026-10-13
CVE-2026-85888 Microsoft SQL Server Information Disclosure Vulnerability — Microsoft SQL Server 2017 (GDR) 7.7 High 2026-10-13
CVE-2026-67628 Microsoft SQL Server Information Disclosure Vulnerability — Microsoft SQL Server 2017 (GDR) 4.9 Medium 2026-10-13
CVE-2026-103822 Substance3D - Designer | Out-of-bounds Read (CWE-125) — Substance 3D Designer 5.5 Medium 2026-10-13
CVE-2026-103825 Substance3D - Designer | Out-of-bounds Read (CWE-125) — Substance 3D Designer 5.5 Medium 2026-10-13
CVE-2026-100131 Substance3D - Sampler | Out-of-bounds Read (CWE-125) — Substance 3D Sampler 5.5 Medium 2026-10-13
CVE-2026-100130 Substance3D - Sampler | Out-of-bounds Read (CWE-125) — Substance 3D Sampler 5.5 Medium 2026-10-13
CVE-2026-103842 Substance3D - Stager | Out-of-bounds Read (CWE-125) — Adobe Substance 3D Stager 7.8 High 2026-10-13
CVE-2026-103841 Substance3D - Stager | Out-of-bounds Read (CWE-125) — Adobe Substance 3D Stager 7.8 High 2026-10-13
CVE-2026-103850 Substance3D - Stager | Out-of-bounds Read (CWE-125) — Adobe Substance 3D Stager 5.5 Medium 2026-10-13
CVE-2026-103840 Substance3D - Stager | Out-of-bounds Read (CWE-125) — Adobe Substance 3D Stager 7.8 High 2026-10-13
CVE-2026-103853 Dimension | Out-of-bounds Read (CWE-125) — Adobe Dimension 5.5 Medium 2026-10-13

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