A race condition in specific microprocessors using Intel (R) DDIO cache allocation and RDMA may allow an authenticated user to potentially …
A race condition in specific microprocessors using Intel (R) DDIO cache allocation and RDMA may allow an authenticated user to potentially enable partial information disclosure via adjacent access.
A number or object is predictable based on observations that the attacker can make about the state of the system or network, such as time, process ID, etc.
https://cwe.mitre.org/data/definitions/341.html →Open in CWE collection →The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.
https://cwe.mitre.org/data/definitions/362.html →Open in CWE collection →The adversary targets a race condition occurring when multiple processes access and manipulate the same resource concurrently, and the outcome of the execution depends on the particular order in which the access takes place. The adversary can leverage a race condition by "running the race", modifying the resource and modifying the normal execution flow. For instance, a race condition can occur while accessing a file: the adversary can trick the system by replacing the original file with their version and cause the system to read the malicious file.
https://capec.mitre.org/data/definitions/26.html →Open in CAPEC collection →This attack targets a race condition occurring between the time of check (state) for a resource and the time of use of a resource. A typical example is file access. The adversary can leverage a file access race condition by "running the race", meaning that they would modify the resource between the first time the target program accesses the file and the time the target program uses the file. During that period of time, the adversary could replace or modify the file, causing the application to behave unexpectedly.
https://capec.mitre.org/data/definitions/29.html →Open in CAPEC collection →| Product | Vendor | Status |
|---|---|---|
| 3106_firmware | * | Tracked |
| 4109t_firmware | * | Tracked |
| 4110_firmware | * | Tracked |
| 4114t_firmware | * | Tracked |
| 4116_firmware | * | Tracked |
| 4116t_firmware | * | Tracked |
| 5118_firmware | * | Tracked |
| 5119t_firmware | * | Tracked |
| 5120t_firmware | * | Tracked |
| 6126_firmware | * | Tracked |
| 6126t_firmware | * | Tracked |
| 6130_firmware | * | Tracked |
| 6130t_firmware | * | Tracked |
| 6138_firmware | * | Tracked |
| cloud_backup | * | Tracked |
| steelstore_cloud_integrated_storage | * | Tracked |
| xeon_e5-1428l_firmware | * | Tracked |
| xeon_e5-1428l_v2_firmware | * | Tracked |
| xeon_e5-1428l_v3_firmware | * | Tracked |
| xeon_e5-1620_firmware | * | Tracked |