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-34288 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 5.5 - 2022-07-12
CVE-2022-34285 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 5.5 - 2022-07-12
CVE-2022-34283 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 5.5 - 2022-07-12
CVE-2022-34282 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 5.5 - 2022-07-12
CVE-2022-34281 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 7.8 - 2022-07-12
CVE-2022-34280 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 7.8 - 2022-07-12
CVE-2022-34279 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 7.8 - 2022-07-12
CVE-2022-34278 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 7.8 - 2022-07-12
CVE-2022-34277 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 7.8 - 2022-07-12
CVE-2022-34272 Siemens PADS Standard/Plus Viewer 缓冲区错误漏洞 — PADS Standard/Plus Viewer 7.8 - 2022-07-12
CVE-2022-2286 Out-of-bounds Read in vim/vim — vim/vim 7.8 - 2022-07-02
CVE-2022-2287 Out-of-bounds Read in vim/vim — vim/vim 7.8 - 2022-07-02
CVE-2022-2257 Out-of-bounds Read in vim/vim — vim/vim 7.8 - 2022-06-30
CVE-2021-33650 Huawei MindSpore Community 缓冲区错误漏洞 — openEuler:mindspore 7.5 - 2022-06-27
CVE-2021-33649 Huawei MindSpore Community 缓冲区错误漏洞 — openEuler:mindspore 7.5 - 2022-06-27
CVE-2021-33648 Huawei MindSpore Community 缓冲区错误漏洞 — openEuler:mindspore 7.5 - 2022-06-27
CVE-2022-2206 Out-of-bounds Read in vim/vim — vim/vim 7.8 - 2022-06-26
CVE-2022-32139 CODESYS runtime system prone to denial of service due to out of bounds read — Runtime Toolkit 6.5 Medium 2022-06-24
CVE-2022-2183 Out-of-bounds Read in vim/vim — vim/vim 7.8 - 2022-06-23
CVE-2022-2126 Out-of-bounds Read in vim/vim — vim/vim 7.8 - 2022-06-19
CVE-2022-30651 Adobe InCopy Font Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — InCopy 7.8 - 2022-06-16
CVE-2022-30669 Adobe Illustrator Out-of-bounds Read Vulnerability could lead to Memory Leak — Illustrator 5.5 Medium 2022-06-15
CVE-2022-30668 Adobe Illustrator Out-of-bounds Read Vulnerability could lead to Memory Leak — Illustrator 5.5 Medium 2022-06-15
CVE-2022-30667 Adobe Illustrator Out-of-bounds Read Vulnerability could lead to Memory Leak — Illustrator 5.5 Medium 2022-06-15
CVE-2022-30666 Adobe Illustrator Out-of-bounds Read Vulnerability could lead to Memory Leak — Illustrator 5.5 Medium 2022-06-15
CVE-2022-28850 Adobe Bridge Font Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Bridge 5.5 Medium 2022-06-15
CVE-2022-31045 Ill-formed headers may lead to unexpected behavior in Istio — istio 7.0 High 2022-06-09
CVE-2022-28330 read beyond bounds in mod_isapi — Apache HTTP Server 5.3 - 2022-06-08
CVE-2022-29488 Horner Automation Cscape Csfont — Horner Automation Cscape Csfont 7.8 High 2022-06-01
CVE-2022-31001 Out-of-bounds Read in Sofia-SIP — sofia-sip 7.5 High 2022-05-31

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