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

Goal: 1000 CNY · Raised: 1336 CNY

100%

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

3492 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-50063 Siemens Solid Edge SE2025 缓冲区错误漏洞 — Solid Edge SE2025 7.8 High 2026-08-11
CVE-2026-50062 Siemens Solid Edge SE2025 缓冲区错误漏洞 — Solid Edge SE2025 7.8 High 2026-08-11
CVE-2026-50058 Siemens Solid Edge SE2025 缓冲区错误漏洞 — Solid Edge SE2025 7.8 High 2026-08-11
CVE-2026-11809 UpdateHub probe: uninitialized-heap out-of-bounds read of network-supplied metadata — zephyr 3.7 Low 2026-08-10
CVE-2026-72522 Expat 缓冲区错误漏洞 — libexpat 6.2 Medium 2026-08-10
CVE-2026-11743 Missing negative-offset/overflow check in SF32LB MPI QSPI NOR flash driver allows out-of-bounds read and write — zephyr 6.6 Medium 2026-08-07
CVE-2026-66151 SonicWALL Global VPN Client 缓冲区错误漏洞 — Global VPN Client - - 2026-08-07
CVE-2026-65819 gopacket: Multiple layer decoders panic on crafted packets (out-of-bounds/underflow) enabling unauthenticated remote DoS via DecodingLayerParser — gopacket 7.5 High 2026-08-07
CVE-2026-19082 Imager versions from 0.45_02 before 1.034 for Perl may expose adjacent heap bytes via strlen() over-read from zero-count ASCII EXIF entries in copy_string_tags — Imager - - 2026-08-07
CVE-2026-20347 ClamAV Mach-O File Format Processing Memory Corruption Vulnerability — Cisco Secure Endpoint 7.5 High 2026-08-07
CVE-2026-20346 ClamAV PDF File Format Processing Memory Corruption Vulnerability — Cisco Secure Endpoint 7.5 High 2026-08-07
CVE-2026-54209 TeamDavid: Buffer Overflow in 'editini' function — TeamDavid 8.9 High 2026-08-07
CVE-2026-71498 node-re2: Out-of-bounds heap read in `replace`/`split` via a `Buffer` ending in a truncated multi-byte UTF-8 character → adjacent heap memory disclosed to JavaScript — node-re2 5.1 Medium 2026-08-06
CVE-2026-5856 Contiki-NG DNS/mDNS Resolver Out-of-Bounds Read via Unchecked skip_name Traversal Before Transaction-ID Validation — Contiki-NG 7.1 High 2026-08-06
CVE-2026-5855 Contiki-NG LwM2M TLV Parser Out-of-Bounds Read via Unchecked Buffer Length in lwm2m_tlv_read — Contiki-NG 7.5 High 2026-08-06
CVE-2026-7405 TIF File Parsing Out-of-Bounds Read in certain Autodesk products — Revit 5.5 Medium 2026-08-06
CVE-2026-11803 PDF File Parsing Out-of-Bounds Read Vulnerability in Autodesk Revit — Revit 7.8 High 2026-08-06
CVE-2026-43630 llama.cpp b5702–b7653 Out-of-Bounds Read Information Disclosure — llama.cpp 6.5 Medium 2026-08-06
CVE-2026-19027 HDF5 out-of-bounds heap read in N-Bit filter decompression — HDF5 6.9 Medium 2026-08-05
CVE-2026-70598 Electron: Off-screen rendering trusts GPU-supplied geometry over shared-memory size — electron 3.9 Low 2026-08-05
CVE-2026-71256 nanoMODBUS Client-Side Out-of-Bounds Read Leading to Wild-Pointer Write via object_id — nanoMODBUS 9.8 Critical 2026-08-05
CVE-2026-45705 OpenSIPS: OOB Read in Multipart Body Boundary Parsing — opensips 5.3 Medium 2026-08-04
CVE-2026-68743 Sssd: sssd: pam responder out-of-bounds read via unchecked auth_token_length in protocol v1 — Red Hat Enterprise Linux 10 5.5 Medium 2026-08-04
CVE-2026-18790 Systerel S2OPC DeleteMonitoredItemsRequest state_machine.c out-of-bounds — S2OPC 3.3 Low 2026-08-04
CVE-2026-70368 Stunnel: stack-based out-of-bounds read/write in stunnel s_vlog via oversized log message — stunnel 6.5 Medium 2026-08-04
CVE-2026-68742 Sssd: sssd: nss responder out-of-bounds read via unchecked addrlen in gethostbyaddr — Red Hat Enterprise Linux 10 5.5 Medium 2026-08-03
CVE-2026-18583 mz-automation libiec61850 MMS Request mms_mapping.c checkDataSetAccess out-of-bounds — libiec61850 5.3 Medium 2026-08-03
CVE-2026-20496 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset - - 2026-08-03
CVE-2026-20494 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset - - 2026-08-03
CVE-2026-20490 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset - - 2026-08-03

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