dbcve.org
FedoraOperating system · Fedoraproject

CVE-2020-0081

HIGH · 7.8 CVSS v3.1 Published 2020-04-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In finalize of AssetManager.java, there is possible memory corruption due to a double free. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android-8.0 Android-8.1 Android-9 Android-10Android ID: A-144028297

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A double-free vulnerability exists in the finalize method of Android's AssetManager.java. When the finalize() method is called, it attempts to free memory that may have already been freed, causing memory corruption. This can be exploited to achieve local privilege escalation without requiring user interaction, affecting Android versions 8.0 through 10.

MitigationApply Android security patches from Google (A-144028297). Organizations should ensure devices receive the latest system updates. For internal applications, review usage of AssetManager and implement additional input validation where possible.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 32
AndroidOperating system
Affected:= 8.0= 8.1= 9.0= 10.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify your operating system
    Determine if you are running Google Android on a mobile device or Fedora 32 Linux distribution. For Android: check Settings > About Phone. For Fedora: run 'cat /etc/os-release'.
    Affected if The system is either Google Android 8.0-10.0 or Fedora 32 with Android tooling installed.
  2. Check Android version on mobile devices
    On Android devices, go to Settings > About Phone and verify the Android version. Affected versions are 8.0, 8.1, 9.0, and 10.0.
    Affected if The Android version is 8.0, 8.1, 9.0, or 10.0.
  3. Check security patch level on Android
    On Android devices, go to Settings > About Phone > Security patch level. The vulnerability was fixed in the March 2020 Android Security Patch Level (A-144028297).
    Affected if The security patch level is earlier than March 2020 or the patch level cannot be verified.
  4. Check for android-tools package on Fedora 32
    On Fedora 32 systems, run 'rpm -qa | grep -i android' or 'dnf list installed | grep -i android' to identify installed Android-related packages.
    Affected if Android-related packages from Fedora 32 are installed.
  5. Check package version on Fedora 32
    For any installed android packages on Fedora 32, run 'rpm -q --changelog <package-name>' or check if updates are available via 'dnf check-update' to determine if the CVE fix has been applied.
    Affected if The installed android packages have not been updated to include the CVE-2020-0081 fix.

You are affected if you are running Google Android versions 8.0 through 10.0 with a security patch level earlier than March 2020, or Fedora 32 with unpatched Android tooling packages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Android security patches from Google (A-144028297). Organizations should ensure devices receive the latest system updates. For internal applications, review usage of AssetManager and implement additional input validation where possible.

Fix this in Fedora Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $12,352.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-0081 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-0081 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data