CVE-2018-6040: Medium severity google chrome (trace event) vulnerability
Insufficient policy enforcement in Blink in Google Chrome prior to 64.0.3282.119 allowed a remote attacker to potentially bypass content security policy via a crafted HTML page.
Other sources
The following flaw was identified in the Chromium browser: content security policy bypass.
Upstream bug(s):
https://code.google.com/p/chromium/issues/detail?id=778658
External References:
https://chromereleases.googleblog.com/2018/01/stable-channel-update-for-desktop24.html
— Red Hat
Credit
Affected Software
Remediation
Patch Available
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-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-6052
- CVE-2018-6053
- CVE-2018-6054
Frequently Asked Questions
What is the severity of CVE-2018-6040?
CVE-2018-6040 is classified as a high severity vulnerability due to its potential to allow attackers to bypass content security policy.
How do I fix CVE-2018-6040?
To fix CVE-2018-6040, users should update their browser to version 64.0.3282.119 or later.
What does CVE-2018-6040 exploit?
CVE-2018-6040 exploits insufficient policy enforcement in Blink, allowing content security policy to be bypassed.
Which versions of Chrome are affected by CVE-2018-6040?
CVE-2018-6040 affects Google Chrome versions prior to 64.0.3282.119.
Is there a workaround for CVE-2018-6040?
There are no effective workarounds for CVE-2018-6040; updating to the secure version is recommended.