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-61839 Format Plugins | Out-of-bounds Read (CWE-125) — Format Plugins 7.8 High2025-11-11
CVE-2025-61845 Format Plugins | Out-of-bounds Read (CWE-125) — Format Plugins 5.5 Medium2025-11-11
CVE-2025-61840 Format Plugins | Out-of-bounds Read (CWE-125) — Format Plugins 5.5 Medium2025-11-11
CVE-2025-61841 Format Plugins | Out-of-bounds Read (CWE-125) — Format Plugins 5.5 Medium2025-11-11
CVE-2025-61844 Format Plugins | Out-of-bounds Read (CWE-125) — Format Plugins 5.5 Medium2025-11-11
CVE-2025-62202 Microsoft Excel Information Disclosure Vulnerability — Microsoft 365 Apps for Enterprise 7.1 High2025-11-11
CVE-2025-60727 Microsoft Excel Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High2025-11-11
CVE-2025-60726 Microsoft Excel Information Disclosure Vulnerability — Microsoft 365 Apps for Enterprise 7.1 High2025-11-11
CVE-2025-60709 Windows Common Log File System Driver Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High2025-11-11
CVE-2025-60706 Windows Hyper-V Information Disclosure Vulnerability — Windows 10 Version 1607 5.5 Medium2025-11-11
CVE-2025-59513 Windows Bluetooth RFCOM Protocol Driver Information Disclosure Vulnerability — Windows 10 Version 1607 5.5 Medium2025-11-11
CVE-2025-12725 Google Chrome 安全漏洞 — Chrome 8.8 -2025-11-10
CVE-2025-12443 Microsoft Edge 安全漏洞 — Chrome 8.1 -2025-11-10
CVE-2025-12441 Microsoft Edge 安全漏洞 — Chrome 8.1 -2025-11-10
CVE-2025-12829 Amazon Ion C 安全漏洞 — Ion-C 6.2 Medium2025-11-07
CVE-2025-11211 Google Chrome 安全漏洞 — Chrome 8.1AIHighAI2025-11-06
CVE-2025-23050 Qt 缓冲区错误漏洞 — Qt 3.1 Low2025-10-31
CVE-2025-23345 NVIDIA GPU Display Driver 缓冲区错误漏洞 — GeForce 4.4 Medium2025-10-23
CVE-2025-11679 Out-of-bounds Read in libwebsockets PNG parsing — libwebsockets 6.5 -2025-10-20
CVE-2025-55085 Web http client: Unchecked Server-Side Malicious Packet Issue — NetX Duo 9.8AICriticalAI2025-10-17
CVE-2025-55100 Potential out-of-bounds read in _ux_host_class_audio10_sam_parse_func() — USBX 8.2AIHighAI2025-10-17
CVE-2025-55099 Potential out-of-bounds read in _ux_host_class_audio_alternate_setting_locate() — USBX 8.2AIHighAI2025-10-17
CVE-2025-55098 Potential out-of-bounds read in _ux_host_class_audio_device_type_get() — USBX 8.2AIHighAI2025-10-17
CVE-2025-55097 Potential out-of-bounds read in _ux_host_class_audio_streaming_sampling_get() — USBX 8.2AIHighAI2025-10-17
CVE-2025-55094 Potential out-of-bounds read in _nx_icmpv6_validate_options() — NetX Duo 5.3AIMediumAI2025-10-17
CVE-2025-55092 Potential out of bound read in _nx_ipv4_option_process() — NetX Duo 5.3AIMediumAI2025-10-17
CVE-2025-62493 Heap out-of-bounds read in js_bigint_to_string1 in QuickJS — QuickJS--AI2025-10-16
CVE-2025-62492 Heap out-of-bounds read in js_typed_array_indexOf in QuickJS — QuickJS 5.9AIMediumAI2025-10-16
CVE-2025-11840 GNU Binutils ldmisc.c vfinfo out-of-bounds — Binutils 3.3 Low2025-10-16
CVE-2025-55091 Potential out of bound read in _nx_ip_packet_receive() — NetX Duo 8.2AIHighAI2025-10-16

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