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-2025-21465 Out-of-bounds Read in Core — Snapdragon 6.5 Medium2025-08-06
CVE-2025-21464 Out-of-bounds Read in Core — Snapdragon 6.5 Medium2025-08-06
CVE-2025-54648 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.4 Medium2025-08-06
CVE-2025-54647 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.4 Medium2025-08-06
CVE-2025-54644 Huawei HarmonyOS和Huawei EMUI 安全漏洞 — HarmonyOS 6.6 Medium2025-08-06
CVE-2025-54643 Huawei HarmonyOS和Huawei EMUI 安全漏洞 — HarmonyOS 6.6 Medium2025-08-06
CVE-2025-54637 Huawei HarmonyOS和Huawei EMUI 安全漏洞 — HarmonyOS 4.4 Medium2025-08-06
CVE-2025-54633 Huawei HarmonyOS 安全漏洞 — HarmonyOS 6.7 Medium2025-08-06
CVE-2025-54609 Huawei HarmonyOS 安全漏洞 — HarmonyOS 5.4 Medium2025-08-06
CVE-2025-47152 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 6.5 Medium2025-08-05
CVE-2025-27931 PDF-XChange Editor 缓冲区错误漏洞 — PDF-XChange Editor 6.5 Medium2025-08-05
CVE-2025-23286 NVIDIA GPU Display Driver 缓冲区错误漏洞 — GPU Display Drivers 4.4 Medium2025-08-02
CVE-2025-48072 OpenEXR's Inaccurate Pointer Arithmetic can Cause an Out of Bounds Heap — openexr 7.8AIHighAI2025-07-31
CVE-2025-6635 PRT File Parsing Out-of-Bounds Read Vulnerability — Shared Components 7.8 High2025-07-29
CVE-2023-53161 buffered-reader crate 缓冲区错误漏洞 — buffered-reader 2.9 Low2025-07-28
CVE-2023-53160 sequoia-openpgp 缓冲区错误漏洞 — sequoia 2.9 Low2025-07-28
CVE-2025-5042 RFA File Parsing Out-of-Bounds Read Vulnerability — Revit 7.8 High2025-07-22
CVE-2025-7324 IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7322 IrfanView CADImage Plugin DWG File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7319 IrfanView CADImage Plugin DWG File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7312 IrfanView CADImage Plugin DWG File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7298 IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7291 IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7279 IrfanView CADImage Plugin CGM File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7275 IrfanView CADImage Plugin CGM File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7273 IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7269 IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7268 IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7267 IrfanView CADImage Plugin DXF File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21
CVE-2025-7265 IrfanView CADImage Plugin CGM File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — IrfanView 7.8 -2025-07-21

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