Google Android 13 setMediaButtonReceiver protection mechanism
| 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 13. Impacted is the function setMediaButtonReceiver. This manipulation causes Local Privilege Escalation.
This vulnerability is handled as CVE-2025-22437. It is possible to launch the attack on the local host. There is not any exploit available.
Applying a patch is the recommended action to fix this issue.
Details
A vulnerability was found in Google Android 13. It has been declared as problematic. Affected by this vulnerability is the function setMediaButtonReceiver. The manipulation with an unknown input leads to a local privilege escalation vulnerability. The CWE definition for the vulnerability is CWE-693. The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In setMediaButtonReceiver of multiple files, there is a possible way to launch arbitrary activities from background due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.
The advisory is shared at android.googlesource.com. This vulnerability is known as CVE-2025-22437 since 01/06/2025. The exploitation appears to be easy. An attack has to be approached locally. Technical details are known, but no exploit is available. The price for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 09/04/2025).
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-26593). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
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: Protection mechanismCWE: CWE-693
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
01/06/2025 CVE reserved09/03/2025 Advisory disclosed
09/03/2025 VulDB entry created
09/04/2025 VulDB entry last update
Sources
Vendor: google.comAdvisory: android.googlesource.com
Status: Confirmed
CVE: CVE-2025-22437 (🔒)
GCVE (CVE): GCVE-0-2025-22437
GCVE (VulDB): GCVE-100-322261
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 09/03/2025 07:24Updated: 09/04/2025 10:50
Changes: 09/03/2025 07:24 (54), 09/04/2025 05:16 (2), 09/04/2025 10:50 (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.