Qualcomm Snapdragon Auto up to XR2 5G Platform Release Command use after free
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile and Snapdragon Wearables. This affects an unknown function of the component Release Command Handler. This manipulation causes use after free. This vulnerability is registered as CVE-2024-33040. The attack needs to be launched locally. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability classified as critical was found in Qualcomm Snapdragon Auto, Snapdragon Compute, Snapdragon Mobile and Snapdragon Wearables. Affected by this vulnerability is an unknown functionality of the component Release Command Handler. The manipulation with an unknown input leads to a use after free vulnerability. The CWE definition for the vulnerability is CWE-416. Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Memory corruption while invoking redundant release command to release one buffer from user space as race condition can occur in kernel space between buffer release and buffer access.
The advisory is shared at docs.qualcomm.com. This vulnerability is known as CVE-2024-33040 since 04/23/2024. The exploitation appears to be easy. An attack has to be approached locally. The exploitation requires an enhanced level of successful authentication. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 12/02/2024).
Upgrading eliminates this vulnerability.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Vendor
Name
Version
- 8 Gen 1 Mobile Platform
- 865 5G Mobile Platform
- 865+ 5G Mobile Platform (SM8250-AB)
- 870 5G Mobile Platform (SM8250-AC)
- FastConnect 6800
- FastConnect 6900
- FastConnect 7800
- QAM8255P
- QCA6391
- QCA6426
- QCA6436
- QCA6595AU
- QCA6678AQ
- SA8255P
- SD865 5G
- SW5100
- SW5100P
- SXR2130
- W5+ Gen 1 Wearable Platform
- WCD9380
- WCN3660B
- WCN3680B
- WCN3980
- WCN3988
- WSA8810
- WSA8815
- WSA8830
- WSA8835
- X55 5G Modem-RF System
- XR2 5G Platform
License
Website
- Vendor: https://www.qualcomm.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.7VulDB Meta Temp Score: 6.6
VulDB Base Score: 6.7
VulDB Temp Score: 6.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 6.7
CNA Vector (qualcomm): 🔍
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: Use after freeCWE: CWE-416 / CWE-119
CAPEC: 🔍
ATT&CK: 🔍
Physical: Partially
Local: Yes
Remote: No
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Timeline
04/23/2024 🔍12/02/2024 🔍
12/02/2024 🔍
12/02/2024 🔍
Sources
Vendor: qualcomm.comAdvisory: docs.qualcomm.com
Status: Confirmed
CVE: CVE-2024-33040 (🔍)
GCVE (CVE): GCVE-0-2024-33040
GCVE (VulDB): GCVE-100-286525
Entry
Created: 12/02/2024 13:40Updated: 12/02/2024 14:00
Changes: 12/02/2024 13:40 (63), 12/02/2024 14:00 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.