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.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Android |
|
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.169% probability within 30 days)
Key SSVC decision points have not yet been added.
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google android |
|
| Vendors & Products |
Google
Google android |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Crypto Key Recovery and Auth Tag Forgery in Android | |
| Weaknesses | CWE-286 CWE-312 CWE-327 |
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Local Crypto Key Recovery and Auth Tag Forgery in Android | |
| Weaknesses | CWE-286 CWE-312 CWE-327 |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | In multiple locations, there is a possible way to recover cryptographic keys and forge authentication tags due to improperly used crypto. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation. | |
| References |
|
No weakness.