CVE-2015-2739
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 ArrayBufferBuilder::append function in Mozilla Firefox before 39.0, Firefox ESR 31.x before 31.8 and 38.x before 38.1, and Thunderbird before 38.1 accesses unintended memory locations, which 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 · high confidenceThe ArrayBufferBuilder::append function in Mozilla Firefox and Thunderbird contains a memory corruption vulnerability where it accesses unintended memory locations, which could allow remote attackers to execute arbitrary code or cause other unspecified impacts via crafted web content.
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<= 38.1.0= 31.0= 31.1.0= 31.1.1= 31.3.0= 31.5.1= 31.5.2= 31.5.3= 38.0= 12.04= 14.04= 14.10= 15.04= 7.0= 8.0= 31.1= 31.2= 31.3= 31.4= 31.5= 31.6.0= 31.7.0= 12.0= 12.0= 11= 12.0= 11.3CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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.
-
Identify if Firefox is installedRun 'firefox --version' on Linux/Unix systems, or check Add/Remove Programs on Windows. On RPM-based systems use 'rpm -q firefox', on Debian-based use 'dpkg -l firefox'.Affected if Firefox is present on the system
-
Identify if Thunderbird is installedRun 'thunderbird --version' on Linux/Unix systems. On RPM-based systems use 'rpm -q thunderbird', on Debian-based use 'dpkg -l thunderbird'.Affected if Thunderbird is present on the system
-
Obtain the exact Firefox version numberRun 'firefox --version' to retrieve the precise version string (for example: 38.0, 38.1.0, 31.5.3, 31.7.0)Affected if Version is 38.1.0 or lower, or matches any of these specific versions: 31.0, 31.1.0, 31.1.1, 31.3.0, 31.5.1, 31.5.2, 31.5.3, 38.0
-
Check Firefox ESR version if applicableRun 'firefox --version' and confirm it is an ESR release. ESR versions follow the 31.x pattern and may display 'ESR' in about:supportAffected if Running Firefox ESR version 31.1, 31.2, 31.3, 31.4, 31.5, 31.6.0, or 31.7.0
If Firefox or Thunderbird version is 38.1.0 or lower, or is one of the listed specific 31.x versions (31.0, 31.1.x, 31.3.0, 31.5.x for regular Firefox; 31.1 through 31.7.0 for ESR), the environment is vulnerable to CVE-2015-2739.
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.
dbcve · scopedUpgrade to Firefox 39.0, Firefox ESR 31.8 or 38.1, or Thunderbird 38.1 or later to remediate this vulnerability.
Firefox 39.0 / Firefox ESR 31.8 / Firefox ESR 38.1 / Thunderbird 38.1 (depending on product line)
- 1. Identify the installed Mozilla product (Firefox, Firefox ESR, or Thunderbird) and its current version via Help > About
- 2. For Firefox: upgrade to version 39.0 or later
- 3. For Firefox ESR 31.x: upgrade to version 31.8 or later
- 4. For Firefox ESR 38.x: upgrade to version 38.1 or later
- 5. For Thunderbird: upgrade to version 38.1 or later
- 6. Restart the application after upgrading
- 7. Verify the new version is installed via Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2739 — 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
- www.debian.org
- www.oracle.com
- www.oracle.com
- www.ubuntu.com
- bugzilla.mozilla.org
- lists.opensuse.org
- lists.opensuse.org
- lists.opensuse.org
- rhn.redhat.com
- rhn.redhat.com
- www.debian.org
- www.securityfocus.com
- www.securitytracker.com
- www.securitytracker.com
- www.ubuntu.com
- www.ubuntu.com
- security.gentoo.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-2739 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