{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2017-5068 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-5068 is a high-severity vulnerability in Google Chrome, published on 27 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2017-5068 and fix it if it is affected.\n\nWhat it is: CVE-2017-5068 is a high-severity vulnerability in Google Chrome, published on 27 Oct 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2017-5068 in the wild and no public exploit code.\n\nAffected product: Google Chrome. 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-2017-5068/ (Markdown: https://insights.sbomify.com/CVE-2017-5068/index.md)","id":"CVE-2017-5068","markdown":"https://insights.sbomify.com/CVE-2017-5068/index.md","name":"CVE-2017-5068","record":{"aliases":["GHSA-j36c-g9g3-m3ph","RHSA-2017:1228","UBUNTU-CVE-2017-5068","openSUSE-SU-2017:1190-1","openSUSE-SU-2017:1194-1"],"analysis":{"component_type":"browser","fix_type":"upgrade","impacts":["other"],"network_reachable":"yes","non_default_config":false,"product_category":"Google Chrome","requires_auth":"none","summary":"A remote attacker can trigger a race condition in WebRTC via a crafted HTML page, potentially leading to undefined behavior or crashes.","user_interaction":"required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Chrome","cpe":[{"product":"chrome","vendor":"google"},{"product":"enterprise_linux_desktop","vendor":"redhat"},{"product":"enterprise_linux_server","vendor":"redhat"},{"product":"enterprise_linux_workstation","vendor":"redhat"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"description":"Incorrect handling of picture ID in WebRTC in Google Chrome prior to 58.0.3029.96 for Mac, Windows, and Linux allowed a remote attacker to trigger a race condition via a crafted HTML page.","ecosystems":["Red Hat:rhel_extras:6","SUSE:Package Hub 12 SP2"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Race condition in Google Chrome prior to 58.0.3029.96 for Mac, Windows and Linux","id":"CVE-2017-5068","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"google:chrome","products":["google:chrome","redhat:enterprise_linux_desktop","redhat:enterprise_linux_server","redhat:enterprise_linux_workstation"],"type":"race_condition","year":"2017"},"n_packages":4,"n_references":5,"next":{"headline":"Cross-site scripting in Google Chrome prior to 58.0.3029.81 for Linux, Windows and Mac, and 58.0.3029.83 for Android","id":"CVE-2017-5069"},"packages":[{"ecosystem":"Red Hat:rhel_extras:6","fixed":["0:58.0.3029.96-1.el6_9"],"introduced":["0"],"last_affected":[],"package":"chromium-browser","purl":"pkg:rpm/redhat/chromium-browser","source":"RHSA-2017:1228"},{"ecosystem":"Red Hat:rhel_extras:6","fixed":["0:58.0.3029.96-1.el6_9"],"introduced":["0"],"last_affected":[],"package":"chromium-browser-debuginfo","purl":"pkg:rpm/redhat/chromium-browser-debuginfo","source":"RHSA-2017:1228"},{"ecosystem":"SUSE:Package Hub 12 SP2","fixed":["58.0.3029.96-17.1"],"introduced":["0"],"last_affected":[],"package":"chromium","purl":"pkg:rpm/suse/chromium\u0026distro=SUSE%20Package%20Hub%2012%20SP2","source":"openSUSE-SU-2017:1190-1"},{"ecosystem":"SUSE:Package Hub 12 SP2","fixed":["58.0.3029.96-17.1"],"introduced":["0"],"last_affected":[],"package":"chromium","purl":"pkg:rpm/suse/chromium\u0026distro=SUSE%20Package%20Hub%2012%20SP2","source":"openSUSE-SU-2017:1194-1"}],"prev":{"headline":"Other in Google Chrome prior to 58.0.3029.81 for Linux, Windows and Mac","id":"CVE-2017-5067"},"products":["Google Chrome prior to 58.0.3029.96 for Mac, Windows and Linux"],"published":"2017-10-27","related":[{"cvss_score":9.6,"headline":"Google Chromium GPU Heap Buffer Overflow","id":"CVE-2022-4135","kev_date_added":"2022-11-28","published":"2022-11-25"},{"cvss_score":9.6,"headline":"Google Chrome Use-After-Free","id":"CVE-2020-16017","kev_date_added":"2021-11-03","published":"2021-01-08"},{"cvss_score":9.6,"headline":"Google Chrome for Android UI Heap Buffer Overflow","id":"CVE-2020-16010","kev_date_added":"2021-11-03","published":"2020-11-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out of Bounds Write","id":"CVE-2026-87491","kev_date_added":"2026-09-09","published":"2026-09-09"},{"cvss_score":8.8,"headline":"Google Chromium V8 Type Confusion","id":"CVE-2026-85046","kev_date_added":"2026-09-04","published":"2026-09-03"},{"cvss_score":8.8,"headline":"Google Chromium V8 Out-of-Bounds Read and Write","id":"CVE-2026-11645","kev_date_added":"2026-06-09","published":"2026-06-08"},{"cvss_score":8.8,"headline":"Google Dawn Use-After-Free","id":"CVE-2026-5281","kev_date_added":"2026-04-01","published":"2026-04-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"Red Hat","prefix":"RHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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-08-05","vendors":["n/a"]},"summary":"A remote attacker can trigger a race condition in WebRTC via a crafted HTML page, potentially leading to undefined behavior or crashes.","url":"https://insights.sbomify.com/CVE-2017-5068/"}