Google Android 13/14/15/16 BiometricEnrollIntroduction.java onStart improper export of android application components
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Google Android 13/14/15/16. It has been rated as problematic. Affected is the function onStart of the file BiometricEnrollIntroduction.java. This manipulation causes Local Privilege Escalation.
This vulnerability is handled as CVE-2025-32347. It is possible to launch the attack on the local host. There is not any exploit available.
To fix this issue, it is recommended to deploy a patch.
Details
A vulnerability classified as problematic was found in Google Android 13/14/15/16. Affected by this vulnerability is the function onStart of the file BiometricEnrollIntroduction.java. The manipulation with an unknown input leads to a local privilege escalation vulnerability. The CWE definition for the vulnerability is CWE-926. The Android application exports a component for use by other applications, but does not properly restrict which applications can launch the component or access the data it contains. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In onStart of BiometricEnrollIntroduction.java, there is a possible way to determine the device's location due to an unsafe PendingIntent. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is needed for exploitation.
It is possible to read the advisory at android.googlesource.com. This vulnerability is known as CVE-2025-32347 since 04/05/2025. The exploitation appears to be easy. Attacking locally is a requirement. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 09/07/2025).
Applying a patch is able to eliminate this problem.
The vulnerability is also documented in the databases at EUVD (EUVD-2025-26830) and CERT Bund (WID-SEC-2025-1944). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: Improper export of android application componentsCWE: CWE-926
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
04/05/2025 CVE reserved09/04/2025 Advisory disclosed
09/04/2025 VulDB entry created
09/07/2025 VulDB entry last update
Sources
Vendor: google.comAdvisory: android.googlesource.com
Status: Confirmed
CVE: CVE-2025-32347 (🔒)
GCVE (CVE): GCVE-0-2025-32347
GCVE (VulDB): GCVE-100-322651
EUVD: 🔒
CERT Bund: WID-SEC-2025-1944 - Android Patchday September 2025: Multiple Vulnerabilities
scip Labs: https://www.scip.ch/en/?labs.20150917
Entry
Created: 09/04/2025 21:53Updated: 09/07/2025 21:02
Changes: 09/04/2025 21:53 (55), 09/06/2025 03:18 (1), 09/06/2025 07:10 (1), 09/07/2025 21:02 (7)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.