Read the docs
TI-2014-06580 Aliases CVE-2014-7914GHSA-xmxx-m7q8-x9xj

Incorrect authorization in Google Android

Priority LOW 36CWE-863Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · High · None
Fix status
Fixed

Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-863.

Summary

btif/src/btif_dm.c in Android before 5.1 does not properly enforce the temporary nature of a Bluetooth pairing, which allows user-assisted remote attackers to bypass intended access restrictions via crafted Bluetooth packets after the tapping of a crafted NFC tag.

Why it matters now

EPSS 0.00475 41st percentileScored 2026-11-07
Fix Fixed Android (Google): 5.1

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
GoogleAndroidbefore 5.15.1Patch availableCNA
  • Android VendorGoogle Affected before 5.1 Fixed in 5.1 Patch available CNA

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:o:google:android:*:*:*:*:*:*:*:*before 5.1VulnerableGoogle
  • cpe:2.3:o:google:android:*:*:*:*:*:*:*:* Versions before 5.1 Vulnerable ·Google

Remediation

  • Fix · CNA Android (Google) Fixed in 5.1

Timeline

  1. 2026-10-02 Threatist record created from CVE-2014-7914
  2. 2026-10-03 Alias added: GHSA-xmxx-m7q8-x9xj

References

Patch 1

  • TI-2026-42236 Improper authorization in Google Android KEVCVSS 3.1HIGH 8.8
  • TI-2025-30821 Use after free in Google Android KEVCVSS 3.1HIGH 8.8
  • TI-2023-17777 Improper privilege management in Google Android KEVCVSS 3.1HIGH 8.8
  • TI-2025-30872 Integer overflow in Google Android KEVCVSS 3.1HIGH 8.4
  • TI-2024-21766 there is a possible way to bypass due to a logic error in the code. KEVCVSS 3.1HIGH 8.1
  • TI-2025-30849 Missing authentication in Google Android KEVCVSS 3.1HIGH 7.8
See all 8410 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences