CVE-2015-0807
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 · uneditedThe navigator.sendBeacon implementation in Mozilla Firefox before 37.0, Firefox ESR 31.x before 31.6, and Thunderbird before 31.6 processes HTTP 30x status codes for redirects after a preflight request has occurred, which allows remote attackers to bypass intended CORS access-control checks and conduct cross-site request forgery (CSRF) attacks via a crafted web site, a similar issue to CVE-2014-8638.
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 confidenceThe navigator.sendBeacon() API in Firefox before 37.0 and Thunderbird before 31.6 improperly processes HTTP 30x redirects that occur after a CORS preflight request, allowing attackers to bypass cross-origin access controls and conduct CSRF attacks against web applications using this API.
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<= 36.0.4= 31.0= 31.1.0= 31.1.1= 31.3.0= 31.5.1= 31.5.2= 31.5.3= 31.1= 31.2= 31.3= 31.4= 31.5<= 31.5CVSS 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 Firefox versionOpen Firefox, click the menu button, select Help, then About Firefox. Note the version number displayed.Affected if The installed version is 36.0.4 or earlier, or exactly 31.0, 31.1.0, 31.1.1, 31.3.0, 31.5.1, 31.5.2, or 31.5.3
-
Check Firefox ESR versionOpen Firefox ESR, click the menu button, select Help, then About Firefox. Note the version number displayed.Affected if The installed version is exactly 31.1, 31.2, 31.3, 31.4, or 31.5
-
Check Thunderbird versionOpen Thunderbird, click the menu button, select Help, then About Thunderbird. Note the version number displayed.Affected if The installed version is 31.5 or earlier
If the installed Firefox version is 36.0.4 or below or any of the specific 31.x versions listed, or Firefox ESR is 31.1 through 31.5, or Thunderbird is 31.5 or below, the browser is vulnerable to CORS bypass via sendBeacon redirects.
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 dataUpdate affected Mozilla products to patched versions (Firefox 37.0+, Firefox ESR 31.6+, Thunderbird 31.6+) to remediate this vulnerability.
- Consultation1.0 h
- Testing2.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-2015-0807 — 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 sources- www.mozilla.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- rhn.redhat.com
- www.debian.org
- www.debian.org
- www.oracle.com
- www.securityfocus.com
- www.securitytracker.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- bugzilla.mozilla.org
- security.gentoo.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-0807 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