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

Goal: 1000 CNY · Raised: 1325 CNY

100%

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

3068 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-2022-41880 ThreadUnsafeUnigramCandidateSampler Heap out of bounds in Tensorflow — tensorflow 6.8 Medium2022-11-18
CVE-2022-41883 Out of bounds segmentation fault due to unequal op inputs in Tensorflow — tensorflow 6.8 Medium2022-11-18
CVE-2022-41895 `MirrorPadGrad` heap out of bounds read in Tensorflow — tensorflow 4.8 Medium2022-11-18
CVE-2022-41897 `FractionalMaxPoolGrad` Heap out of bounds read in Tensorflow — tensorflow 4.8 Medium2022-11-18
CVE-2022-39316 Out of bound read in FreeRDP — FreeRDP 4.8 Medium2022-11-16
CVE-2022-39317 Out of bounds read in zgfx decoder in FreeRDP — FreeRDP 4.6 Medium2022-11-16
CVE-2022-39319 Missing length validation in urbdrc channel in FreeRDP — FreeRDP 4.6 Medium2022-11-16
CVE-2022-39320 Heap buffer overflow in urbdrc channel — FreeRDP 5.5 Medium2022-11-16
CVE-2022-3737 Out-of-bounds Read in PHOENIX CONTACT Automationworx Software Suite — Config+ 7.8 High2022-11-15
CVE-2022-41873 Out-of-bounds read and write in BLE L2CAP module — contiki-ng 4.2 Medium2022-11-11
CVE-2022-36938 Meta ReDex 缓冲区错误漏洞 — Redex 9.8 -2022-11-10
CVE-2021-34567 WAGO I/O-Check Service prone to Out-of-bounds Read — 750-81xx/xxx-xxxFW 8.2 High2022-11-09
CVE-2022-39891 SAMSUNG Editor Lite 缓冲区错误漏洞 — Editor Lite 4.3 Medium2022-11-09
CVE-2022-39157 Siemens Parasolid 缓冲区错误漏洞 — Parasolid V34.0 7.8 High2022-11-08
CVE-2022-41661 Siemens JT2Go和Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 7.8 High2022-11-08
CVE-2022-41662 Siemens JT2Go和Teamcenter Visualization 缓冲区错误漏洞 — JT2Go 7.8 High2022-11-08
CVE-2022-38436 Adobe Illustrator CDR File Parsing Out-Of-Bounds Read Remote Code Execution Vulnerability — Illustrator 7.8 High2022-10-25
CVE-2022-35271 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35270 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35269 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35268 Robustel R1510 命令注入漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35267 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35266 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35265 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35264 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35263 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35262 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-35261 Robustel R1510 缓冲区错误漏洞 — R1510 7.5 -2022-10-25
CVE-2022-3576 Synology DiskStation Manager 缓冲区错误漏洞 — DiskStation Manager (DSM) 5.3 Medium2022-10-20
CVE-2022-1738 Fuji Electric D300win Out-of-bounds Read — D300win 8.7 High2022-10-19

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