LiveActive security incident?Get immediate response
CVE Record

CVE-2018-12716: The API service on Google Home and Chromecast devices before mid-July 2018 does not prevent DNS rebinding a...

The API service on Google Home and Chromecast devices before mid-July 2018 does not prevent DNS rebinding attacks from reading the scan_results JSON data, which allows remote attackers to determine the physical location of most web browsers by leveraging the presence of one of these devices on its local network, extracting the scan_results bssid fields, and sending these fields in a geolocation/v1/geolocate Google Maps Geolocation API request.

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

Security readout for executives and security teams

Plain-English summary

This issue let a malicious website abuse DNS rebinding to query vulnerable Google Home or Chromecast devices on the visitor’s local network. The exposed Wi-Fi scan data could be converted into an approximate physical location. The business risk is privacy and location disclosure, not direct device takeover based on the supplied sources.

Executive priority

Treat this as a targeted privacy and location-disclosure risk. It is not presented as active exploitation or remote code execution. Prioritize inventory and network hygiene, especially where consumer IoT devices sit on corporate or executive networks.

Technical view

Google Home and Chromecast API services before mid-July 2018 did not prevent DNS rebinding access to scan_results JSON. An attacker-controlled site could read BSSID fields from a local device and use Google Maps Geolocation API data to infer the browser user’s physical location. No CVSS, CWE, or CPE data is supplied.

Likely exposure

Exposure is most likely where legacy or unpatched Google Home or Chromecast devices share a network with user browsers. Current exposure is unclear from the bundle and should be treated as limited if devices received vendor updates after mid-July 2018.

Exploitation context

The source bundle describes public research and reporting, but KEV is false and no cited source in the bundle establishes active exploitation. Exploitation required a browser reaching attacker-controlled web content while a vulnerable device was reachable on the same local network.

Researcher notes

Evidence is strongest for vulnerable Google Home and Chromecast API behavior before mid-July 2018. The bundle does not provide CVSS, affected CPEs, detailed patch identifiers, or current exploit telemetry. Avoid assuming Roku or Sonos are affected by this CVE unless separately sourced.

Mitigation direction

  • Confirm Google Home and Chromecast devices are updated beyond mid-July 2018 vendor fixes.
  • Check current Google guidance for any remaining supported-device recommendations.
  • Segment consumer IoT devices away from sensitive corporate networks.
  • Use DNS rebinding protections where available in DNS, browser, or gateway controls.
  • Remove unsupported or unmanaged consumer IoT devices from business networks.

Validation and detection

  • Inventory Google Home and Chromecast devices on office, guest, and lab networks.
  • Verify firmware or update status for discovered devices.
  • Confirm IoT devices cannot be reached from sensitive user or server segments.
  • Review DNS security controls for rebinding protections.
  • Document any legacy devices that cannot receive vendor updates.
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-12716 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.