CVE-2018-6048: Referrer policy bypass in Blink
A referrer policy bypass flaw was found in the Blink component of the Chromium browser.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=763194
External References:
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop24.html
Other sources
Insufficient policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially leak referrer information via a crafted HTML page.
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-2017-15420
- CVE-2018-6049
- CVE-2018-6050
- CVE-2018-6051
- CVE-2018-6052
- CVE-2018-6053
- CVE-2018-6054
Frequently Asked Questions
What is the severity of CVE-2018-6048?
CVE-2018-6048 is classified as a medium severity vulnerability affecting the Blink component of the Chromium browser.
How do I fix CVE-2018-6048?
To mitigate CVE-2018-6048, update your Chromium browser to version 64.0.3282.119 or later.
Which versions of Chromium are affected by CVE-2018-6048?
CVE-2018-6048 affects versions of Chromium prior to 64.0.3282.119.
Is CVE-2018-6048 applicable to Google Chrome?
Yes, CVE-2018-6048 impacts Google Chrome versions before 64.0.3282.119.
What component is involved in CVE-2018-6048?
CVE-2018-6048 involves a referrer policy bypass flaw in the Blink component of the Chromium browser.