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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2901 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)
ConfidentialityRead Memory
An attacker could get secret values such as cryptographic keys, PII, memory addresses, or other information that could be used in additional attacks.
ConfidentialityBypass 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.
AvailabilityDoS: 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.
OtherVaries by Context
The read operation could produce other undefined or unexpected results.
Mitigations (2)
ImplementationAssume 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 DesignUse 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 IDTitleCVSSSeverityPublished
CVE-2026-21303 Substance3D - Modeler | Out-of-bounds Read (CWE-125) — Substance3D - Modeler 5.5 Medium2026-01-13
CVE-2026-21302 Substance3D - Modeler | Out-of-bounds Read (CWE-125) — Substance3D - Modeler 5.5 Medium2026-01-13
CVE-2026-21308 Substance3D - Designer | Out-of-bounds Read (CWE-125) — Substance3D - Designer 5.5 Medium2026-01-13
CVE-2026-21278 InDesign Desktop | Out-of-bounds Read (CWE-125) — InDesign Desktop 5.5 Medium2026-01-13
CVE-2026-20936 Windows NDIS Information Disclosure Vulnerability — Windows 10 Version 1607 4.3 Medium2026-01-13
CVE-2026-20946 Microsoft Excel Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High2026-01-13
CVE-2026-20944 Microsoft Word Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 8.4 High2026-01-13
CVE-2026-20851 Capability Access Management Service (camsvc) Information Disclosure Vulnerability — Windows 11 Version 24H2 6.2 Medium2026-01-13
CVE-2026-20835 Capability Access Management Service (camsvc) Information Disclosure Vulnerability — Windows 11 Version 24H2 5.5 Medium2026-01-13
CVE-2026-20829 TPM Trustlet Information Disclosure Vulnerability — Windows 10 Version 1809 5.5 Medium2026-01-13
CVE-2026-20828 Windows rndismp6.sys Information Disclosure Vulnerability — Windows 10 Version 1607 4.6 Medium2026-01-13
CVE-2026-22801 LIBPNG has an integer truncation causing heap buffer over-read in png_image_write_* — libpng 6.8 Medium2026-01-12
CVE-2026-22695 LIBPNG has a heap buffer over-read in png_image_read_direct_scaled (regression from CVE-2025-65018 fix) — libpng 6.1 Medium2026-01-12
CVE-2025-15506 AcademySoftwareFoundation OpenColorIO FileRules.cpp ConvertToRegularExpression out-of-bounds — OpenColorIO 3.3 Low2026-01-11
CVE-2025-53470 Apache Mynewt NimBLE: Out-of-Bounds Write Vulnerability in NimBLE HCI H4 driver — Apache Mynewt NimBLE 6.5 -2026-01-10
CVE-2026-22023 CryptoLib Has Out-of-Bounds Read in KMC AEAD Encrypt Metadata Parsing via Flawed strtok Pattern — CryptoLib 9.1 -2026-01-10
CVE-2026-21900 CryptoLib Has Out-of-Bounds Read in KMC Encrypt Metadata Parsing via Flawed strtok Pattern — CryptoLib 9.1 -2026-01-10
CVE-2026-21899 CryptoLib has an out-of-bounds read and crash vulnerability when decoding an empty Base64url string — CryptoLib 4.7 Medium2026-01-10
CVE-2026-21898 CryptoLib Has Out-of-bounds Read in Crypto_AOS_ProcessSecurity — CryptoLib 8.2 High2026-01-10
CVE-2026-22185 OpenLDAP <= 2.6.10 LMDB mdb_load Heap Buffer Underflow in readline() — OpenLDAP 7.1 -2026-01-07
CVE-2025-15382 Client SCP Request Triggers Buffer Overread by 1 Byte — wolfSSH 8.1 -2026-01-06
CVE-2026-21489 iccDEV has Out-of-bounds Read and Integer Underflow (Wrap or Wraparound) — iccDEV 6.1 Medium2026-01-06
CVE-2025-10933 Silicon Labs Z-Wave Protocol Controller Integer underflow vulnerability leads to out of bounds read — Z-Wave Protocol Controller 9.1 -2026-01-05
CVE-2025-52871 License Center — License Center 7.5 -2026-01-02
CVE-2025-54166 QTS, QuTS hero — QTS 4.9 -2026-01-02
CVE-2025-54165 QTS, QuTS hero — QTS 4.9 -2026-01-02
CVE-2025-54164 QTS, QuTS hero — QTS 4.9 -2026-01-02
CVE-2025-15412 WebAssembly wabt wasm-decompile VarName out-of-bounds — wabt 5.3 Medium2026-01-01
CVE-2025-68431 libheif has Potential Heap Buffer Over-Read — libheif 6.5 Medium2025-12-29
CVE-2025-14177 Information Leak of Memory in getimagesize — PHP 9.1 -2025-12-27

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