CVE-2018-6152: Google Chrome vulnerability
Google · Chrome
Vendor fix available · Affected: Google Chrome · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 71% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
The implementation of the Page.downloadBehavior backend unconditionally marked downloaded files as safe, regardless of file type in Google Chrome prior to 66.0.3359.117 allowed an attacker who convinced a user to install a malicious extension to potentially perform a sandbox escape via a crafted HTML page and user interaction.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Google · Chromebefore 66.0.3359.117
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- Published
- December 2018
CoverageNo articles yet
No CyberSIXT article names CVE-2018-6152 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-434cwe.mitre.org
- Vendor advisoryaccess.redhat.com
- Vendor advisorysecurity.gentoo.org
- Vendor advisorydebian.org
- chromereleases.googleblog.com/2018/04/stable-channel-update-for-chromereleases.googleblog.com
- crbug.com/805445crbug.com
- securityfocus.com/bid/104887securityfocus.com