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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

3070 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-7933 Google Chrome 缓冲区错误漏洞 — Chrome 8.1 -2026-05-06
CVE-2026-7904 Google Chrome 缓冲区错误漏洞 — Chrome 8.1AIHighAI2026-05-06
CVE-2026-30923 libModSecurity3 denial of service via segfault when using t:hexDecode on single-character query strings — ModSecurity 7.5 -2026-05-05
CVE-2026-34000 Xwayland: xorg: x.org x server: information disclosure and denial of service via out-of-bounds read in xkb geometry processing. — Red Hat Enterprise Linux 10.0 Extended Update Support 6.1 Medium2026-05-05
CVE-2026-6918 Eclipse OpenJ9 缓冲区错误漏洞 — Eclipse OpenJ9 6.5 -2026-05-05
CVE-2026-33857 Apache HTTP Server: Off-by-one OOB reads in AJP getter functions — Apache HTTP Server 7.5 -2026-05-04
CVE-2026-7482 Ollama heap out-of-bounds read in GGUF tensor parsing leaks server process memory to unauthenticated remote attackers — ollama 9.1 Critical2026-05-04
CVE-2026-7737 osrg GoBGP BMP Parser bmp.go BMPStatisticsReport.ParseBody out-of-bounds — GoBGP 5.3 Medium2026-05-04
CVE-2026-20447 MediaTek Chipsets 缓冲区错误漏洞 — MediaTek chipset 6.7 -2026-05-04
CVE-2026-7668 MikroTik RouterOS SCEP Endpoint scep.p ASN1_STRING_data out-of-bounds — RouterOS 7.3 High2026-05-02
CVE-2026-42799 Out-of-bounds read in ulp — Kestrel 7.4 High2026-04-30
CVE-2026-40686 Exim 缓冲区错误漏洞 — Exim 3.7 Low2026-04-30
CVE-2026-7425 Out-of-Bounds Read in Router Advertisement Option Parser in FreeRTOS-Plus-TCP — FreeRTOS-Plus-TCP 6.5 Medium2026-04-29
CVE-2026-2810 Endpoint DLP Driver Out-of-Bounds Read — Client 5.5AIMediumAI2026-04-29
CVE-2026-41607 Apache Thrift: C++ JSON OOB read — Apache Thrift 7.5AIHighAI2026-04-28
CVE-2026-41604 Apache Thrift: Swift Range crash in skip() — Apache Thrift 7.5AIHighAI2026-04-28
CVE-2026-7233 Artifex MuPDF CFF Index subset-cff.c fz_subset_cff_for_gids out-of-bounds — MuPDF 3.3 Low2026-04-28
CVE-2026-7135 GPAC MP4Box box_code_base.c elng_box_read out-of-bounds — GPAC 5.3 Medium2026-04-27
CVE-2026-41503 BACnet Stack: Out-of-Bounds Read in ReadPropertyMultiple Property Decoder via Deprecated Tag Parser — bacnet-stack 7.5AIHighAI2026-04-24
CVE-2026-41502 BACnet Stack: Off-by-One Out-of-Bounds Read in ReadPropertyMultiple Object ID Decoder — bacnet-stack 9.1AICriticalAI2026-04-24
CVE-2026-41475 BACnet Stack: Out-of-Bounds Read in WritePropertyMultiple Decoder via Deprecated Tag Parser — bacnet-stack 7.5AIHighAI2026-04-24
CVE-2026-41415 PJSIP: SIP Multipart CID URI Length Underflow — pjproject 9.1AICriticalAI2026-04-24
CVE-2026-41677 rust-openssl: Out-of-bounds read in PEM password callback when user callback returns an oversized length — rust-openssl--AI2026-04-24
CVE-2026-41079 OpenPrinting CUPS: Heap out-of-bounds read in SNMP supply-level polling leaks stack memory to authenticated users — cups 4.3 Medium2026-04-24
CVE-2026-33317 OP-TEE: PKCS#11 TA out-of-bounds read and memory disclosure — optee_os 8.7 High2026-04-24
CVE-2026-6920 Google Chrome 缓冲区错误漏洞 — Chrome 9.3AICriticalAI2026-04-23
CVE-2026-34003 Xorg: xwayland: x.org x server: information exposure and denial of service via out-of-bounds memory access — Red Hat Enterprise Linux 10 7.8 High2026-04-23
CVE-2026-40890 github.com/gomarkdown/markdown: Out-of-bounds Read in SmartypantsRenderer — markdown 7.5 High2026-04-21
CVE-2026-24189 NVIDIA CUDA-Q 缓冲区错误漏洞 — CUDA-Q 8.2 High2026-04-21
CVE-2026-40340 libgphoto2 has OOB read in ptp_unpack_OI() in ptp-pack.c via malicious PTP ObjectInfo response — libgphoto2 6.1 Medium2026-04-17

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