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

Goal: 1000 CNY · Raised: 1000 CNY

100.0%

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-2025-58427 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2025-66617 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2025-47873 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2025-61952 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2025-66503 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2025-66042 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2025-65119 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2025-62403 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2026-20726 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2026-22882 Canva Affinity 安全漏洞 — Affinity 6.1 Medium2026-03-17
CVE-2026-0708 Libucl: libucl: denial of service via embedded null byte in ucl input — libucl 8.3 High2026-03-17
CVE-2025-71264 Mumble 缓冲区错误漏洞 — Mumble 3.7 Low2026-03-16
CVE-2026-28521 arduino-TuyaOpen TuyaIoT Out-of-Bounds Memory Read Information Disclosure — arduino-TuyaOpen 7.7 High2026-03-15
CVE-2026-3441 Binutils: gnu binutils: information disclosure via specially crafted xcoff object file — Red Hat Enterprise Linux 10 6.1 Medium2026-03-15
CVE-2026-3442 Binutils: gnu binutils: information disclosure or denial of service via out-of-bounds read in bfd linker — Red Hat Enterprise Linux 10 6.1 Medium2026-03-15
CVE-2026-31897 FreeRDP has an out-of-bounds read in `freerdp_bitmap_decompress_planar` — FreeRDP--2026-03-13
CVE-2026-31885 FreeRDP has an out-of-bounds read in ADPCM decoders due to missing predictor/step_index bounds checks — FreeRDP 6.5 Medium2026-03-13
CVE-2026-0956 Out-Of-Bounds Read in Digilent DASYLab — DASYLab 7.8 High2026-03-13
CVE-2026-0955 Out-Of-Bounds Read When Opening a Corrupt File in Digilent DASYLab — DASYLab 7.8 High2026-03-13
CVE-2026-32320 Ella Core: AMF DoS via malformed PathSwitchRequest with empty NR security capability bitstrings — core 6.5 Medium2026-03-12
CVE-2026-32319 Ella Core: Unauthenticated AMF DoS via malformed InitialUEMessage with undersized integrity-protected NAS payload — core 7.5 High2026-03-12
CVE-2026-4012 rxi fe fe.c read_ out-of-bounds — fe 3.3 Low2026-03-12
CVE-2026-4009 jarikomppa soloud WAV File dr_wav.h drwav_read_pcm_frames_s16__msadpcm out-of-bounds — soloud 3.3 Low2026-03-12
CVE-2025-15038 ASUS Business System Control Interface 安全漏洞 — ASUS Business System Control Interface 7.1AIHighAI2026-03-12
CVE-2026-3926 Google Chrome 缓冲区错误漏洞 — Chrome 8.1AIHighAI2026-03-11
CVE-2026-3916 Google Chrome 缓冲区错误漏洞 — Chrome 9.3AICriticalAI2026-03-11
CVE-2026-3950 strukturag libheif stsz/stts track.cc load out-of-bounds — libheif 3.3 Low2026-03-11
CVE-2026-3949 strukturag libheif HEIF File decoder_vvdec.cc vvdec_push_data2 out-of-bounds — libheif 3.3 Low2026-03-11
CVE-2026-21888 MQTT v5 Variable Byte Integer parsing out-of-bounds: get_var_integer() — nanomq 7.5 High2026-03-11
CVE-2026-27270 Illustrator | Out-of-bounds Read (CWE-125) — Illustrator 5.5 Medium2026-03-10

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