Threats / Android / CVE-2020-0041
CVE-2020-0041
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
Android Kernel vulnerability
Android Kernel binder_transaction function contains an out-of-bounds write vulnerability due to incorrect bounds checking, enabling local privilege escalation.
Verdict
Today item — known-exploited.
A bounds check failure in the Android Kernel binder driver allows local attackers to write out-of-bounds memory, achieving privilege escalation. Active exploitation observed in coordinated attack chains.
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
2 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 2021-11-03).
Probability (EPSS)
EPSS 0.03246 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Android, Android Kernel. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-20 Improper Input Validation.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 gain local code execution on an Android device through an initial vulnerability or user interaction.
Business
An attacker establishes a foothold on the device with unprivileged application-level access.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious binder transaction that bypasses the bounds check in binder_transaction, writing data outside allocated memory.
Business
The out-of-bounds write corrupts kernel memory structures, creating conditions for privilege escalation.
3
Lateral reach — past segmentation narrative 3
Attacker
I escalate my privileges to kernel or system level by exploiting the memory corruption.
Business
The attacker gains full device control, bypassing security boundaries and accessing sensitive user data.
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.