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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

3495 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-45457 Microsoft Word Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High 2026-06-09
CVE-2026-45455 Microsoft Excel Information Disclosure Vulnerability — Microsoft 365 Apps for Enterprise 3.3 Low 2026-06-09
CVE-2026-44822 Microsoft Excel Information Disclosure Vulnerability — Microsoft 365 Apps for Enterprise 8.2 High 2026-06-09
CVE-2026-48566 Windows DWM Core Library Information Disclosure Vulnerability — Windows 11 Version 24H2 5.5 Medium 2026-06-09
CVE-2026-45634 Windows DHCP Client Information Disclosure Vulnerability — Windows 10 Version 1607 5.5 Medium 2026-06-09
CVE-2026-45607 Windows Hyper-V Remote Code Execution Vulnerability — Windows 10 Version 1607 8.4 High 2026-06-09
CVE-2026-45606 Microsoft UxTheme Library (uxtheme.dll) Denial of Service Vulnerability — Windows 10 Version 1607 5.5 Medium 2026-06-09
CVE-2026-45639 Windows Remote Desktop Protocol (RDP) Information Disclosure Vulnerability — Remote Desktop client for Windows Desktop 7.5 High 2026-06-09
CVE-2026-44820 Microsoft Excel Remote Code Execution Vulnerability — Microsoft 365 Apps for Enterprise 7.8 High 2026-06-09
CVE-2026-44821 Microsoft Office Information Disclosure Vulnerability — Microsoft 365 Apps for Enterprise 5.5 Medium 2026-06-09
CVE-2026-45485 Microsoft Office Information Disclosure Vulnerability — Microsoft 365 Apps for Enterprise 3.3 Low 2026-06-09
CVE-2026-42771 Possible Out of Bounds Read in X509_VERIFY_PARAM_set1_email() — OpenSSL - - 2026-06-09
CVE-2026-34180 Heap Buffer Over-read in ASN.1 Content Parsing — OpenSSL - - 2026-06-09
CVE-2026-9076 Out-of-Bounds Read in CMS Password-Based Decryption — OpenSSL - - 2026-06-09
CVE-2026-11786 389-ds-base: 389-ds-base: heap out-of-bounds read in ldif parser str2entry_state_information_from_type() — Red Hat Directory Server 11 1.9 Low 2026-06-09
CVE-2026-11667 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-08
CVE-2026-11665 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-08
CVE-2026-40215 OpenVPN OpenSource 安全漏洞 — OpenVPN - - 2026-06-08
CVE-2026-43951 Apache HTTP Server: OOB Read in `merge_response_headers` can cause crash — Apache HTTP Server - - 2026-06-08
CVE-2026-48111 GHSL-2026-121 7-Zip UEFI DEPEX OOB Read — 7-Zip 4.3 Medium 2026-06-05
CVE-2026-48103 GHSL-2026-119 7-Zip WIM SecurityId OOB read — 7-Zip 4.3 Medium 2026-06-05
CVE-2026-48102 GHSL-2026-118: 7-Zip UDF Field OOB Read — 7-Zip 3.1 Low 2026-06-05
CVE-2026-48092 7-Zip SquashFS Fragment Offset Overflow (GHSL-2026-116) — 7-Zip 4.3 Medium 2026-06-05
CVE-2026-50262 Xorg-x11-server: xorg-x11-server-xwayland: xorg-x11-server: out-of-bounds read/write in glx changedrawableattributes — Red Hat Enterprise Linux 10 5.5 Medium 2026-06-05
CVE-2026-11301 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-04
CVE-2026-11299 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-04
CVE-2026-11279 Google Chrome 安全漏洞 — Chrome - - 2026-06-04
CVE-2026-11256 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-04
CVE-2026-11183 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-04
CVE-2026-11160 Google Chrome 缓冲区错误漏洞 — Chrome - - 2026-06-04

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