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

Goal: 1000 CNY · Raised: 1020 CNY

100%

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

2935 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-2021-46612 Bentley Systems MicroStation 安全漏洞 — MicroStation CONNECT 7.8 -2022-02-18
CVE-2021-46611 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46610 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46608 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46607 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46602 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46600 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46599 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46596 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46595 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46594 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46593 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46591 Bentley Systems MicroStation 安全漏洞 — MicroStation CONNECT 7.8 -2022-02-18
CVE-2021-46590 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2022-02-18
CVE-2021-46589 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 5.5 -2022-02-18
CVE-2021-46563 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2022-02-18
CVE-2021-46562 Bentley Systems MicroStation 缓冲区错误漏洞 — MicroStation CONNECT 7.8 -2022-02-18
CVE-2021-3947 QEMU 缓冲区错误漏洞 — QEMU 5.5 -2022-02-18
CVE-2021-4093 Linux kernel 缓冲区错误漏洞 — kernel 8.8 -2022-02-18
CVE-2022-0623 Out-of-bounds Read in mruby/mruby — mruby/mruby 9.1 -2022-02-17
CVE-2022-23204 Adobe Premiere Rush JPEG File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Premiere Rush 5.5 Medium2022-02-16
CVE-2022-23197 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2022-23196 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2022-23195 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2022-23194 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2022-23190 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2022-23191 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2022-23192 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2022-23193 Adobe Illustrator Out-of-bounds Read could lead to Memory leak — Illustrator 5.5 Medium2022-02-16
CVE-2021-3753 Linux kernel 缓冲区错误漏洞 — kernel 4.7 -2022-02-16

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