Google Android up to 15 avdtp/avctp unnecessary privileges
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $5k-$25k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Google Android 12/12L/13/14/15. This vulnerability affects unknown code of the component avdtp/avctp. The manipulation leads to Local Privilege Escalation. This vulnerability is listed as CVE-2025-0079. The attack must be carried out locally. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Android 12/12L/13/14/15. It has been rated as problematic. This issue affects some unknown functionality of the component avdtp/avctp. The manipulation with an unknown input leads to a local privilege escalation vulnerability. Using CWE to declare the problem leads to CWE-250. The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
In multiple locations, there is a possible way that avdtp and avctp channels could be unencrypted due to a logic error in the code. This could lead to local escalation of privilege with User execution privileges needed. User interaction is not needed for exploitation.
The advisory is shared at android.googlesource.com. The identification of this vulnerability is CVE-2025-0079 since 12/13/2024. The exploitation is known to be easy. An attack has to be approached locally. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/06/2025). MITRE ATT&CK project uses the attack technique T1068 for this issue.
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-0477). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- Google Android
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://www.google.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.1
VulDB Base Score: 5.3
VulDB Temp Score: 5.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: Unnecessary privilegesCWE: CWE-250
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: PatchStatus: 🔍
0-Day Time: 🔒
Timeline
12/13/2024 CVE reserved08/27/2025 Advisory disclosed
08/27/2025 VulDB entry created
09/06/2025 VulDB entry last update
Sources
Vendor: google.comAdvisory: android.googlesource.com
Status: Confirmed
CVE: CVE-2025-0079 (🔒)
GCVE (CVE): GCVE-0-2025-0079
GCVE (VulDB): GCVE-100-321533
CERT Bund: WID-SEC-2025-0477 - Android Patchday März 2025: Mehrere Schwachstellen
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 08/27/2025 07:03Updated: 09/06/2025 11:07
Changes: 08/27/2025 07:03 (54), 08/27/2025 16:53 (3), 09/06/2025 11:07 (7)
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.