CVE-2018-6052: Infoleak
Lack of support for a non standard no-referrer policy value in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to obtain referrer details from a web page that had thought it had opted out of sending referrer data.
Other sources
The following flaw was identified in the Chromium browser: incomplete no-referrer policy implementation.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=615608
External References:
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop24.html
— Red Hat
Credit
Affected Software
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2018-6031
- CVE-2018-6032
- CVE-2018-6033
- CVE-2018-6034
- CVE-2018-6035
- CVE-2018-6036
- CVE-2018-6037
- CVE-2018-6038
- CVE-2018-6039
- CVE-2018-6040
- CVE-2018-6041
- CVE-2018-6042
- CVE-2018-6043
- CVE-2018-6045
- CVE-2018-6046
- CVE-2018-6047
- CVE-2018-6048
- CVE-2017-15420
- CVE-2018-6049
- CVE-2018-6050
- CVE-2018-6051
- CVE-2018-6053
- CVE-2018-6054
Frequently Asked Questions
What is the severity of CVE-2018-6052?
CVE-2018-6052 has been rated as a medium severity vulnerability.
How do I fix CVE-2018-6052?
To fix CVE-2018-6052, update to versions 64.0.3282.119 or later of Google Chrome or Chromium.
What are the affected versions for CVE-2018-6052?
CVE-2018-6052 affects Google Chrome versions prior to 64.0.3282.119.
Which software packages are impacted by CVE-2018-6052?
CVE-2018-6052 impacts the Chromium browser and Google Chrome across various operating systems, including Debian and Red Hat.
Can attackers exploit CVE-2018-6052 remotely?
Yes, CVE-2018-6052 allows remote attackers to obtain referrer details from a web page, indicating a potential exploit vector.