CVE-2023-21237
CVE-2023-21237 is a medium-severity vulnerability (CVSS 3.1 base score 6.2). Android Pixel contains a vulnerability in the Framework component, where the UI may be misleading or insufficient, providing a means to hide a foreground service notification. CISA added it to the Known Exploited Vulnerabilities catalog on 2024-03-05, with a remediation due date of 2024-03-26 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 0.3% probability of exploitation in the next 30 days, in the 18th percentile of scored CVEs.
Updated
- CVSS 3.1
- 6.2 MEDIUM
- EPSS
- 0.3% (18th pct)
- CISA KEV
- Exploited
- Published
- 2023-06-28
- Weakness
- CWE-200
Android Pixel Information Disclosure Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
CISA notes
https://source.android.com/docs/security/bulletin/pixel/2023-06-01; https://nvd.nist.gov/vuln/detail/CVE-2023-21237
Description
In applyRemoteView of NotificationContentInflater.java, there is a possible way to hide foreground service notification due to misleading or insufficient UI. This could lead to local information disclosure with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-13Android ID: A-251586912
Key Findings
as of 2026-11-22- CISA added CVE-2023-21237 to the KEV catalog 251 days after its CVE record was published. The median for entries added in 2024 is 21.5 days.
- It is one of 17 Android entries in the CISA KEV catalog, and one of 6 added in 2024.
Severity
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NOpen in CVSS calculator Remediation Timeline
BOD 26-04, US federal agenciesDeadlines for US federal civilian agencies under Table 1 of CISA BOD 26-04, from the CVE's KEV status (listed) and CISA's SSVC values (automatable no, technical impact partial, 2024-03-05).
How the timeline is set
Table 1 of CISA's Binding Operational Directive 26-04 sets the time US federal civilian agencies have to remediate a vulnerability. It depends on four inputs: whether the asset is publicly exposed, whether the CVE is in the KEV catalog, whether an adversary can automate its exploitation, and whether exploitation gives partial or total control of the asset, which SSVC calls technical impact. CISA publishes the last three for every CVE through services such as its Vulnrichment program.
Days are calendar days. The clock starts at whichever comes first: CISA adds the CVE to the KEV catalog, or the agency identifies the vulnerability on an asset and reports it to its Continuous Diagnostics and Mitigation (CDM) dashboard. A publicly exposed asset is accessible to unauthenticated or untrusted entities via public networks, such as the internet.
CISA calculates the KEV due date with the same table, using its own evidence on whether the vulnerability is present in a publicly exposed asset. Each agency makes the final exposure decision for each of its assets.
Affected Products
| Vendor | Product | Affected versions |
|---|---|---|
| - | Android | Android-13 |
References
1 linksOther references
Record Details
- Published
- 2023-06-28
- Last updated
- 2025-10-21
- Assigner (CNA)
- google_android
- Credited to
- -
More from Android
Android Pixel Privilege Escalation Vulnerability
Android Pixel Privilege Escalation Vulnerability
Android Pixel Information Disclosure Vulnerability
Android Kernel Use-After-Free Vulnerability
CVE record data © The MITRE Corporation, used under the CVE Terms of Use. Exploited-in-the-wild data from the CISA Known Exploited Vulnerabilities catalog (CC0). Exploit prediction scores by FIRST EPSS (first.org/epss). Alert titles and links from CISA cybersecurity alerts. This site is not affiliated with or endorsed by MITRE, NVD, CISA, or FIRST.