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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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

2925 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-2025-1659 DWFX File Parsing Out-of-Bounds Read Vulnerability — Navisworks Freedom 7.8 High2025-04-01
CVE-2025-1658 DWFX File Parsing Out-of-Bounds Read Vulnerability — Navisworks Freedom 7.8 High2025-04-01
CVE-2025-3015 Open Asset Import Library Assimp ASE File ASELoader.cpp BuildUniqueRepresentation out-of-bounds — Assimp 6.3 Medium2025-03-31
CVE-2025-2755 Open Asset Import Library Assimp AC3D File ACLoader.cpp ConvertObjectSection out-of-bounds — Assimp 6.3 Medium2025-03-25
CVE-2025-2753 Open Asset Import Library Assimp LWS File LWSLoader.cpp MergeScenes out-of-bounds — Assimp 6.3 Medium2025-03-25
CVE-2025-2752 Open Asset Import Library Assimp CSM File fast_atof.h fast_atoreal_move out-of-bounds — Assimp 4.3 Medium2025-03-25
CVE-2025-2751 Open Asset Import Library Assimp CSM File CSMLoader.cpp InternReadFile out-of-bounds — Assimp 4.3 Medium2025-03-25
CVE-2025-2231 PDF-XChange Editor RTF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — PDF-XChange Editor 7.8AIHighAI2025-03-24
CVE-2025-30347 Varnish Enterprise 安全漏洞 — Varnish Enterprise 4.0 Medium2025-03-21
CVE-2024-12055 DoS using malicious gguf model file in ollama/ollama — ollama/ollama 6.5 -2025-03-20
CVE-2024-11131 Synology Camera Firmware 缓冲区错误漏洞 — Camera Firmware 9.8 Critical2025-03-19
CVE-2025-29913 CryptoLib's Crypto_TC_Prep_AAD Has Buffer Overflow Due to Integer Underflow — CryptoLib 9.8 -2025-03-17
CVE-2025-1652 MODEL File Parsing Out-of-Bounds Read Vulnerability — AutoCAD 7.8 High2025-03-13
CVE-2025-1433 MODEL File Parsing Out-of-Bounds Read Vulnerability — AutoCAD 7.8 High2025-03-13
CVE-2025-1431 SLDPRT File Parsing Out-of-Bounds Read Vulnerability — AutoCAD 7.8 High2025-03-13
CVE-2025-1428 CATPRODUCT File Parsing Out-of-Bounds Read Vulnerability — AutoCAD 7.8 High2025-03-13
CVE-2025-27788 Ruby JSON Parser has Out-of-bounds Read — json 7.5 High2025-03-12
CVE-2025-0900 PDF-XChange Editor PDF File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — PDF-XChange Editor 5.5 -2025-03-11
CVE-2025-2012 Ashlar-Vellum Cobalt VS File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — Cobalt 7.8 -2025-03-11
CVE-2025-27180 Substance3D - Modeler | Out-of-bounds Read (CWE-125) — Substance3D - Modeler 5.5 Medium2025-03-11
CVE-2025-24431 Acrobat Reader | Out-of-bounds Read (CWE-125) — Acrobat Reader 5.5 Medium2025-03-11
CVE-2025-27161 Acrobat Reader | Out-of-bounds Read (CWE-125) — Acrobat Reader 7.8 High2025-03-11
CVE-2025-27164 Acrobat Reader | Out-of-bounds Read (CWE-125) — Acrobat Reader 5.5 Medium2025-03-11
CVE-2025-27163 Acrobat Reader | Out-of-bounds Read (CWE-125) — Acrobat Reader 5.5 Medium2025-03-11
CVE-2025-24449 Illustrator | Out-of-bounds Read (CWE-125) — Illustrator 5.5 Medium2025-03-11
CVE-2025-24448 Illustrator | Out-of-bounds Read (CWE-125) — Illustrator 5.5 Medium2025-03-11
CVE-2025-24991 Windows NTFS Information Disclosure Vulnerability — Windows 10 Version 1507 5.5 Medium2025-03-11
CVE-2025-24055 Windows USB Video Class System Driver Information Disclosure Vulnerability — Windows 10 Version 1507 4.3 Medium2025-03-11
CVE-2025-24988 Windows USB Video Class System Driver Elevation of Privilege Vulnerability — Windows 10 Version 1507 6.6 Medium2025-03-11
CVE-2025-24987 Windows USB Video Class System Driver Elevation of Privilege Vulnerability — Windows 10 Version 1507 6.6 Medium2025-03-11

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