CVE-2023-21087
published 2023-04-19CVE-2023-21087: In PreferencesHelper.java, an uncaught exception may cause the device to get stuck in a boot loop. This could lead to local persistent denial of service with…
PriorityP421medium5.5CVSS 3.1
AVLACLPRLUINSUCNINAH
EPSS
0.09%
0.6th percentile
In PreferencesHelper.java, an uncaught exception may cause the device to get stuck in a boot loop. This could lead to local persistent denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-261723753
Affected
11 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| android | — | — | |
| android | — | — | |
| android | — | — | |
| android | — | — | |
| android | — | — | |
| android | — | — | |
| platform | frameworks_base | >= 11:0 < 11:2023-07-01 | 11:2023-07-01 |
| platform | frameworks_base | >= 12:0 < 12:2023-07-01 | 12:2023-07-01 |
| platform | frameworks_base | >= 12L:0 < 12L:2023-07-01 | 12L:2023-07-01 |
| platform | frameworks_base | >= 13-next:0 < 13-next:2023-07-01 | 13-next:2023-07-01 |
| platform | frameworks_base | >= 13:0 < 13:2023-07-01 | 13:2023-07-01 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
CVE-2023-21087: In PreferencesHelper
osv·2023-07-01
CVE-2023-21087 CVE-2023-21087: In PreferencesHelper
In PreferencesHelper.java, an uncaught exception may cause the device to get stuck in a boot loop. This could lead to local persistent denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.
GHSA
GHSA-f9vx-6cfw-vgpg: In PreferencesHelper
ghsa_unreviewed·2023-04-19
CVE-2023-21087 [MEDIUM] CWE-248 GHSA-f9vx-6cfw-vgpg: In PreferencesHelper
In PreferencesHelper.java, an uncaught exception may cause the device to get stuck in a boot loop. This could lead to local persistent denial of service with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-12 Android-12L Android-13Android ID: A-261723753
Android
CVE-2023-21087: Android Security Bulletin 2023-07-01
CVE: CVE-2023-21087
Severity: HIGH
Type: DoS
Affected AOSP versions: 11, 12, 12L, 13
References: A-261723753
vendor_android·2023-07-01·CVSS 5.5
CVE-2023-21087 [MEDIUM] CVE-2023-21087: Android Security Bulletin 2023-07-01
CVE: CVE-2023-21087
Severity: HIGH
Type: DoS
Affected AOSP versions: 11, 12, 12L, 13
References: A-261723753
Android Security Bulletin 2023-07-01
CVE: CVE-2023-21087
Severity: HIGH
Type: DoS
Affected AOSP versions: 11, 12, 12L, 13
References: A-261723753
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
CWE
Uncaught Exception
mitre_cwe·CVSS 7.5
[HIGH] CWE-248 Uncaught Exception
CWE-248: Uncaught Exception
An exception is thrown from a function, but it is not caught.
When an exception is not caught, it may cause the program to crash or expose sensitive information.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Availability, Confidentiality. Impact: DoS: Crash, Exit, or Restart, Read Application Data. An uncaught exception could cause the system to be placed in a state that could lead to a crash, exposure of sensitive information or other unintended behaviors.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this
CWE
Incorrect Control Flow Scoping
mitre_cwe·CVSS 7.4
[HIGH] CWE-705 Incorrect Control Flow Scoping
CWE-705: Incorrect Control Flow Scoping
The product does not properly return control flow to the proper location after it has completed a task or detected an unusual condition.
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Other. Impact: Alter Execution Logic, Other.
Detection Methods:
Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external comp
2023-04-19
Published