Security readout for executives and security teams
Plain-English summary
This issue affects Android devices before 5.1. A crafted NFC tag could set up a Bluetooth pairing condition that should have been temporary, but was not properly limited. An attacker still needs user interaction and Bluetooth/NFC proximity, so this is not a broad internet-facing threat.
Executive priority
Treat this as a legacy-device hygiene issue, not an emergency internet-scale flaw. Priority rises if the organization still uses pre-5.1 Android devices in sensitive environments or with NFC/Bluetooth enabled.
Technical view
In Android Bluedroid, btif/src/btif_dm.c did not properly enforce the temporary nature of a Bluetooth pairing. Public CVE text says user-assisted remote attackers could bypass intended access restrictions using crafted Bluetooth packets after a crafted NFC tag was tapped. The affected range is Android before 5.1.
Likely exposure
Exposure is mainly legacy Android devices running versions before 5.1, especially where NFC and Bluetooth are enabled. Modern managed fleets should have low exposure unless old devices remain in use.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. The described attack requires a user to tap a crafted NFC tag, followed by crafted Bluetooth packets, implying proximity and user assistance.
Researcher notes
Evidence is limited to the CVE description and Android source reference. No CVSS, CWE, exploit confirmation, or detailed vendor advisory is included in the provided bundle, so assessment confidence is constrained.
Mitigation direction
- Upgrade affected Android devices to 5.1 or later where supported.
- Retire unsupported Android devices that cannot receive platform fixes.
- Disable NFC or Bluetooth on legacy devices when not operationally required.
- Check OEM or Google guidance for device-specific patch availability.
Validation and detection
- Inventory Android devices and identify versions before 5.1.
- Confirm whether NFC and Bluetooth are enabled on legacy devices.
- Review mobile device management records for Android version compliance.
- Validate that unsupported devices are isolated, replaced, or removed.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2014-7914 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://android.googlesource.com/platform/external/bluetooth/bluedroid/+/0360aa7c418152a3e5e335a065ac3629cbb09559CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.