What is CVE-2018-12716?A medium-severity flaw in Chromecast, explained.
CVE-2018-12716 is a medium-severity flaw (CVSS 4.3) in Chromecast from Google, published on 25 June 2018. It is not on the list of flaws known to be exploited today. The latest forecast puts its chance of use in the next 30 days at 0.7%. If you run an affected version, plan in the vendor’s fix.
Published 25 June 2018. Record last updated 7 November 2023. We keep this page's data up to date.
What is CVE-2018-12716? In plain terms.
An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can read some data.
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.
What kind of flaw is it?
- CWE-200Exposure of Sensitive Information to an Unauthorized Actor
How an attack on it works
Read straight from its severity rating, translated out of the shorthand.
- Where an attacker can beOn the same local network
- How hard it is to pull offEasy: no special conditions
- Login needed firstNo login needed
- Does someone have to clickNo, nobody has to do anything
- What an attacker getsCan read some data
Severity vector: CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Is CVE-2018-12716 being exploited? Not that we know of.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.7%. That can change at any time, which is why we keep watching.
Timeline
- Published
- Record last updated
CVE-2018-12716 scores 15. Action: Track.
We keep the score of every published flaw up to date as the evidence changes. Four things go into the score, and evidence that criminals are actually using it counts most. In order:
- Evidence it is being exploitedBiggest factor
- How severe it isStrong factor
- How widely exposed it isKey context
- Real threat activity around itKey context
85 and above is Critical. Anything confirmed as exploited is always marked for an emergency patch, whatever its score.
When CVE-2018-12716 matches software you track, it lands in your list with its score and the reasons behind it.
See your own ranked list →Who is affected by CVE-2018-12716? 4 products.
The published record lists 4 products from 1 vendor. If you run one of these, check your version, then go to the fix below.
- Hardware
Chromecast
by Google
Affected versionsversion not specified - Operating system
Chromecast Firmware
by Google
Affected versionsversion not specified - Hardware
Home
by Google
Affected versionsversion not specified - Operating system
Home Firmware
by Google
Affected versionsversion not specified
How do I fix CVE-2018-12716? Four steps.
- Check whether you run itCompare your versions with the affected products above. Not sure what you run? EdgeProtect can work it out from your public website, or you can pick it from a list.
- Apply the vendor’s fixInstall the latest update from the vendor. The references list where the vendor has published details.
- If you can’t patch todayFollow any mitigation the vendor publishes, and limit who can reach the affected system from the internet until the update is in.
- Keep an eye on itTrack the product and we tell you as soon as we spot this flaw on the list of exploited flaws, or a jump in its exploit likelihood.
References
4 links- Google to Fix Location Data Leak in Google Home Chromecast (opens in a new tab)krebsonsecurity.com · 2018
- Attacking Private Networks from the Internet with DNS Rebinding Ea7098a2d325 (opens in a new tab)medium.com
- Googles Newest Feature Find My Home (opens in a new tab)tripwire.com
- Chromecast Roku Sonos DNS Rebinding Vulnerability (opens in a new tab)wired.com
Does CVE-2018-12716 affect you? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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, wh...
- Matched to
- Chromecast on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
CVE-2018-12716 is a medium-severity flaw in Chromecast from Google, published on 25 June 2018. An attacker has to be on the same local network without logging in, and nobody has to click anything. If it works, the attacker can read some data.
It scores 4.3 out of 10 on the CVSS severity scale, which is medium. Our risk score for CVE-2018-12716 is 15 out of 100, which is Info. Its action is "Track". No sign of exploitation and a low forecast. Patch it in your normal update cycle.
It is not on the list of flaws known to be exploited today. The latest forecast puts the chance of it being used in the next 30 days at 0.7%. That can change at any time, which is why we keep watching.
For Chromecast from Google: version not specified. The record lists 4 products in all, each with its versions, under "Who is affected" on this page.
Install the update the vendor names in its advisory. If you can't patch today, follow the vendor's mitigation and limit who can reach the affected system from the internet.