CVE-2017-15405

Description

Inappropriate symlink handling and a race condition in the stateful recovery feature implementation could lead to a persistance established by a malicious code running with root privileges in cryptohomed in Google Chrome on Chrome OS prior to 61.0.3163.113 allowed a local attacker to execute arbitrary code via a crafted HTML page.

Category

7.0
CVSS
Severity: High
CVSS 3.0 •
CVSS 2.0 •
EPSS 0.01%
Affected: Google Chrome
Published at:
Updated at:

References

Link Tags
https://crbug.com/766276
https://chromereleases.googleblog.com/2017/10/stable-channel-updates-for-chrome-os.html

Frequently Asked Questions

What is the severity of CVE-2017-15405?
CVE-2017-15405 has been scored as a high severity vulnerability.
How to fix CVE-2017-15405?
To fix CVE-2017-15405, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-15405 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2017-15405 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2017-15405?
CVE-2017-15405 affects Google Chrome.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.