Debian LinuxOperating system · Debian
CVE-2015-1274
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 · uneditedGoogle Chrome before 44.0.2403.89 does not ensure that the auto-open list omits all dangerous file types, which makes it easier for remote attackers to execute arbitrary code by providing a crafted file and leveraging a user's previous "Always open files of this type" choice, related to download_commands.cc and download_prefs.cc.
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 · high confidenceGoogle Chrome before 44.0.2403.89 failed to properly exclude dangerous file types from the auto-open list. When a user previously chose 'Always open files of this type' for a file extension, Chrome would automatically execute subsequently downloaded files of that type, allowing remote attackers to achieve arbitrary code execution via crafted malicious files.
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
Debian LinuxOperating system
= 8.0
Enterprise Linux Desktop SupplementaryOperating system
= 6.0
Enterprise Linux Server SupplementaryOperating system
= 6.0= 6.7.z
Enterprise Linux Workstation SupplementaryOperating system
= 6.0
ChromeWeb browser
<= 43.0.2357.134= 13.1= 13.2CVSS 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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/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.
-
Check installed Chrome versionRun 'google-chrome --version' or 'google-chrome-stable --version' from the command line, or visit chrome://version in the browserAffected if Version is 43.0.2357.134 or lower (versions prior to 44.0.2403.89)
-
Locate Chrome preferences fileFind the file at ~/.config/google-chrome/Default/Preferences (or ~/.config/chromium/Default/Preferences for Chromium)Affected if The preferences file exists and contains a 'autoopen' key with file extensions listed
-
Inspect auto-open preferencesOpen the Preferences file in a text editor and search for the 'autoopen' or 'autoOpen' key under the 'download' sectionAffected if Any file extension is configured in auto-open preferences - this indicates the user previously selected 'Always open files of this type' for that extension
-
Verify dangerous file type associationCheck if any executable or dangerous file extensions (such as .exe, .js, .jar, .bat, .sh, .cmd, .msi, .scr) appear in the auto-open preferencesAffected if Executable or script file extensions are present in the auto-open list, which would allow automatic execution of maliciously crafted downloads
You are affected if Chrome version is 43.0.2357.134 or lower AND the auto-open preference is set for any file extension, enabling automatic execution of downloaded files of that type.
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 dataUpgrade Google Chrome to version 44.0.2403.89 or later to obtain the corrected download preferences logic that properly excludes dangerous file types from auto-opening.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1274 — 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-2015-1274 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