Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Android | unaffected |
|
Configuration 1 [-]
|
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Android |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.068% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Missing Permission Check in CarDevicePolicyService |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:o:google:android:14.0:*:*:*:*:*:*:* cpe:2.3:o:google:android:15.0:*:*:*:*:*:*:* |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Missing Permission Check in CarDevicePolicyService |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Bypassed Disclaimer Dialog in Android CarDevicePolicyService | |
| Weaknesses | CWE-285 |
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-862 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Privilege Escalation via Bypassed Disclaimer Dialog in Android CarDevicePolicyService | |
| Weaknesses | CWE-285 |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In setUserDisclaimerAcknowledged of CarDevicePolicyService.java, there is a possible way to bypass the user dialog when adding an account to a managed device due to a missing permission check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|