dbcve.org
AndroidOperating system · Google

CVE-2020-0076

MEDIUM · 6.7 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 →
69/100
Remediation priority · Elevated
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 get_auth_result of the FPC IRIS TrustZone app, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege with System execution privileges needed. User interaction is not needed for exploitation.Product: AndroidVersions: Android kernelAndroid ID: A-146056878

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

An out-of-bounds write vulnerability exists in the get_auth_result function of the FPC IRIS TrustZone application due to a missing bounds check. This allows a local attacker with System-level privileges to escalate to higher privileges. The vulnerability is in the secure TrustZone environment, which handles biometric (iris) authentication on Android devices.

MitigationApply the Android security patch for Android ID A-146056878, which updates the FPC IRIS TrustZone component with proper bounds validation. Users should ensure their devices receive the latest Android security updates.

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
AndroidOperating system
Affected:all versions

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/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. Check if device uses FPC iris biometric hardware
    Inspect /system/etc/firmware/ or /vendor/firmware/ for FPC iris-related firmware files, or check /sys/class/biometric/ for FPC iris sensor entries. On some devices, 'getprop ro.hardware.fingerprint' or checking /proc/fingerprint/ vendor may reveal FPC hardware presence.
    Affected if FPC (Fingerprint Cards) iris/biometric hardware is present and the device has not received the Android security patch for A-146056878
  2. Verify TrustZone component version
    If accessible, check the TrustZone version or the FPC IRIS TrustZone application version via vendor-specific diagnostic tools or /vendor/etc/fpc/ directory containing TrustZone-related binaries.
    Affected if The FPC IRIS TrustZone application version is unpatched and the get_auth_result function lacks bounds validation
  3. Confirm iris authentication is enrolled or available
    Check if iris authentication is available or enrolled on the device by examining Settings > Security > Iris or using 'dumpsys iris' command if available (requires root or system-level access).
    Affected if Iris authentication is enabled and the underlying TrustZone component is vulnerable
  4. Check Android security patch level
    Run 'getprop ro.build.version.security_patch' to retrieve the installed security patch level. Compare against the patch date for A-146056878.
    Affected if The security patch level predates the fix for A-146056878 or shows no patch date for this specific Android ID

A device is affected if it contains FPC iris biometric hardware, has not received the specific Android security update for CVE-2020-0076, and has the vulnerable TrustZone component present in its secure enclave.

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 the Android security patch for Android ID A-146056878, which updates the FPC IRIS TrustZone component with proper bounds validation. Users should ensure their devices receive the latest Android security updates.

Fix this in Android Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-0076 — 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-0076 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