CVE-2017-5124: Google Chrome prior to 62.0.3202.62 vulnerability
Google · Google Chrome prior to 62.0.3202.62
Vendor fix available · Affected: Google Chrome prior to 62.0.3202.62 · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 92% of scored CVEs
Not scored yet. The CVE record carries no CVSS score.
DescriptionCVE.org
Incorrect application of sandboxing in Blink in Google Chrome prior to 62.0.3202.62 allowed a remote attacker to inject arbitrary scripts or HTML (UXSS) via a crafted MHTML page.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- Google Chrome prior to 62.0.3202.62Google Chrome prior to 62.0.3202.62
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
- Weakness
- Cross-site Scripting
- Vendor
- Published
- February 2018
CoverageNo articles yet
No CyberSIXT article names CVE-2017-5124 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-79cwe.mitre.org
- Vendor advisorydebian.org
- Vendor advisoryaccess.redhat.com
- Vendor advisorysecurity.gentoo.org
- securityfocus.com/bid/101482securityfocus.com
- reddit.com/r/netsec/comments/7cus2h/chrome_61_uxss_exploit_cve20reddit.com
- chromereleases.googleblog.com/2017/10/stable-channel-update-for-chromereleases.googleblog.com
- crbug.com/762930crbug.com
- chromium.googlesource.com/chromium/src/+/4558c2885e618557a674660chromium.googlesource.com
- github.com/Bo0oM/CVE-2017-5124github.com