CVE-2023-20963
CVE-2023-20963 is a high-severity vulnerability (CVSS 3.1 base score 7.8). Android Framework contains an unspecified vulnerability that allows for privilege escalation after updating an app to a higher Target SDK with no additional execution privileges needed. CISA added it to the Known Exploited Vulnerabilities catalog on 2023-04-13, with a remediation due date of 2023-05-04 for US federal civilian agencies. As of 2026-11-22, EPSS estimates a 1.5% probability of exploitation in the next 30 days, in the 74th percentile of scored CVEs.
Updated
- CVSS 3.1
- 7.8 HIGH
- EPSS
- 1.5% (74th pct)
- CISA KEV
- Exploited
- Published
- 2023-03-24
- Weakness
- CWE-295
Android Framework Privilege Escalation Vulnerability is confirmed as actively exploited and is listed in the CISA KEV catalog.
Required action
Apply updates per vendor instructions.
CISA notes
https://source.android.com/docs/security/bulletin/2023-03-01; https://nvd.nist.gov/vuln/detail/CVE-2023-20963
Description
In WorkSource, there is a possible parcel mismatch. This could lead to local escalation of privilege 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-220302519
Key Findings
as of 2026-11-22- CISA added CVE-2023-20963 to the KEV catalog 20 days after its CVE record was published. The median for entries added in 2023 is 12 days.
- It is one of 17 Android entries in the CISA KEV catalog, and one of 2 added in 2023.
- Its current EPSS score (1.5%) is higher than that of 4% of CISA KEV entries.
Severity
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HOpen 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 total, 2025-01-28).
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. Forensic triage means assessing the asset to determine whether it has been compromised.
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-11 Android-12 Android-12L Android-13 |
References
1 linksOther references
Record Details
- Published
- 2023-03-24
- Last updated
- 2025-10-21
- Assigner (CNA)
- google_android
- Credited to
- -
More from Android
Android Framework Privilege Escalation Vulnerability
Android Framework Integer Overflow Vulnerability
Android Framework Privilege Escalation Vulnerability
Android Framework Privilege Escalation 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.