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 |
|
No data.
No data.
No data available yet.
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.142% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-327 | |
| Metrics |
cvssV3_1
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Possible forging of AES‑256 CMAC in Android leading to local privilege escalation | |
| Weaknesses | CWE-330 |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Possible forging of AES‑256 CMAC in Android leading to local privilege escalation | |
| Weaknesses | CWE-330 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In aes256_cmac_sw of aes.rs, there is a possible way to forge message authentication codes over multi-block messages due to improperly used crypto. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
No data.