Vulnerability in Google Android

CVE-2020-0438

In the AIBinder_Class constructor of ibinder.cpp, there is a possible arbitrary code execution due to uninitialized data. This could lead to local escalation of privilege if a process were using libbinder_ndk in a vulnerable way with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-11 Android-10Android ID: A-161812320

Published · last modified .

CVSS v3 metric

CVSS v3 base score 7.8 (High). Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H.

EPSS exploit prediction

EPSS: 0.002 (5.7th percentile), scored .

Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 6th percentile — 5.7% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.

EPSS trend (30 days)EPSS over the last 30 days for CVE-2020-0438: held from 0.002 to 0.002.

EPSS over last 30 days · oldest: 0.002 · newest: 0.002 · change: 0.000

Affected products

  • Google Android — versions 10.0, 11.0
  • Android — versions Android-11 Android-10

Weakness classification (CWE)

Public proof-of-concept exploits

References

Frequently asked questions

What is CVE-2020-0438?
CVE-2020-0438 is a high-severity vulnerability in Google Android, classified under Access of Uninitialized Pointer. CVSS score: 7.8/10. Published 2020-11-10.
How severe is CVE-2020-0438?
High severity. CVSS v3 base score is 7.8 out of 10.
Is CVE-2020-0438 known to be exploited?
1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.