Google Android 13/14/15/16 Shared.java getCallingAppName permission
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.1 | $5k-$25k | 0.00 |
Summary
A vulnerability has been found in Google Android 13/14/15/16 and classified as critical. This vulnerability affects the function getCallingAppName of the file Shared.java. This manipulation causes permission.
This vulnerability appears as CVE-2025-32323. The attack requires local access. There is no available exploit.
It is suggested to install a patch to address this issue.
Details
A vulnerability classified as critical was found in Google Android 13/14/15/16. Affected by this vulnerability is the function getCallingAppName of the file Shared.java. The manipulation with an unknown input leads to a permission vulnerability. The CWE definition for the vulnerability is CWE-275. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
In getCallingAppName of Shared.java, there is a possible way to trick users into granting file access via deceptive text in a permission popup due to improper input validation. 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-32323 since 04/05/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/07/2025). MITRE ATT&CK project uses the attack technique T1222 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-1944). Several companies clearly confirm that VulDB is the primary source for best 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: PermissionCWE: CWE-275 / CWE-266
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-32323 (🔒)
GCVE (CVE): GCVE-0-2025-32323
GCVE (VulDB): GCVE-100-322633
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:50Updated: 09/07/2025 20:14
Changes: 09/04/2025 21:50 (57), 09/07/2025 20:14 (7)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.