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

Goal: 1000 CNY · Raised: 1310 CNY

100%

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

2965 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-2023-38240 ZDI-CAN-21245: Adobe Acrobat Reader DC Font Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Acrobat Reader 5.5 Medium2023-08-10
CVE-2023-38239 ZDI-CAN-21242: Adobe Acrobat Reader DC Font Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Acrobat Reader 5.5 Medium2023-08-10
CVE-2023-38241 ZDI-CAN-21246: Adobe Acrobat Reader DC Font Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Acrobat Reader 5.5 Medium2023-08-10
CVE-2023-38213 ZDI-CAN-21094: Adobe Dimension GLB File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Dimension 5.5 Medium2023-08-09
CVE-2023-35386 Windows Kernel Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2023-08-08
CVE-2023-36905 Windows Wireless Wide Area Network Service (WwanSvc) Information Disclosure Vulnerability — Windows 10 Version 1809 5.5 Medium2023-08-08
CVE-2023-39188 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2023-08-08
CVE-2023-39187 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2023-08-08
CVE-2023-39186 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2023-08-08
CVE-2023-39185 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2023-08-08
CVE-2023-39184 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2023-08-08
CVE-2023-39183 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2023-08-08
CVE-2023-39182 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2023-08-08
CVE-2023-38682 Siemens Parasolid 缓冲区错误漏洞 — JT2Go 7.8 High2023-08-08
CVE-2023-38531 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.1 7.8 High2023-08-08
CVE-2023-38530 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.1 7.8 High2023-08-08
CVE-2023-38529 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.1 7.8 High2023-08-08
CVE-2023-38527 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.1 7.8 High2023-08-08
CVE-2023-38526 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.1 7.8 High2023-08-08
CVE-2023-38525 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.1 7.8 High2023-08-08
CVE-2023-30796 多款Siemens产品 缓冲区错误漏洞 — JT Open 7.8 High2023-08-08
CVE-2023-30795 Siemens 多款产品 缓冲区错误漏洞 — JT Open 7.8 High2023-08-08
CVE-2023-4135 Out-of-bounds read information disclosure vulnerability — qemu-kvm 6.0 Medium2023-08-04
CVE-2023-38559 Ghostscript: out-of-bound read in base/gdevdevn.c:1973 in devn_pcx_write_rle could result in dos — Red Hat Enterprise Linux 8 5.5 Medium2023-08-01
CVE-2023-34359 ASUS RT-AX88U - Out-of-bounds Read - 2 — RT-AX88U 7.5 High2023-07-31
CVE-2023-34358 ASUS RT-AX88U - Out-of-bounds Read - 1 — RT-AX88U 7.5 High2023-07-31
CVE-2023-3773 Kernel: xfrm: out-of-bounds read of xfrma_mtimer_thresh nlattr — Red Hat Enterprise Linux 9 5.5 Medium2023-07-25
CVE-2023-3745 Imagemagick: heap-buffer-overflow in pushcharpixel() in quantum-private.h — Red Hat Enterprise Linux 6 5.5 Medium2023-07-24
CVE-2023-2860 Out-of-bounds read when setting hmac data — kernel 4.4 Medium2023-07-24
CVE-2022-2127 Samba: out-of-bounds read in winbind auth_crap — Red Hat Enterprise Linux 8 5.9 Medium2023-07-20

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