CVE-2015-2729
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 AudioParamTimeline::AudioNodeInputValue function in the Web Audio implementation in Mozilla Firefox before 39.0 and Firefox ESR 38.x before 38.1 does not properly calculate an oscillator rendering range, which allows remote attackers to obtain sensitive information from process memory or cause a denial of service (out-of-bounds read) via unspecified 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 confidenceA flaw in Mozilla Firefox's Web Audio implementation (AudioParamTimeline::AudioNodeInputValue) allows improper calculation of oscillator rendering ranges, leading to out-of-bounds memory reads. This can leak sensitive process memory to remote attackers or cause denial-of-service crashes.
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= 31.0= 31.1.0= 31.1.1= 31.3.0= 31.5.1= 31.5.2= 31.5.3= 38.0<= 38.1.0= 31.1= 31.2= 31.3= 31.4= 31.5= 31.6.0= 31.7.0<= 38.0.1= 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Mozilla Firefox versionOpen Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. The version number is displayed in the window that opens.Affected if Version is 31.0, 31.1.0, 31.1.1, 31.3.0, 31.5.1, 31.5.2, 31.5.3, 38.0, or between 38.0.1 and 38.1.0 inclusive
-
Check Mozilla Firefox ESR versionOpen Firefox ESR, click the menu button, select Help, then About Firefox. The version displayed will indicate ESR (for example, '38.0 ESR').Affected if Version is 31.1, 31.2, 31.3, 31.4, 31.5, 31.6.0, or 31.7.0
-
Check Mozilla Thunderbird versionOpen Thunderbird, click the menu button, select Help, then About Thunderbird. The version number is shown in the dialog.Affected if Version is 38.0.1 or earlier
-
Check Oracle Solaris versionRun the command 'cat /etc/release' or 'uname -a' in a terminal to display the Oracle Solaris version.Affected if Version is exactly 11.3 (Solaris 11.3)
-
Confirm Web Audio usage contextFor desktop browsers, this vulnerability is triggered when processing malicious Web Audio content. If using a vulnerable Firefox/Thunderbird version and browsing untrusted websites, the system is potentially affected.Affected if Vulnerable browser version is in use and the browser processes web content that leverages the Web Audio API
You are affected if you are running Firefox 31.x through 38.1.0, Firefox ESR 31.1 through 31.7.0, Thunderbird 38.0.1 or earlier, or Oracle Solaris 11.3, and the browser processes Web Audio content.
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 Firefox to version 39.0 or later (or ESR 38.1 or later) to patch the vulnerability.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-2729 — 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-2729 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