LiveActive security incident?Get immediate response
CVE Record

CVE-2020-0041: In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check.

In binder_transaction of binder.c, there is a possible out of bounds write due to an incorrect bounds check. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-145988638References: Upstream kernel

HighCVSS 7.8Known exploitedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-0041 is an Android kernel flaw in Binder that can let a local attacker gain higher privileges. It does not require user interaction, but the attacker must already have local execution privileges. CISA lists it as known exploited, so unpatched Android devices should be treated as urgent exposure.

Executive priority

Treat this as a high-priority mobile fleet issue because CISA identifies known exploitation and successful abuse could give an attacker broad control over an affected device. Patchable devices should be updated promptly; unsupported devices need replacement or risk acceptance.

Technical view

The issue is an incorrect bounds check in binder_transaction in binder.c, causing a possible out-of-bounds write. The CVSS vector is local, low complexity, low privileges, no user interaction, with high confidentiality, integrity, and availability impact. The affected product is Android kernel.

Likely exposure

Exposure is likely on Android devices using affected Android kernel builds that have not received the relevant Android or device-vendor security update. Risk is highest where attackers can run local code, such as through a malicious app or prior compromise.

Exploitation context

Active exploitation is supported by CISA KEV listing for CVE-2020-0041. The provided sources do not describe exploit mechanics, campaigns, affected device models, or attacker groups, so those details should not be assumed.

Researcher notes

Evidence supports Android kernel exposure and local privilege escalation through Binder. The bundle identifies CWE-20 and Android ID A-145988638, but does not provide commit details, exploit indicators, affected device models, or confirmed fixed kernel versions.

Mitigation direction

  • Prioritize Android devices that lack the relevant Android security bulletin or OEM kernel update.
  • Check device vendor guidance for fixed builds and patch availability.
  • Retire or isolate devices that cannot receive vendor security updates.
  • Restrict installation of untrusted apps on unmanaged or legacy Android devices.
  • Monitor mobile fleet compliance against required Android security patch levels.

Validation and detection

  • Inventory Android devices and record OS, kernel, and security patch level.
  • Compare device patch state against Android and OEM guidance for CVE-2020-0041.
  • Identify devices unable to receive further security updates.
  • Review mobile threat telemetry for signs of local privilege escalation or suspicious apps.
  • Confirm compensating controls for devices awaiting remediation.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-0041 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.8 (3.1)
Known Exploited
Yes
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CISA KEV status

Status
Known exploited
Source
CISA / ADP
Date added
Not provided

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H1.85.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2020-0041Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/aAndroidAndroid kernelListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.