CVE-2023-20963 — base
CVE-2023-20963 is a CWE-295 vulnerability in platform/frameworks/base. It is in CISA's Known Exploited Vulnerabilities catalog (added 2023-04-13) — treat it as actively exploited and patch now. A fix is available for platform/frameworks/base — see the affected versions and patch details below.
Exploitation Status
Actively exploited in the wild
- Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2023-04-13. Federal agencies were required to remediate by 2023-05-04.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2023-20963.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/base📦platform/frameworks/baseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Android packages — download data is not available via public APIs for these ecosystems.
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦Android | platform/frameworks/base | ≥ 13-next:0&&< 13-next:2023-03-01 | 13-next:2023-03-01 |
| 📦Android | platform/frameworks/base | ≥ 11:0&&< 11:2023-03-01 | 11:2023-03-01 |
| 📦Android | platform/frameworks/base | ≥ 12:0&&< 12:2023-03-01 | 12:2023-03-01 |
| 📦Android | platform/frameworks/base | ≥ 12L:0&&< 12L:2023-03-01 | 12L:2023-03-01 |
| 📦Android | platform/frameworks/base | ≥ 13:0&&< 13:2023-03-01 | 13:2023-03-01 |
Affected Products
androidgoogleResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
In WorkSource, there is a possible parcel mismatch. This could lead to l…
In WorkSource, there is a possible parcel mismatch. This could lead to l…
In WorkSource, there is a possible parcel mismatch. This could lead to l…
In WorkSource, there is a possible parcel mismatch. This could lead to l…
In WorkSource, there is a possible parcel mismatch. This could lead to l…
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for platform/frameworks/base, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update platform/frameworks/base to 13-next:2023-03-01 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-20963 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2023-20963 in your dependencies?
Find it across Android, including transitive dependencies.