What is the severity of CVE-2014-1706?

CVE-2014-1706 is categorized as a high severity vulnerability due to its potential to allow command injection.

How do I fix CVE-2014-1706?

To fix CVE-2014-1706, users should update their Google Chrome OS to the latest version beyond 33.0.1750.152.

What systems are affected by CVE-2014-1706?

CVE-2014-1706 affects Google Chrome OS versions prior to 33.0.1750.152.

Can CVE-2014-1706 lead to remote code execution?

Yes, CVE-2014-1706 can potentially allow remote attackers to execute arbitrary commands.

Is there a workaround for CVE-2014-1706?

There are no recommended workarounds for CVE-2014-1706; updating the software is the best mitigation.

Vulnerability/
CVE-2014-1706

high

7.5

16/3/2014

6/8/2024

CVE-2014-1706

First published: Sun Mar 16 2014(Updated: )

crosh in Google Chrome OS before 33.0.1750.152 allows attackers to inject commands via unspecified vectors.

Credit: cve-coordination@google.com

Affected Software	Affected Version	How to fix
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

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2014-1706?
CVE-2014-1706 is categorized as a high severity vulnerability due to its potential to allow command injection.
How do I fix CVE-2014-1706?
To fix CVE-2014-1706, users should update their Google Chrome OS to the latest version beyond 33.0.1750.152.
What systems are affected by CVE-2014-1706?
CVE-2014-1706 affects Google Chrome OS versions prior to 33.0.1750.152.
Can CVE-2014-1706 lead to remote code execution?
Yes, CVE-2014-1706 can potentially allow remote attackers to execute arbitrary commands.
Is there a workaround for CVE-2014-1706?
There are no recommended workarounds for CVE-2014-1706; updating the software is the best mitigation.

collector/nvd-index
agent/references
agent/type
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/severity
agent/last-modified-date
agent/author
agent/tags
agent/description
agent/first-publish-date
agent/event
agent/source
vendor/google
canonical/google chrome os
version/google chrome os/33.0.1750.149
version/google chrome os/33.0.1750.2
version/google chrome os/33.0.1750.5
version/google chrome os/33.0.1750.16
version/google chrome os/33.0.1750.29
version/google chrome os/33.0.1750.51
version/google chrome os/33.0.1750.58
version/google chrome os/33.0.1750.70
version/google chrome os/33.0.1750.93
version/google chrome os/33.0.1750.112
version/google chrome os/33.0.1750.124

Company

Resources

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.

Frequently Asked Questions

What is the severity of CVE-2014-1706?
CVE-2014-1706 is categorized as a high severity vulnerability due to its potential to allow command injection.
How do I fix CVE-2014-1706?
To fix CVE-2014-1706, users should update their Google Chrome OS to the latest version beyond 33.0.1750.152.
What systems are affected by CVE-2014-1706?
CVE-2014-1706 affects Google Chrome OS versions prior to 33.0.1750.152.
Can CVE-2014-1706 lead to remote code execution?
Yes, CVE-2014-1706 can potentially allow remote attackers to execute arbitrary commands.
Is there a workaround for CVE-2014-1706?
There are no recommended workarounds for CVE-2014-1706; updating the software is the best mitigation.