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

Goal: 1000 CNY · Raised: 1359 CNY

100%

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

4343 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-2022-1276 Out-of-bounds Read in mrb_get_args in mruby/mruby — mruby/mruby 9.8 - 2022-04-10
CVE-2022-24786 Potential out-of-bound read/write in PJSIP — pjproject 9.8 Critical 2022-04-06
CVE-2021-20295 Red Hat Enterprise Linux 缓冲区错误漏洞 — QEMU 7.1 - 2022-04-01
CVE-2021-26623 Bandisoft ARK Library Out-of-bound Vulnerability — Bandizip 7.8 High 2022-04-01
CVE-2022-1207 Out-of-bounds read in radareorg/radare2 — radareorg/radare2 5.5 - 2022-04-01
CVE-2021-3422 Indexer denial-of-service via malformed S2S request — Splunk Enterprise 7.5 High 2022-03-25
CVE-2021-44768 Delta Electronics CNCSoft Out-of-bounds Read — CNCSoft 6.1 Medium 2022-03-25
CVE-2021-4156 libsndfile 缓冲区错误漏洞 — libsndfile 7.1 - 2022-03-23
CVE-2021-40769 Adobe Character Animator SVG File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Character Animator (Preview 4) 3.3 - 2022-03-16
CVE-2021-42722 Adobe Bridge Out-of-bounds read could lead to Arbitrary Code Execution — Bridge 7.8 High 2022-03-16
CVE-2021-42720 Adobe Bridge Out-of-bounds read could lead to Arbitrary Code Execution — Bridge 7.8 High 2022-03-16
CVE-2021-40766 Adobe Character Animator SVG File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Character Animator (Preview 4) 3.3 Low 2022-03-16
CVE-2021-42719 Adobe Bridge Out-of-bounds read could lead to Arbitrary Code Execution — Bridge 7.8 - 2022-03-16
CVE-2021-42387 Yandex ClickHouse 缓冲区错误漏洞 — clickhouse 8.1 - 2022-03-14
CVE-2021-42388 Yandex ClickHouse 缓冲区错误漏洞 — clickhouse 8.1 - 2022-03-14
CVE-2022-24090 Adobe Photoshop 2022 Out-of-bounds Read could lead to Memory leak — Photoshop 5.5 Medium 2022-03-11
CVE-2022-25821 Samsung Shannon缓冲区错误漏洞 — Samsung Mobile Devices 3.3 Low 2022-03-08
CVE-2022-25819 Samsung hdcp2缓冲区错误漏洞 — Samsung Mobile Devices with Exynos chipsets 5.3 Medium 2022-03-08
CVE-2021-34338 Ming 缓冲区错误漏洞 — ming 6.5 - 2022-03-07
CVE-2021-34339 Ming 缓冲区错误漏洞 — ming 6.5 - 2022-03-07
CVE-2021-34340 Ming 缓冲区错误漏洞 — ming 6.5 - 2022-03-07
CVE-2021-34341 Ming 缓冲区错误漏洞 — ming 6.5 - 2022-03-07
CVE-2021-34342 Ming 缓冲区错误漏洞 — ming 6.5 - 2022-03-07
CVE-2021-3743 Linux kernel 缓冲区错误漏洞 — Kernel 7.1 - 2022-03-04
CVE-2022-21209 ICSA-22-055-01 FATEK Automation FvDesigner — FvDesigner 7.8 High 2022-02-25
CVE-2021-3610 Imagemagick Studio ImageMagick 缓冲区错误漏洞 — ImageMagick 6.5 - 2022-02-24
CVE-2022-0717 Out-of-bounds Read in mruby/mruby — mruby/mruby 8.1 - 2022-02-23
CVE-2021-44142 Samba 缓冲区错误漏洞 — Samba 8.8 - 2022-02-21
CVE-2022-0630 Out-of-bounds Read in mruby/mruby — mruby/mruby 9.1 - 2022-02-19
CVE-2022-23645 Out-of-bounds read in swtpm — swtpm 6.2 Medium 2022-02-18

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