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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

3074 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-2024-20712 Adobe Substance 3D Stager v2.1.1 Vulnerability III — Substance3D - Stager 5.5 Medium2024-01-10
CVE-2024-20713 Adobe Substance 3D Stager v2.1.1 Vulnerability IV — Substance3D - Stager 5.5 Medium2024-01-10
CVE-2024-20714 Adobe Substance 3D Stager v2.1.1 Vulnerability V — Substance3D - Stager 5.5 Medium2024-01-10
CVE-2024-20710 Adobe Substance 3D Stager v2.1.1 Vulnerability I — Substance3D - Stager 5.5 Medium2024-01-10
CVE-2024-20715 Adobe Substance 3D Stager v2.1.1 Vulnerability VIII — Substance3D - Stager 5.5 Medium2024-01-10
CVE-2024-21314 Microsoft Message Queuing Information Disclosure Vulnerability — Windows 10 Version 1809 6.5 Medium2024-01-09
CVE-2024-21311 Windows Cryptographic Services Information Disclosure Vulnerability — Windows 10 Version 1809 5.5 Medium2024-01-09
CVE-2024-20687 Microsoft AllJoyn API Denial of Service Vulnerability — Windows 10 Version 1809 7.5 High2024-01-09
CVE-2024-20660 Microsoft Message Queuing Information Disclosure Vulnerability — Windows 10 Version 1809 6.5 Medium2024-01-09
CVE-2024-20653 Microsoft Common Log File System Elevation of Privilege Vulnerability — Windows Server 2022, 23H2 Edition (Server Core installation) 7.8 High2024-01-09
CVE-2024-20691 Windows Themes Information Disclosure Vulnerability — Windows 10 Version 1809 4.7 Medium2024-01-09
CVE-2024-20658 Microsoft Virtual Hard Disk Elevation of Privilege Vulnerability — Windows 10 Version 1809 7.8 High2024-01-09
CVE-2023-51439 Siemens JT2GO 和 Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 7.8 High2024-01-09
CVE-2023-49127 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2024-01-09
CVE-2023-49126 Siemens Solid Edge 缓冲区错误漏洞 — Solid Edge SE2023 7.8 High2024-01-09
CVE-2023-49124 Siemens Solid Edge 安全漏洞 — Solid Edge SE2023 7.8 High2024-01-09
CVE-2024-0322 Out-of-bounds Read in gpac/gpac — gpac/gpac 7.1AIHighAI2024-01-08
CVE-2023-38678 Segfault in paddle.mode — PaddlePaddle 4.7 Medium2024-01-03
CVE-2024-0207 Out-of-bounds Read in Wireshark — Wireshark 7.8 High2024-01-03
CVE-2023-4280 Unvalidated input in Silicon Labs TrustZone implementation leads to accessing Trusted memory region — GSDK 9.3 Critical2024-01-02
CVE-2023-4020 Unvalidated input in Silicon Labs PSA Attestation service leads to secure memory access from non-secure memory — GSDK 9.0 Critical2023-12-15
CVE-2023-48638 Adobe Substance 3D Designer 13.0.2 build 6942 Vulnerability III — Substance3D - Designer 5.5 Medium2023-12-13
CVE-2023-48637 Adobe Substance 3D Designer 13.0.2 build 6942 Vulnerability II — Substance3D - Designer 5.5 Medium2023-12-13
CVE-2023-48636 Adobe Substance 3D Designer 13.0.2 build 6942 Vulnerability IV — Substance3D - Designer 5.5 Medium2023-12-13
CVE-2023-48635 ZDI-CAN-22174: Adobe After Effects AEP File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — After Effects 5.5 Medium2023-12-13
CVE-2023-47080 Adobe Substance 3D Stager v2.1.1 Vulnerability VI — Substance3D - Stager 5.5 Medium2023-12-13
CVE-2023-47081 Adobe Substance 3D Stager v2.1.1 Vulnerability II — Substance3D - Stager 5.5 Medium2023-12-13
CVE-2023-47061 ZDI-CAN-22278: Adobe Dimension GLB File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Dimension 5.5 Medium2023-12-13
CVE-2023-47079 ZDI-CAN-22279: Adobe Dimension USD File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Dimension 5.5 Medium2023-12-13
CVE-2023-47062 ZDI-CAN-22284: Adobe Dimension GLTF File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability — Dimension 5.5 Medium2023-12-13

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