CVE-2018-6160
JavaScript alert handling in Prompts in Google Chrome prior to 68.0.3440.75 allowed a remote...
JavaScript alert handling in Prompts in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- None
- User interaction
- Required
What an attacker can affect
- Confidentiality
- None
- Integrity
- High
- Availability
- None
Exploit likelihood
What each source reports
NVD Score used
6.5
JavaScript alert handling in Prompts in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
- Record
CVE-2018-6160- CVSS 3.0
- 6.5 Medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N - CVSS 2.0
- 4.3 Medium
AV:N/AC:M/Au:N/C:N/I:P/A:N - Weakness
- CWE-20
- Updated
- 2026-11-02
CVE List No score
JavaScript alert handling in Prompts in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
- Record
CVE-2018-6160- Updated
- 2026-11-02
EUVDEUVD-2018-17923 No score
JavaScript alert handling in Prompts in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
- Record
EUVD-2018-17923- Updated
- 2026-11-03
GitHub AdvisoriesGHSA-6qcp-7hqx-rm6q
6.5
JavaScript alert handling in Prompts in Google Chrome prior to 68.0.3440.75 allowed a remote...
JavaScript alert handling in Prompts in Google Chrome prior to 68.0.3440.75 allowed a remote attacker to spoof the contents of the Omnibox (URL bar) via a crafted HTML page.
- Record
GHSA-6qcp-7hqx-rm6q- CVSS 3.0
- 6.5 Medium
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N - Weakness
- CWE-20
- Updated
- 2026-11-02
OSVMGASA-2018-0343 No score
Updated chromium-browser-stable packages fix security vulnerabilities
Chromium-browser 68.0.3440.106 fixes security issues:
Multiple flaws were found in the way Chromium 67.0.3396.87 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-2018-4117, CVE-2018-6044, CVE-2018-6153, CVE-2018-6154, CVE-2018-6155, CVE-2018-6156, CVE-2018-6157, CVE-2018-6158, CVE-2018-6159, CVE-2018-6160, CVE-2018-6161, CVE-2018-6162, CVE-2018-6163, CVE-2018-6164, CVE-2018-6165, CVE-2018-6166, CVE-2018-6167, CVE-2018-6168, CVE-2018-6169, CVE-2018-6170, CVE-2018-6171, CVE-2018-6172, CVE-2018-6173, CVE-2018-6174, CVE-2018-6175, CVE-2018-6176, CVE-2018-6177, CVE-2018-6178, CVE-2018-6179)
Upstream also reported for release 68.0.3440.75 that three additional flaws were fixed in earlier (unspecified) chromium releases but not listed in the release notes for those releases. (CVE-2018-6150, CVE-2018-6151, CVE-2018-6152)
- Record
MGASA-2018-0343- 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:6 From an advisory covering 32 CVEs |
before 68.0.3440.106-1.mga6 | 68.0.3440.106-1.mga6 |
chromiumopenSUSE:Tumbleweed From an advisory covering 1081 CVEs |
before 93.0.4577.82-1.1 | 93.0.4577.82-1.1 |
chromiumopenSUSE:Tumbleweed From an advisory covering 2310 CVEs |
before 113.0.5672.92-1.1 | 113.0.5672.92-1.1 |
History
| Recorded | Changed | Sources |
|---|---|---|
| affected, facts | ||
| 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-2018-6160 is a medium vulnerability (CVSS 6.5) in Google Chrome, published August 17, 2018. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 0.97%, the 62nd percentile. No source names a fixed version.
References
chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop.html
security.gentoo.org/glsa/201808-01
securityfocus.com/bid/104887
crbug.com/839822
nvd.nist.gov/vuln/detail/CVE-2018-6160
github.com/advisories/GHSA-6qcp-7hqx-rm6q
Show 194 moreShow less
advisories.mageia.org/MGASA-2018-0343.html
bugs.mageia.org/show_bug.cgi?id=23364
chromereleases.googleblog.com/2018/06/stable-channel-update-for-desktop_25.html
chromereleases.googleblog.com/2018/07/stable-channel-update-for-desktop_31.html
chromereleases.googleblog.com/2018/08/stable-channel-update-for-desktop.html
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-5068
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
suse.com/security/cve/CVE-2018-17470
suse.com/security/cve/CVE-2018-17471
suse.com/security/cve/CVE-2018-17472
suse.com/security/cve/CVE-2018-17473
suse.com/security/cve/CVE-2018-17474
suse.com/security/cve/CVE-2018-17475
suse.com/security/cve/CVE-2018-17476
suse.com/security/cve/CVE-2018-17477
suse.com/security/cve/CVE-2018-17478
suse.com/security/cve/CVE-2018-17479
suse.com/security/cve/CVE-2018-17480
suse.com/security/cve/CVE-2018-17481
suse.com/security/cve/CVE-2018-18335
suse.com/security/cve/CVE-2018-18336
suse.com/security/cve/CVE-2018-18337
suse.com/security/cve/CVE-2018-18338
suse.com/security/cve/CVE-2018-18339
Left out here: 2,121 references. The JSON record has them.