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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%
Buy Us a Coffee

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-2026-20429 MediaTek Chipsets 安全漏洞 — MediaTek chipset 4.4AIMediumAI2026-03-02
CVE-2026-20424 MediaTek Chipsets 安全漏洞 — MediaTek chipset 4.4AIMediumAI2026-03-02
CVE-2026-3391 FascinatedBox lily lily_emitter.c clear_storages out-of-bounds — lily 3.3 Low2026-03-01
CVE-2026-3390 FascinatedBox lily Error Reporting lily_build_error.c patch_line_end out-of-bounds — lily 3.3 Low2026-03-01
CVE-2026-3386 wren-lang wren wren_compiler.c emitOp out-of-bounds — wren 3.3 Low2026-03-01
CVE-2026-28231 pillow_heif Has Integer Overflow in Encode Path Buffer Validation that Leads to Heap Out-of-Bounds Read — pillow_heif 9.1 -2026-02-27
CVE-2026-22717 VMware Workstation out-of-bound read vulnerability — Workstation 2.7 Low2026-02-27
CVE-2026-3285 berry-lang berry be_lexer.c scan_string out-of-bounds — berry 3.3 Low2026-02-27
CVE-2026-3283 libvips extract.c vips_extract_band_build out-of-bounds — libvips 3.3 Low2026-02-27
CVE-2026-3282 libvips unpremultiply.c vips_unpremultiply_build out-of-bounds — libvips 3.3 Low2026-02-27
CVE-2026-27831 rldns Vulnerable to Heap-based Out-of-Bounds Read — rldns 7.5 High2026-02-26
CVE-2026-27711 NanaZip UFS Archive Parser Memory Corruption via Unvalidated Directory Record Length — NanaZip 7.8AIHighAI2026-02-25
CVE-2026-27709 NanaZip .NET Single-File Manifest Parser Vulnerable to Out-of-Bounds Read via Unchecked RelativePathLength — NanaZip 9.1AICriticalAI2026-02-25
CVE-2026-27798 ImageMagick: Heap Buffer Over-read in WaveletDenoise when processing small images — ImageMagick 4.0 Medium2026-02-25
CVE-2026-25942 FreeRDP has global-buffer-overflow in xf_rail_server_execute_result — FreeRDP 8.2AIHighAI2026-02-25
CVE-2026-27692 iccDEV has HBO in CIccTagTextDescription::Release() — iccDEV 7.1 High2026-02-25
CVE-2026-0402 SonicWALL SonicOS 安全漏洞 — SonicOS 6.5AIMediumAI2026-02-24
CVE-2026-2664 Out of bounds read vulnerability in grpcfuse kernel module — Docker Desktop 7.1AIHighAI2026-02-24
CVE-2026-25987 ImageMagick has heap buffer over-read in MAP image decoder — ImageMagick 5.3 Medium2026-02-24
CVE-2026-25982 ImageMagick Has Heap Out-of-Bounds Read in DCM Decoder (ReadDCMImage) — ImageMagick 6.5 Medium2026-02-24
CVE-2026-25898 Imagemagick Has Global Buffer Overflow (OOB Read) via Negative Pixel Index in UIL and XPM Writer — ImageMagick 6.5 Medium2026-02-24
CVE-2026-24481 ImageMagick has Possible Heap Information Disclosure in PSD ZIP Decompression — ImageMagick 7.5 High2026-02-24
CVE-2026-3061 Google Chrome 安全漏洞 — Chrome 8.1AIHighAI2026-02-23
CVE-2026-21863 Malformed Valkey Cluster bus message can lead to Remote DoS — valkey 7.5 High2026-02-23
CVE-2026-2869 janet-lang janet handleattr specials.c janetc_varset out-of-bounds — janet 3.3 Low2026-02-21
CVE-2026-2858 wren-lang wren Source File wren_compiler.c peekChar out-of-bounds — wren 3.3 Low2026-02-20
CVE-2026-22885 EnOcean SmartServer IoT Out-of-bounds Read — SmartServer IoT 3.7 Low2026-02-20
CVE-2026-2243 Qemu-kvm: heap buffer out-of-bounds read in vmdk compressed grain parsing 5.1 Medium2026-02-19
CVE-2026-2705 Open Babel MOL2 File atom.h SetFormalCharge out-of-bounds — Open Babel 4.3 Medium2026-02-19
CVE-2026-2704 Open Babel CIF File transform3d.cpp DescribeAsString out-of-bounds — Open Babel 4.3 Medium2026-02-19

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