CVE-2014-1708: Critical severity Google Chrome OS vulnerability
Published Mar 16, 2014
·Updated
The boot implementation in Google Chrome OS before 33.0.1750.152 does not properly consider file persistence, which allows remote attackers to execute arbitrary code via unspecified vectors.
Affected Software
11 affected components
Google Chrome OS<=33.0.1750.149
Google Chrome OS=33.0.1750.2
Google Chrome OS=33.0.1750.5
Google Chrome OS=33.0.1750.16
Google Chrome OS=33.0.1750.29
Google Chrome OS=33.0.1750.51
Google Chrome OS=33.0.1750.58
Google Chrome OS=33.0.1750.70
Google Chrome OS=33.0.1750.93
Google Chrome OS=33.0.1750.112
Google Chrome OS=33.0.1750.124
Event History
Mar 16, 2014
CVE Published
via MITRE·10:00 AM
Data Sourced
via MITRE·10:00 AM
Description
Data Sourced
via NVD·02:06 PM
DescriptionSeverityAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2014-1708?
CVE-2014-1708 is classified as a high severity vulnerability due to its potential to allow remote code execution.
2
How do I fix CVE-2014-1708?
To fix CVE-2014-1708, update Google Chrome OS to version 33.0.1750.152 or later.
3
What systems are affected by CVE-2014-1708?
CVE-2014-1708 affects Google Chrome OS versions prior to 33.0.1750.152.
4
What type of vulnerability is CVE-2014-1708?
CVE-2014-1708 is a remote code execution vulnerability that arises from improper file persistence handling.
5
How can attackers exploit CVE-2014-1708?
Attackers can exploit CVE-2014-1708 through unspecified vectors that take advantage of the boot implementation flaw.