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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

2943 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-2026-23679 libusb < 1.0.30 NULL Pointer Dereference in parse_interface() — libusb 6.2 Medium2026-05-27
CVE-2026-47104 libusb < 1.0.30 Out-of-Bounds Read in parse_iad_array() — libusb 4.0 Medium2026-05-27
CVE-2026-24196 Linux显示驱动存在越界读取漏洞 — GeForce 7.1 High2026-05-26
CVE-2026-48132 VPN service may restart unexpectedly when processing IKE traffic over NAT-T 4500/UDP — Quantum Security Gateway 8.1 High2026-05-26
CVE-2026-9530 GNU LibreDWG Dwgbmp Utility decode.c read_2004_compressed_section out-of-bounds — LibreDWG 3.3 Low2026-05-26
CVE-2026-9504 GNU LibreDWG Dwggrep Utility dwggrep.c bit_convert_TU out-of-bounds — LibreDWG 3.3 Low2026-05-25
CVE-2026-41071 libheif: Heap buffer over-read in SampleAuxInfoReader via crafted HEIF sequence file with mismatched saiz sample count — libheif--2026-05-22
CVE-2026-41069 libheif allows Out-of-bounds vector access leading to invalid dereference (DoS) — libheif 6.5 Medium2026-05-22
CVE-2026-44067 EA header parsing heap over-read — Netatalk 3.7 Medium2026-05-21
CVE-2026-44066 Heap out-of-bounds reads in Spotlight RPC unmarshalling — Netatalk 7.1 High2026-05-21
CVE-2026-44064 ASP session ID out-of-bounds access — Netatalk 7.1 High2026-05-21
CVE-2026-9121 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-20
CVE-2026-9122 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-20
CVE-2026-9113 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-20
CVE-2026-24213 NVIDIA Triton Inference Server 缓冲区错误漏洞 — Triton Inference Server 8.0 High2026-05-20
CVE-2026-43620 Rsync < 3.4.3 Out-of-Bounds Array Read via recv_files() — rsync 6.5 Medium2026-05-20
CVE-2026-32882 libheif: Heap Buffer OOB Read in overlay compositing due to wrong alpha stride — libheif 7.1 High2026-05-19
CVE-2026-32738 libheif has a Heap OOB Read/SEGV Crash via Zero samples_per_chunk — libheif 6.5 Medium2026-05-19
CVE-2026-8686 DoS from MQTT v5.0 Deserialization Fault in core MQTT — coreMQTT 7.5 High2026-05-15
CVE-2024-21950 AMD多款产品 缓冲区错误漏洞 — AMD Instinct™ MI300X--2026-05-15
CVE-2025-0044 AMD Ryzen 缓冲区错误漏洞 — AMD Ryzen™ Al Max+--2026-05-15
CVE-2025-66664 AMD多款产品 缓冲区错误漏洞 — AMD Radeon™ RX 6000 Series Graphics Products--2026-05-15
CVE-2025-29937 AMD Processors 缓冲区错误漏洞 — AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt R")--2026-05-15
CVE-2025-48520 AMD多款产品 缓冲区错误漏洞 — AMD Ryzen™ 7035 Series Processors with Radeon™ Graphics (formerly codenamed "Rembrandt R")--2026-05-15
CVE-2026-8578 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-14
CVE-2026-8546 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-14
CVE-2026-8543 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-14
CVE-2026-8541 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-14
CVE-2026-8535 Google Chrome 缓冲区错误漏洞 — Chrome--2026-05-14
CVE-2026-43996 OpenImageIO: Integer wraparound in bounds check of decode_pixel leads to out-of-bounds read in TGA paletted image decoder — OpenImageIO 5.5 Medium2026-05-14

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