CVE-2018-6076: XSS
First published: Wed Mar 07 2018(Updated: )
An incorrect handling of url fragment identifiers flaw was found in the Blink component of the Chromium browser. Upstream bug(s): <a href="https://code.google.com/p/chromium/issues/detail?id=758523">https://code.google.com/p/chromium/issues/detail?id=758523</a> External References: <a href="https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html">https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html</a>
Credit: cve-coordination@google.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/chromium-browser | <65.0.3325.146 | 65.0.3325.146 |
| Google Chrome | <65.0.3325.146 | |
| Redhat Linux Desktop | =6.0 | |
| Redhat Linux Server | =6.0 | |
| Redhat Linux Workstation | =6.0 | |
| Debian Debian Linux | =9.0 | |
| debian/chromium-browser |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
- http://www.securityfocus.com/bid/103297
- https://access.redhat.com/errata/RHSA-2018:0484
- https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html
- https://crbug.com/758523
- https://www.debian.org/security/2018/dsa-4182
- https://code.google.com/p/chromium/issues/detail?id=758523
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1552502
- https://bugzilla.redhat.com/show_bug.cgi/show_bug.cgi?id=1552504
- https://bugzilla.redhat.com/show_bug.cgi?id=1552493
- https://security-tracker.debian.org/tracker/CVE-2018-6076
Frequently Asked Questions
What is the severity of CVE-2018-6076?
The severity of CVE-2018-6076 is medium, with a severity value of 6.1.
How does CVE-2018-6076 affect Google Chrome?
CVE-2018-6076 affects Google Chrome versions prior to 65.0.3325.146.
How can a remote attacker exploit CVE-2018-6076?
A remote attacker can exploit CVE-2018-6076 by performing a DOM based XSS attack via a crafted HTML page.
What is the remedy for CVE-2018-6076?
There is no specific remedy mentioned for CVE-2018-6076.
Where can I find more information about CVE-2018-6076?
You can find more information about CVE-2018-6076 at the following references: [1](https://security-tracker.debian.org/tracker/CVE-2018-6076), [2](https://code.google.com/p/chromium/issues/detail?id=758523), [3](https://chromereleases.googleblog.com/2018/03/stable-channel-update-for-desktop.html)
- collector/security-tracker-debian
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- collector/nvd-index
- agent/software-canonical-lookup-request
- agent/severity
- agent/references
- agent/author
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2018-6076
- agent/software-canonical-lookup
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/weakness
- agent/tags
- agent/description
- agent/event
- agent/trending
- package-manager/debian
- vendor/google
- canonical/google chrome
- vendor/redhat
- canonical/redhat linux desktop
- version/redhat linux desktop/6.0
- canonical/redhat linux server
- version/redhat linux server/6.0
- canonical/redhat linux workstation
- version/redhat linux workstation/6.0
- vendor/debian
- canonical/debian debian linux
- version/debian debian linux/9.0
- package-manager/redhat