CVE-2014-1708

NONECVSS 0.0

0.0

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.

CVSS v3: —
EG Score: 0.0(none)
EPSS: 86.6%
KEV: Not listed

Published

March 16, 2014

Last Modified

May 6, 2026

References (4)

chrome-cve-admin@googlehttp://googlechromereleases.blogspot.com/2014/03/stable-channel-update-for-chrome-os_14.html
chrome-cve-admin@googlehttps://code.google.com/p/chromium/issues/detail?id=344051
af854a3a-2127-422b-91ae-364da2661108http://googlechromereleases.blogspot.com/2014/03/stable-channel-update-for-chrome-os_14.html
af854a3a-2127-422b-91ae-364da2661108https://code.google.com/p/chromium/issues/detail?id=344051

Data Freshness Timeline

(refreshed 8× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

2026-06-08 14:14 UTCEPSS rescore
2026-06-07 15:22 UTCEPSS rescore
2026-06-05 22:44 UTCEPSS rescore
2026-06-05 22:44 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-05 06:08 UTCEPSS rescore
2026-06-04 13:09 UTCEPSS rescore
2026-06-04 13:09 UTCEPSS rescore
2026-06-02 20:10 UTCEPSS rescore
2026-06-02 20:10 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 22:28 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-31 00:14 UTCEPSS rescore
2026-05-29 13:41 UTCEPSS rescore
2026-05-29 13:41 UTCEPSS rescore
2026-05-28 19:55 UTCEG score recompute
2026-05-28 19:55 UTCGHSA enrichment
2026-05-28 13:42 UTCEPSS rescore
2026-05-28 13:42 UTCEPSS rescore

Frequently asked(4)

What is CVE-2014-1708?

CVE-2014-1708 is a none vulnerability published on March 16, 2014. 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.

When was CVE-2014-1708 disclosed?

CVE-2014-1708 was first published in the National Vulnerability Database on March 16, 2014, with the most recent update on May 6, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2014-1708 actively exploited?

CVE-2014-1708 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 86.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

How do I remediate CVE-2014-1708?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2014-1708, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2014-1708

Explore →

Is Your Infrastructure Affected by CVE-2014-1708?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2014-1708

📅 Published

🔄 Last Modified

🔗 References (4)