CVE-2017-15405: Race Condition

Published Jan 9, 2019
·
Updated

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.

Affected Software

1 affected component
Google Chrome<61.0.3163.113

Event History

Jan 9, 2019
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
DescriptionWeakness

Frequently Asked Questions

1

What is the severity of CVE-2017-15405?

CVE-2017-15405 is classified as a high severity vulnerability due to its potential for remote code execution with root privileges.

2

How do I fix CVE-2017-15405?

To fix CVE-2017-15405, upgrade Google Chrome to version 61.0.3163.113 or later.

3

What type of vulnerability is CVE-2017-15405?

CVE-2017-15405 is an inappropriate symlink handling vulnerability combined with a race condition.

4

Who is affected by CVE-2017-15405?

CVE-2017-15405 affects users of Google Chrome on Chrome OS versions prior to 61.0.3163.113.

5

What could an attacker achieve with CVE-2017-15405?

An attacker could exploit CVE-2017-15405 to execute arbitrary code with root privileges on the affected systems.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203