CVE-2017-5068
Incorrect handling of picture ID in WebRTC in Google Chrome prior to 58.0.3029.96 for Mac,...
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.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- High
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- High
- Integrity
- High
- Availability
- High
Exploit likelihood
What each source reports
NVD Score used
7.5
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.
- Record
CVE-2017-5068- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H - CVSS 2.0
- 5.1 Medium
AV:N/AC:H/Au:N/C:P/I:P/A:P - Weakness
- CWE-362
- Updated
- 2026-11-02
CVE List No score
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.
- Record
CVE-2017-5068- Updated
- 2026-11-02
EUVDEUVD-2017-14177 No score
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.
- Record
EUVD-2017-14177- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-j36c-g9g3-m3ph
7.5
Incorrect handling of picture ID in WebRTC in Google Chrome prior to 58.0.3029.96 for Mac,...
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.
- Record
GHSA-j36c-g9g3-m3ph- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H - Weakness
- CWE-362
- Updated
- 2026-11-02
OSVRHSA-2017:1228
8.8
Red Hat Security Advisory: chromium-browser security update
- Record
RHSA-2017:1228- CVSS 3.0
- 8.8 High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
OSVUBUNTU-CVE-2017-5068
7.5
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.
- Record
UBUNTU-CVE-2017-5068- CVSS 3.1
- 7.5 High
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H - CVSS 3.0
- 7.5 High
CVSS:3.0/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H - Updated
- 2026-11-02
Show 5 moreShow less
OSVMGASA-2017-0317 No score
Chromium-browser 60.0.3112.101 fixes security issues
Multiple flaws were found in the way Chromium 57 processes various types of web content, where loading a web page containing malicious content could cause Chromium to crash, execute arbitrary code, or disclose sensitive information. (CVE-2017-5057, CVE-2017-5058, CVE-2017-5059, CVE-2017-5060, CVE-2017-5061, CVE-2017-5062, CVE-2017-5063, CVE-2017-5064, CVE-2017-5065, CVE-2017-5066, CVE-2017-5067, CVE-2017-5068, CVE-2017-5069, CVE-2017-5070, CVE-2017-5071, CVE-2017-5072, CVE-2017-5073, CVE-2017-5074, CVE-2017-5075, CVE-2017-5076, CVE-2017-5077, CVE-2017-5078, CVE-2017-5079, CVE-2017-5080, CVE-2017-5081, CVE-2017-5082, CVE-2017-5083, CVE-2017-5085, CVE-2017-5086, CVE-2017-5087, CVE-2017-5088, CVE-2017-5089, CVE-2017-5091, CVE-2017-5092, CVE-2017-5093, CVE-2017-5094, CVE-2017-5095, CVE-2017-5096, CVE-2017-5097, CVE-2017-5098, CVE-2017-5099, CVE-2017-5100, CVE-2017-5101, CVE-2017-5102, CVE-2017-5103, CVE-2017-5104, CVE-2017-5105, CVE-2017-5106, CVE-2017-5107, CVE-2017-5108, CVE-2017-5109, CVE-2017-5110, CVE-2017-6991)
- Record
MGASA-2017-0317- Updated
- 2026-11-02
OSVopenSUSE-SU-2017:1190-1 No score
Security update for Chromium
This update to Chromium 58.0.3029.96 fixes one security issue:
- CVE-2017-5068: race condition in WebRTC (bsc#1037594)
- Record
openSUSE-SU-2017:1190-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2017:1194-1 No score
Security update for Chromium
This update to Chromium 58.0.3029.96 fixes one security issue:
- CVE-2017-5068: race condition in WebRTC (bsc#1037594)
- Record
openSUSE-SU-2017:1194-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:10681-1 No score
chromedriver-93.0.4577.82-1.1 on GA media
These are all security issues fixed in the chromedriver-93.0.4577.82-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:10681-1- Updated
- 2026-11-02
OSVopenSUSE-SU-2024:12948-1 No score
ungoogled-chromium-113.0.5672.92-1.1 on GA media
These are all security issues fixed in the ungoogled-chromium-113.0.5672.92-1.1 package on the GA media of openSUSE Tumbleweed.
- Record
openSUSE-SU-2024:12948-1- Updated
- 2026-11-02
Affected products
Affected packages
| Package | Affected | Fixed |
|---|---|---|
chromium-browser-stableMageia:5 |
before 60.0.3112.101-1.mga5 | 60.0.3112.101-1.mga5 |
libwebpMageia:5 |
before 0.4.3-1.1.mga5 | 0.4.3-1.1.mga5 |
chromium-browser-stableMageia:6 |
before 60.0.3112.101-1.mga6 | 60.0.3112.101-1.mga6 |
chromium-browserRed Hat:rhel_extras:6 |
before 0:58.0.3029.96-1.el6_9 | 0:58.0.3029.96-1.el6_9 |
chromium-browser-debuginfoRed Hat:rhel_extras:6 |
before 0:58.0.3029.96-1.el6_9 | 0:58.0.3029.96-1.el6_9 |
chromium-browserUbuntu:14.04:LTS |
before 58.0.3029.96-0ubuntu0.14.04.1174, plus listed versions 29.0.1547.65-0ubuntu231.0.1650.63-0ubuntu1~20131204.132.0.1700.107-0ubuntu1~20140204.977.133.0.1750.152-0ubuntu1~pkg995.134.0.1847.116-0ubuntu2 Show 25 moreShow less36.0.1985.125-0ubuntu1.14.04.0~pkg102937.0.2062.94-0ubuntu0.14.04.1~pkg104237.0.2062.120-0ubuntu0.14.04.1~pkg104938.0.2125.111-0ubuntu0.14.04.1.106139.0.2171.65-0ubuntu0.14.04.1.106440.0.2214.94-0ubuntu0.14.04.1.106840.0.2214.111-0ubuntu0.14.04.1.106941.0.2272.76-0ubuntu0.14.04.1.107643.0.2357.81-0ubuntu0.14.04.1.108943.0.2357.130-0ubuntu0.14.04.1.109244.0.2403.89-0ubuntu0.14.04.1.109545.0.2454.85-0ubuntu0.14.04.1.109745.0.2454.101-0ubuntu0.14.04.1.109947.0.2526.73-0ubuntu0.14.04.1.110647.0.2526.106-0ubuntu0.14.04.1.110748.0.2564.82-0ubuntu0.14.04.1.110848.0.2564.116-0ubuntu0.14.04.1.111149.0.2623.87-0ubuntu0.14.04.1.111249.0.2623.108-0ubuntu0.14.04.1.111350.0.2661.102-0ubuntu0.14.04.1.111751.0.2704.79-0ubuntu0.14.04.1.112152.0.2743.116-0ubuntu0.14.04.1.113453.0.2785.143-0ubuntu0.14.04.1.114253.0.2785.143-0ubuntu0.14.04.1.114558.0.3029.81-0ubuntu0.14.04.1172 |
58.0.3029.96-0ubuntu0.14.04.1174 |
oxide-qtUbuntu:16.04:LTS |
All versions, plus listed versions 1.9.5-0ubuntu11.10.3-0ubuntu0.15.10.11.10.3-0ubuntu0.15.10.21.11.3-0ubuntu31.11.4-0ubuntu1 Show 17 moreShow less1.11.5-0ubuntu11.12.5-0ubuntu11.12.6-0ubuntu11.12.7-0ubuntu11.13.6-0ubuntu11.14.7-0ubuntu11.14.9-0ubuntu0.16.04.11.15.7-0ubuntu0.16.04.11.15.8-0ubuntu0.16.04.11.16.5-0ubuntu0.16.04.11.17.7-0ubuntu0.16.04.11.17.9-0ubuntu0.16.04.11.18.3-0ubuntu0.16.04.11.18.5-0ubuntu0.16.04.11.19.4-0ubuntu0.16.04.11.20.4-0ubuntu0.16.04.11.21.5-0ubuntu0.16.04.1 |
None known |
chromiumSUSE:Package Hub 12 SP2 |
before 58.0.3029.96-17.1 | 58.0.3029.96-17.1 |
chromiumopenSUSE:Tumbleweed |
before 93.0.4577.82-1.1 | 93.0.4577.82-1.1 |
chromiumopenSUSE:Tumbleweed |
before 113.0.5672.92-1.1 | 113.0.5672.92-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| aliases | EUVD | |
| first indexed | CVE List, GitHub Advisories, NVD, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
CVE-2017-5068 is a high vulnerability (CVSS 7.5) in Google Chrome, published May 6, 2017. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.02%, the 63rd percentile. Fixed in chromium-browser-stable 60.0.3112.101-1.mga5.
References
access.redhat.com/errata/RHSA-2017:1228
chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop.html
securityfocus.com/bid/98288
crbug.com/679306
security.gentoo.org/glsa/201706-20
nvd.nist.gov/vuln/detail/CVE-2017-5068
Show 194 moreShow less
github.com/advisories/GHSA-j36c-g9g3-m3ph
advisories.mageia.org/MGASA-2017-0317.html
bugs.mageia.org/show_bug.cgi?id=20708
chromereleases.googleblog.com/2017/04/stable-channel-update-for-desktop.html
chromereleases.googleblog.com/2017/05/stable-channel-update-for-desktop_9.html
chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop.html
chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_15.html
chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_20.html
chromereleases.googleblog.com/2017/06/stable-channel-update-for-desktop_26.html
chromereleases.googleblog.com/2017/07/stable-channel-update-for-desktop.html
chromereleases.googleblog.com/2017/08/stable-channel-update-for-desktop.html
chromereleases.googleblog.com/2017/08/stable-channel-update-for-desktop_14.html
access.redhat.com/security/updates/classification
bugzilla.redhat.com/show_bug.cgi?id=1448031
security.access.redhat.com/data/csaf/v2/advisories/2017/rhsa-2017_1228.json
access.redhat.com/security/cve/CVE-2017-5068
cve.org/CVERecord?id=CVE-2017-5068
ubuntu.com/security/CVE-2017-5068
bugs.chromium.org/p/chromium/issues/detail?id=679306
lists.opensuse.org/archives/list/[email protected]/thread/UD4Q5UWWOUNI4KNXFOOAQINMQ3THLWMC
bugzilla.suse.com/1037594
suse.com/security/cve/CVE-2017-5068
lists.opensuse.org/archives/list/[email protected]/thread/MIVTE275MNRZH6MRS5CFAIREEHEO5CU2
suse.com/security/cve/CVE-2017-11215
suse.com/security/cve/CVE-2017-11225
suse.com/security/cve/CVE-2017-15386
suse.com/security/cve/CVE-2017-15387
suse.com/security/cve/CVE-2017-15388
suse.com/security/cve/CVE-2017-15389
suse.com/security/cve/CVE-2017-15390
suse.com/security/cve/CVE-2017-15391
suse.com/security/cve/CVE-2017-15392
suse.com/security/cve/CVE-2017-15393
suse.com/security/cve/CVE-2017-15394
suse.com/security/cve/CVE-2017-15395
suse.com/security/cve/CVE-2017-15396
suse.com/security/cve/CVE-2017-15398
suse.com/security/cve/CVE-2017-15399
suse.com/security/cve/CVE-2017-15407
suse.com/security/cve/CVE-2017-15408
suse.com/security/cve/CVE-2017-15409
suse.com/security/cve/CVE-2017-15410
suse.com/security/cve/CVE-2017-15411
suse.com/security/cve/CVE-2017-15412
suse.com/security/cve/CVE-2017-15413
suse.com/security/cve/CVE-2017-15415
suse.com/security/cve/CVE-2017-15416
suse.com/security/cve/CVE-2017-15417
suse.com/security/cve/CVE-2017-15418
suse.com/security/cve/CVE-2017-15419
suse.com/security/cve/CVE-2017-15420
suse.com/security/cve/CVE-2017-15422
suse.com/security/cve/CVE-2017-15423
suse.com/security/cve/CVE-2017-15424
suse.com/security/cve/CVE-2017-15425
suse.com/security/cve/CVE-2017-15426
suse.com/security/cve/CVE-2017-15427
suse.com/security/cve/CVE-2017-15429
suse.com/security/cve/CVE-2017-15430
suse.com/security/cve/CVE-2017-5006
suse.com/security/cve/CVE-2017-5007
suse.com/security/cve/CVE-2017-5008
suse.com/security/cve/CVE-2017-5009
suse.com/security/cve/CVE-2017-5010
suse.com/security/cve/CVE-2017-5011
suse.com/security/cve/CVE-2017-5012
suse.com/security/cve/CVE-2017-5013
suse.com/security/cve/CVE-2017-5014
suse.com/security/cve/CVE-2017-5015
suse.com/security/cve/CVE-2017-5016
suse.com/security/cve/CVE-2017-5017
suse.com/security/cve/CVE-2017-5018
suse.com/security/cve/CVE-2017-5019
suse.com/security/cve/CVE-2017-5020
suse.com/security/cve/CVE-2017-5021
suse.com/security/cve/CVE-2017-5022
suse.com/security/cve/CVE-2017-5023
suse.com/security/cve/CVE-2017-5024
suse.com/security/cve/CVE-2017-5025
suse.com/security/cve/CVE-2017-5026
suse.com/security/cve/CVE-2017-5030
suse.com/security/cve/CVE-2017-5035
suse.com/security/cve/CVE-2017-5041
suse.com/security/cve/CVE-2017-5044
suse.com/security/cve/CVE-2017-5052
suse.com/security/cve/CVE-2017-5053
suse.com/security/cve/CVE-2017-5054
suse.com/security/cve/CVE-2017-5055
suse.com/security/cve/CVE-2017-5056
suse.com/security/cve/CVE-2017-5057
suse.com/security/cve/CVE-2017-5058
suse.com/security/cve/CVE-2017-5059
suse.com/security/cve/CVE-2017-5060
suse.com/security/cve/CVE-2017-5061
suse.com/security/cve/CVE-2017-5062
suse.com/security/cve/CVE-2017-5063
suse.com/security/cve/CVE-2017-5064
suse.com/security/cve/CVE-2017-5065
suse.com/security/cve/CVE-2017-5066
suse.com/security/cve/CVE-2017-5067
suse.com/security/cve/CVE-2017-5069
suse.com/security/cve/CVE-2017-5070
suse.com/security/cve/CVE-2017-5071
suse.com/security/cve/CVE-2017-5072
suse.com/security/cve/CVE-2017-5073
suse.com/security/cve/CVE-2017-5074
suse.com/security/cve/CVE-2017-5075
suse.com/security/cve/CVE-2017-5076
suse.com/security/cve/CVE-2017-5077
suse.com/security/cve/CVE-2017-5078
suse.com/security/cve/CVE-2017-5079
suse.com/security/cve/CVE-2017-5080
suse.com/security/cve/CVE-2017-5081
suse.com/security/cve/CVE-2017-5082
suse.com/security/cve/CVE-2017-5083
suse.com/security/cve/CVE-2017-5085
suse.com/security/cve/CVE-2017-5086
suse.com/security/cve/CVE-2017-5087
suse.com/security/cve/CVE-2017-5088
suse.com/security/cve/CVE-2017-5089
suse.com/security/cve/CVE-2017-5091
suse.com/security/cve/CVE-2017-5092
suse.com/security/cve/CVE-2017-5093
suse.com/security/cve/CVE-2017-5094
suse.com/security/cve/CVE-2017-5095
suse.com/security/cve/CVE-2017-5096
suse.com/security/cve/CVE-2017-5097
suse.com/security/cve/CVE-2017-5098
suse.com/security/cve/CVE-2017-5099
suse.com/security/cve/CVE-2017-5100
suse.com/security/cve/CVE-2017-5101
suse.com/security/cve/CVE-2017-5102
suse.com/security/cve/CVE-2017-5103
suse.com/security/cve/CVE-2017-5104
suse.com/security/cve/CVE-2017-5105
suse.com/security/cve/CVE-2017-5106
suse.com/security/cve/CVE-2017-5107
suse.com/security/cve/CVE-2017-5108
suse.com/security/cve/CVE-2017-5109
suse.com/security/cve/CVE-2017-5110
suse.com/security/cve/CVE-2017-5111
suse.com/security/cve/CVE-2017-5112
suse.com/security/cve/CVE-2017-5113
suse.com/security/cve/CVE-2017-5114
suse.com/security/cve/CVE-2017-5115
suse.com/security/cve/CVE-2017-5116
suse.com/security/cve/CVE-2017-5117
suse.com/security/cve/CVE-2017-5118
suse.com/security/cve/CVE-2017-5119
suse.com/security/cve/CVE-2017-5120
suse.com/security/cve/CVE-2017-5121
suse.com/security/cve/CVE-2017-5122
suse.com/security/cve/CVE-2017-5124
suse.com/security/cve/CVE-2017-5125
suse.com/security/cve/CVE-2017-5126
suse.com/security/cve/CVE-2017-5127
suse.com/security/cve/CVE-2017-5128
suse.com/security/cve/CVE-2017-5129
suse.com/security/cve/CVE-2017-5130
suse.com/security/cve/CVE-2017-5131
suse.com/security/cve/CVE-2017-5132
suse.com/security/cve/CVE-2017-5133
suse.com/security/cve/CVE-2017-7000
suse.com/security/cve/CVE-2018-16065
suse.com/security/cve/CVE-2018-16066
suse.com/security/cve/CVE-2018-16067
suse.com/security/cve/CVE-2018-16068
suse.com/security/cve/CVE-2018-16069
suse.com/security/cve/CVE-2018-16070
suse.com/security/cve/CVE-2018-16071
suse.com/security/cve/CVE-2018-16073
suse.com/security/cve/CVE-2018-16074
suse.com/security/cve/CVE-2018-16075
suse.com/security/cve/CVE-2018-16076
suse.com/security/cve/CVE-2018-16077
suse.com/security/cve/CVE-2018-16078
suse.com/security/cve/CVE-2018-16079
suse.com/security/cve/CVE-2018-16080
suse.com/security/cve/CVE-2018-16081
suse.com/security/cve/CVE-2018-16082
suse.com/security/cve/CVE-2018-16083
suse.com/security/cve/CVE-2018-16084
suse.com/security/cve/CVE-2018-16085
suse.com/security/cve/CVE-2018-16086
suse.com/security/cve/CVE-2018-16087
suse.com/security/cve/CVE-2018-16088
suse.com/security/cve/CVE-2018-17462
suse.com/security/cve/CVE-2018-17463
suse.com/security/cve/CVE-2018-17464
suse.com/security/cve/CVE-2018-17465
suse.com/security/cve/CVE-2018-17466
suse.com/security/cve/CVE-2018-17467
suse.com/security/cve/CVE-2018-17468
suse.com/security/cve/CVE-2018-17469
Left out here: 2,138 references. The JSON record has them.