CVE-2019-2014
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 · uneditedIn rw_t3t_handle_get_sc_poll_rsp of rw_t3t.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 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-120499324
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 confidenceIn the NFC subsystem's T3T (Type 3 Tag) handling code, the function rw_t3t_handle_get_sc_poll_rsp in rw_t3t.cc lacks proper bounds validation when processing poll responses from NFC tags. This missing check allows an attacker to trigger an out-of-bounds write operation by crafting a malicious NFC tag response, potentially achieving local privilege escalation. User interaction is required, likely involving the device processing a malicious NFC tag.
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= 7.0= 7.1.1= 7.1.2= 8.0= 8.1= 9.0CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Android version is affectedGo to Settings > About Phone > Android version, or run 'getprop ro.build.version.release' via ADB. Confirm the version is 7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0Affected if The Android version is one of the listed affected versions (7.0, 7.1.1, 7.1.2, 8.0, 8.1, or 9.0)
-
Confirm NFC is enabledGo to Settings > Network & Internet > NFC (or Settings > Connections > NFC on Samsung), or run 'settings get secure nfc_enabled' via ADB shell. NFC must be turned on for the device to process NFC tag responsesAffected if NFC is enabled and the device can receive NFC tag poll responses
-
Check security patch levelGo to Settings > About Phone > Build number (tap 7 times), then Settings > System > About Phone > Android security patch level, or run 'getprop ro.build.version.security_patch' via ADBAffected if The security patch level is earlier than November 2019, meaning the bounds check fix has not been applied
-
Verify NFC service is activeRun 'dumpsys nfc' via ADB shell to check if the NFC service is running and processing tagsAffected if The NFC service is active and capable of processing incoming NFC tag responses
You are affected if your device runs Android 7.0-9.0, has NFC enabled, and has a security patch level earlier than November 2019, allowing a malicious NFC tag to trigger the out-of-bounds write in rw_t3t_handle_get_sc_poll_rsp.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the Android security patch for the November 2019 bulletin (or later) which includes the bounds check fix in the NFC rw_t3t.cc component. For affected Android versions (7.0-9), verify the patch level is current.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-2014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-2014 in production — separate from our analysis above.
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.
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.
- 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