ChromeWeb browser · Google
CVE-2014-1715
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedDirectory traversal vulnerability in Google Chrome before 33.0.1750.152 on OS X and Linux and before 33.0.1750.154 on Windows has unspecified impact and attack vectors.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceA directory traversal vulnerability exists in Google Chrome versions prior to 33.0.1750.152 (Mac/Linux) and 33.0.1750.154 (Windows). This flaw allows attackers to access files and directories outside the intended web root or restricted paths, potentially enabling unauthorized file读取 or system compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
< 33.0.1750.152< 33.0.1750.154CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Determine the installed Google Chrome versionOpen Chrome and navigate to chrome://version, or run 'google-chrome --version' (Linux), 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' (Windows), or 'open -a Google\ Chrome --version' (Mac)Affected if The displayed version number is lower than 33.0.1750.152 (Mac/Linux) or 33.0.1750.154 (Windows)
-
Identify the host operating systemCheck whether the system is running Mac OS X, Linux, or Windows. On Windows, run 'systeminfo | findstr /B /C:OSName'. On Mac, run 'sw_vers'. On Linux, check /etc/os-release or run 'uname -a'Affected if The OS is Chrome-running Mac, Linux, or Windows - each has its own version threshold for this vulnerability
-
Compare the installed version against the vulnerable rangeParse the version number from step 1. For Mac and Linux, compare the full version string numerically against 33.0.1750.152. For Windows, compare against 33.0.1750.154Affected if The installed version is 33.0.1750.151 or lower (Mac/Linux) or 33.0.1750.153 or lower (Windows)
-
Audit Chrome-based browsers for inherited versionsIdentify any Chromium-based browsers installed (such as Opera, Brave, Edge Chromium) and check their version numbers, as they may share the underlying Chrome engineAffected if Any installed Chromium-based browser shares the same vulnerable version base and falls below the respective threshold
A user is affected if their installed Google Chrome version (or a Chromium-based browser inheriting that engine) is below 33.0.1750.152 on Mac/Linux or below 33.0.1750.154 on Windows.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data33.0.1750.15233.0.1750.154
Update Google Chrome to version 33.0.1750.152 or later (Mac/Linux) or 33.0.1750.154 or later (Windows). For enterprise environments, deploy the update via centralized patch management.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1715 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-1715 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data