Threats / Android / CVE-2023-20963
CVE-2023-20963
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Android Framework vulnerability
Android Framework privilege escalation vulnerability allowing unprivileged attackers to gain elevated permissions through app updates targeting higher SDK levels.
Verdict
Today item — known-exploited.
An unspecified privilege escalation flaw in Android Framework permits attackers to escalate privileges without additional execution rights by updating applications to higher Target SDK versions. Active exploitation observed in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Public proof-of-concept exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
4 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-04-13).
Probability (EPSS)
EPSS 0.01445 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Android, Framework. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-295 Improper Certificate Validation — weakness family: Authentication.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft or modify an Android application to target a higher SDK level, exploiting the Framework's handling of permission grants during app updates.
Business
Device security posture degrades as unprivileged applications gain unauthorized system-level permissions, enabling unauthorized data access or device control.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I distribute the malicious app update through legitimate channels or social engineering, triggering the vulnerability when users install or update the application.
Business
User trust erodes and incident response costs escalate as compromised devices proliferate across the installed base.
3
Lateral reach — past segmentation narrative 3
Attacker
I leverage the escalated privileges to access sensitive user data, modify system settings, or persist malicious code on the device.
Business
Privacy violations and regulatory exposure increase; customer remediation and notification obligations create operational and reputational damage.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05
Coverage & confidence
— what we know, and what we don’tEstablished (cited)
Coverage gaps — stated, not hidden
Disclosure & credit2
Catalogued by google_androidCNA
Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.