CVE-2015-1248
published 2015-04-19CVE-2015-1248: The FileSystem API in Google Chrome before 40.0.2214.91 allows remote attackers to bypass the SafeBrowsing for Executable Files protection mechanism by…
PriorityP422medium4.3CVSS 2.0
AVNACMAuNCNIPAN
EPSS
1.54%
72.4th percentile
The FileSystem API in Google Chrome before 40.0.2214.91 allows remote attackers to bypass the SafeBrowsing for Executable Files protection mechanism by creating a .exe file in a temporary filesystem and then referencing this file with a filesystem:http: URL.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| chrome | <= 40.0.2214.85 | — |
CVSS provenance
nvdv2.04.3MEDIUMAV:N/AC:M/Au:N/C:N/I:P/A:N
osv4.3MEDIUM
vendor_redhat4.3MEDIUM
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-prgf-rqp7-pmqx: The FileSystem API in Google Chrome before 40
ghsa_unreviewed·2022-05-17
CVE-2015-1248 [MEDIUM] GHSA-prgf-rqp7-pmqx: The FileSystem API in Google Chrome before 40
The FileSystem API in Google Chrome before 40.0.2214.91 allows remote attackers to bypass the SafeBrowsing for Executable Files protection mechanism by creating a .exe file in a temporary filesystem and then referencing this file with a filesystem:http: URL.
OSV
CVE-2015-1248: The FileSystem API in Google Chrome before 40
osv·2015-04-19·CVSS 4.3
CVE-2015-1248 [MEDIUM] CVE-2015-1248: The FileSystem API in Google Chrome before 40
The FileSystem API in Google Chrome before 40.0.2214.91 allows remote attackers to bypass the SafeBrowsing for Executable Files protection mechanism by creating a .exe file in a temporary filesystem and then referencing this file with a filesystem:http: URL.
Red Hat
chromium-browser: SafeBrowsing bypass
vendor_redhat·2015-04-14·CVSS 4.3
CVE-2015-1248 [MEDIUM] CWE-352 chromium-browser: SafeBrowsing bypass
chromium-browser: SafeBrowsing bypass
The FileSystem API in Google Chrome before 40.0.2214.91 allows remote attackers to bypass the SafeBrowsing for Executable Files protection mechanism by creating a .exe file in a temporary filesystem and then referencing this file with a filesystem:http: URL.
No detection rules found.
No public exploits indexed.
http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.htmlhttp://lists.opensuse.org/opensuse-updates/2015-04/msg00040.htmlhttp://lists.opensuse.org/opensuse-updates/2015-11/msg00024.htmlhttp://rhn.redhat.com/errata/RHSA-2015-0816.htmlhttp://www.debian.org/security/2015/dsa-3238http://www.securitytracker.com/id/1032209https://code.google.com/p/chromium/issues/detail?id=380663https://security.gentoo.org/glsa/201506-04http://googlechromereleases.blogspot.com/2015/04/stable-channel-update_14.htmlhttp://lists.opensuse.org/opensuse-updates/2015-04/msg00040.htmlhttp://lists.opensuse.org/opensuse-updates/2015-11/msg00024.htmlhttp://rhn.redhat.com/errata/RHSA-2015-0816.htmlhttp://www.debian.org/security/2015/dsa-3238http://www.securitytracker.com/id/1032209https://code.google.com/p/chromium/issues/detail?id=380663https://security.gentoo.org/glsa/201506-04
2015-04-19
Published