{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2018-12716 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2018-12716 yet. Limit exposure of the affected software until one is available.","what":"CVE-2018-12716 is a medium-severity vulnerability in n/a, published on 25 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2018-12716 and fix it if it is affected.\n\nWhat it is: CVE-2018-12716 is a medium-severity vulnerability in n/a, published on 25 Jun 2018. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2018-12716 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2018-12716/ (Markdown: https://insights.sbomify.com/CVE-2018-12716/index.md)","id":"CVE-2018-12716","markdown":"https://insights.sbomify.com/CVE-2018-12716/index.md","name":"CVE-2018-12716","record":{"aliases":["GHSA-8j32-3cqp-g7rx"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Google Home Chromecast","requires_auth":"none","summary":"Remote attackers can determine physical locations of web browsers by exploiting DNS rebinding to read scan results from Google Home or Chromecast devices.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"chromecast_firmware","vendor":"google"},{"product":"home_firmware","vendor":"google"}],"cvss":{"score":4.3,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2018-12716","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2018"},"n_packages":0,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2018-12735"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2018-12715"},"products":["n/a"],"published":"2018-06-25","related":[{"cvss_score":10,"headline":"Chromecast Bootloader \u0026 Kernel-level code-execution including compromise of user-data","id":"CVE-2023-48426","kev_date_added":null,"published":"2024-04-05"},{"cvss_score":9.8,"headline":"Missing authorization in Android","id":"CVE-2023-48417","kev_date_added":null,"published":"2023-12-11"},{"cvss_score":9.8,"headline":"Privilege escalation in Android","id":"CVE-2023-48424","kev_date_added":null,"published":"2023-12-11"},{"cvss_score":9.8,"headline":"Code injection in Android","id":"CVE-2023-48425","kev_date_added":null,"published":"2023-12-11"},{"cvss_score":9.8,"headline":"Code injection in Android","id":"CVE-2023-6181","kev_date_added":null,"published":"2023-12-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["n/a"]},"summary":"Remote attackers can determine physical locations of web browsers by exploiting DNS rebinding to read scan results from Google Home or Chromecast devices.","url":"https://insights.sbomify.com/CVE-2018-12716/"}