AndroidOperating system · Google

CVE-2019-2010

HIGH · 7.8 CVSS v3.0 Published 2019-06-19

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

NVD · unedited

In phNxpNciHal_process_ext_rsp of phNxpNciHal_ext.cc, there is a possible out-of-bound write due to a missing 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-7.0 Android-7.1.1 Android-7.1.2 Android-8.0 Android-8.1 Android-9Android ID: A-118152591

Technical summary

dbcve analysis · high confidence

A missing bounds check in the phNxpNciHal_process_ext_rsp function within the NFC Controller Interface (NCI) vendor extension handler (phNxpNciHal_ext.cc) allows an out-of-bounds write. This memory corruption vulnerability in the NFC HAL can be exploited locally to escalate privileges without requiring additional execution privileges or user interaction.

MitigationApply the Android security patch level that includes the fix for A-118152591, or obtain a vendor-specific patch from the NFC chipset provider (NXP) that adds proper bounds validation before writing to the response buffer.

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

Affected products & versions

NVD · CPE data

AndroidOperating system

Affected:= 7.0= 7.1.1= 7.1.2= 8.0= 8.1= 9.0

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Check Android OS version

Go to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB shell

Affected if The displayed version matches 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0
Verify NFC hardware is present

Check for NFC capability in Settings > Connected devices > NFC, or run 'getprop ro.hardware.nfc' via ADB shell

Affected if NFC hardware is reported as present on the device
Confirm NFC is enabled

Check that NFC is turned on in Settings > Connected devices > NFC, or check the secure setting 'nfc_on' via 'settings get secure nfc_on' via ADB

Affected if NFC is currently enabled on the device
Identify NFC HAL vendor implementation

Check for the NXP NFC HAL library on the system, typically found in /vendor/lib/hw/ or /system/lib/hw/ directories containing 'nfc' and 'nxp' in the filename

Affected if The device uses an NXP-based NFC HAL implementation (phNxpNciHal)
Check firmware version for NFC controller

Use an NFC debugging app or check NFC service logs via 'logcat -d | grep -i nci' to identify the NFC controller firmware version

Affected if The NFC controller firmware is an unpatched version from the affected Android release timeframe

A device is affected if it runs Android 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0, has NFC hardware present and enabled, and uses an NXP NFC HAL implementation with the vulnerable phNxpNciHal_process_ext_rsp function.

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

Remediation

From vendor data

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply the Android security patch level that includes the fix for A-118152591, or obtain a vendor-specific patch from the NFC chipset provider (NXP) that adds proper bounds validation before writing to the response buffer.

Fix this in Android Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing6.0 h
Review / QA2.0 h

14.0 hours of engineering $2,380

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

source.android.comVendor Advisory
nvd.nist.govNVD record

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2019-2010?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.8 High

Exploit likelihood EPSS, next 30 days 0.2%

Affects: Android

Remediation

A high-priority fix

Fix this in Android 14 hrs · Moderate

Typical engagement from $2,380

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2019-2010 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References