CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
3.1 | $0-$5k | 0.04 |
A vulnerability was found in AMD CPU. It has been classified as problematic. This affects some unknown processing of the component Speculative Execution. The manipulation with an unknown input leads to a race condition vulnerability. CWE is classifying the issue as CWE-362. The product contains a code sequence that can run concurrently with other code, and the code sequence 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 that is operating concurrently. This is going to have an impact on confidentiality. The summary by CVE is:
A Speculative Race Condition (SRC) vulnerability that impacts modern CPU architectures supporting speculative execution (related to Spectre V1) has been disclosed. An unauthenticated attacker can exploit this vulnerability to disclose arbitrary data from the CPU using race conditions to access the speculative executable code paths.
The weakness was presented by Hany Ragab, Cristiano Giuffrida, Andrea Mambretti and Anil Kurmus. It is possible to read the advisory at kb.cert.org. This vulnerability is uniquely identified as CVE-2024-2193 since 03/05/2024. The exploitability is told to be difficult. No form of authentication is needed for exploitation. The technical details are unknown and an exploit is not publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Affected
- AMD CPU
- Xen
- Linux Kernel
Product
Type
Vendor
Name
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB CVSS-B Score: 🔒VulDB CVSS-BT Score: 🔒
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.1VulDB Meta Temp Score: 3.1
VulDB Base Score: 3.1
VulDB Temp Score: 3.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
AV | AC | Au | C | I | A |
---|---|---|---|---|---|
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
---|---|---|---|---|---|
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
unlock | unlock | unlock | unlock | unlock | unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Race conditionCWE: CWE-362
CAPEC: 🔒
ATT&CK: 🔒
Local: No
Remote: Partially
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day | unlock | unlock | unlock | unlock |
---|---|---|---|---|
Today | unlock | unlock | unlock | unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/05/2024 CVE reserved03/15/2024 Advisory disclosed
03/15/2024 VulDB entry created
03/15/2024 VulDB entry last update
Sources
Advisory: kb.cert.orgResearcher: Hany Ragab, Cristiano Giuffrida, Andrea Mambretti, Anil Kurmus
Status: Confirmed
Confirmation: 🔒
CVE: CVE-2024-2193 (🔒)
Entry
Created: 03/15/2024 20:44Changes: 03/15/2024 20:44 (41)
Complete: 🔍
This CVE. impacts the major hardware vendors (Intel, AMD, ARM, and IBM) and the Linux kernel. Could You add all the cpes?
Best Regards,
TEAM CERT
Are you interested in using VulDB?
Download the whitepaper to learn more about our service!