First published: Thu Jul 23 2015(Updated: )
Google 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.
Credit: cve-coordination@google.com
Affected Software | Affected Version | How to fix |
---|---|---|
Debian GNU/Linux | =8.0 | |
openSUSE | =13.1 | |
openSUSE | =13.2 | |
redhat enterprise linux desktop supplementary | =6.0 | |
Red Hat Enterprise Linux Server Supplementary | =6.0 | |
Red Hat Enterprise Linux Server Supplementary | =6.7.z | |
Red Hat Enterprise Linux Workstation Supplementary | =6.0 | |
Google Chrome | <=43.0.2357.134 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2015-1274 has a high severity rating due to its potential to allow remote code execution.
To fix CVE-2015-1274, update Google Chrome to version 44.0.2403.89 or later.
CVE-2015-1274 affects all versions of Google Chrome prior to 44.0.2403.89.
Yes, CVE-2015-1274 can significantly impact system security by allowing malicious files to be executed.
Yes, distributions such as Debian, openSUSE, and Red Hat that run affected versions of Google Chrome are vulnerable to CVE-2015-1274.