LiveActive security incident?Get immediate response
CVE Record

CVE-2018-9119: An attacker with physical access to a BrilliantTS FUZE card (MCU firmware 0.1.73, BLE firmware 0.7.4) can u...

An attacker with physical access to a BrilliantTS FUZE card (MCU firmware 0.1.73, BLE firmware 0.7.4) can unlock the card, extract credit card numbers, and tamper with data on the card via Bluetooth because no authentication is needed, as demonstrated by gatttool.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-9119 concerns a BrilliantTS FUZE payment card that can expose stored credit card numbers if an attacker has physical access to the card. The reported issue is Bluetooth access without authentication. The public sources describe data extraction and tampering risks, but do not cite active exploitation or a confirmed vendor patch.

Executive priority

Prioritize if the organization issued, tested, stored, or supported FUZE cards. The risk is not internet-scale, but compromise could expose payment card data and create fraud, privacy, and incident-response obligations. If no FUZE cards exist, business urgency is low.

Technical view

The source bundle describes unauthenticated Bluetooth access to BrilliantTS FUZE cards running MCU firmware 0.1.73 and BLE firmware 0.7.4. Public research demonstrated unlocking the card, reading stored credit card numbers, and modifying card data. The CVE record provides no CVSS score, CWE, CPE, or authoritative remediation details.

Likely exposure

Exposure appears limited to users or organizations still holding BrilliantTS FUZE cards with MCU firmware 0.1.73 and BLE firmware 0.7.4. The attack requires physical access to the card and Bluetooth proximity. No broader affected product list is provided in the source bundle.

Exploitation context

Public research and an advisory described practical exploitation, but the source bundle does not cite real-world attacks. The CVE is not listed as CISA KEV. Treat this as a demonstrated local physical-access risk, not evidence of active mass exploitation.

Researcher notes

The key weakness is unauthenticated Bluetooth access to sensitive card functions. The available sources identify affected firmware versions and demonstrated outcomes, but they do not provide CVSS, CWE classification, vendor-fixed versions, or confirmed exploitation in the wild. Validate exposure through asset evidence, not assumptions.

Mitigation direction

  • Check BrilliantTS or FUZE vendor guidance for firmware updates or retirement advice.
  • Retire affected cards if no supported fix is available.
  • Avoid storing active payment card numbers on affected devices.
  • Reissue stored payment cards if unauthorized physical access is suspected.
  • Apply strict physical custody controls for any remaining devices.

Validation and detection

  • Inventory any BrilliantTS FUZE cards still in use or storage.
  • Confirm MCU and BLE firmware versions against the affected versions.
  • Determine whether live payment card numbers are stored on affected devices.
  • Review loss, loaner, repair, or disposal records for physical access exposure.
  • Document vendor response status and any compensating controls.
Prepared
Confidence
medium
Sources
6

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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 · low confidence lookup

CVE-2018-9119 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
5Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.