dbcve.org
FirefoxWeb browser · Mozilla

CVE-2013-0761

HIGH · 9.3 CVSS v2.0 Published 2013-01-13
Fix available
A fix is available. Upgrade to 2.15 / 10.0.12 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Use-after-free vulnerability in the mozilla::TrackUnionStream::EndTrack implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.1, Thunderbird before 17.0.2, Thunderbird ESR 17.x before 17.0.1, and SeaMonkey before 2.15 allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) 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 confidence

Use-after-free vulnerability in Mozilla's TrackUnionStream::EndTrack media tracking code allows remote attackers to execute arbitrary code or cause heap memory corruption by freeing memory and then accessing it, leading to controlled memory corruption.

MitigationUpdate affected Mozilla products to patched versions: Firefox 18.0+, Firefox ESR 17.0.1+, Thunderbird 17.0.2+, Thunderbird ESR 17.0.1+, or SeaMonkey 2.15+. Alternatively, disable or restrict access to untrusted media content until patching can be completed.

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
FirefoxWeb browser
Affected:< 18.0>= 10.0, < 10.0.12>= 17.0, < 17.0.2
Ubuntu LinuxOperating system
Affected:= 10.04= 11.10= 12.04= 12.10
SeamonkeyApplication
Affected:< 2.15
ThunderbirdApplication
Affected:< 17.0.2
Thunderbird EsrApplication
Affected:>= 10.0, < 10.0.12>= 17.0, < 17.0.2
OpensuseOperating system
Affected:= 11.4= 12.1= 12.2
Linux Enterprise DesktopOperating system
Affected:= 10= 11
Linux Enterprise ServerOperating system
Affected:= 10= 11

CVSS 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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Mozilla product
    Run 'firefox --version' for Firefox, 'thunderbird --version' for Thunderbird, or 'seamonkey --version' for SeaMonkey. On Linux, also check package manager: dpkg -l | grep -E 'firefox|thunderbird|seamonkey' or rpm -qa | grep -E 'firefox|thunderbird|seamonkey'
    Affected if Any Firefox, Thunderbird, or SeaMonkey version is installed
  2. Determine exact product version
    Extract the full version number from the version command output or package listing. For Firefox on Windows, check Help > About Firefox. For Thunderbird, check Help > About Thunderbird.
    Affected if Version cannot be determined or is in an older release format
  3. Compare version against affected ranges
    For Firefox: check if version is < 10.0.12, OR >= 10.0 and < 17.0.2, OR >= 17.0 and < 17.0.2, OR < 18.0. For Thunderbird: check if < 17.0.2. For SeaMonkey: check if < 2.15. For Thunderbird ESR: check if >= 10.0 and < 10.0.12, OR >= 17.0 and < 17.0.2.
    Affected if Installed version falls within any of the vulnerable ranges: Firefox < 10.0.12, 10.0 <= Firefox < 17.0.2, 17.0 <= Firefox < 17.0.2, Firefox < 18.0; Thunderbird < 17.0.2; SeaMonkey < 2.15; Thunderbird ESR 10.0-10.0.11 or 17.0-17.0.1
  4. Verify media playback capability is enabled
    The vulnerability exists in the TrackUnionStream::EndTrack media tracking code. Check if the browser has media playback enabled by testing HTML5 audio/video playback on a test page, or checking about:config for media.autoplay.enabled (Firefox)
    Affected if Media playback features are enabled and the product version is vulnerable

A user is affected if they run any Firefox version before 18.0, Thunderbird before 17.0.2, SeaMonkey before 2.15, or Thunderbird ESR 10.0.x/17.0.x before the patched versions, AND have media playback capabilities enabled in the application.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.15 / 10.0.12 / 17.0.2 or later
Fixed in 2.1510.0.1217.0.2
Interim mitigation

Update affected Mozilla products to patched versions: Firefox 18.0+, Firefox ESR 17.0.1+, Thunderbird 17.0.2+, Thunderbird ESR 17.0.1+, or SeaMonkey 2.15+. Alternatively, disable or restrict access to untrusted media content until patching can be completed.

Recommended fix High confidence

Firefox 18.0+ / Firefox ESR 17.0.1+ / Thunderbird 17.0.2+ / Thunderbird ESR 17.0.1+ / SeaMonkey 2.15+

  1. 1. Identify the installed Mozilla product (Firefox, Thunderbird, SeaMonkey) and current version using 'firefox --version', 'thunderbird --version', or 'seamonkey --version'
  2. 2. If using Firefox: upgrade to Firefox 18.0 or later, or for ESR users upgrade to Firefox ESR 17.0.1 or later
  3. 3. If using Thunderbird: upgrade to Thunderbird 17.0.2 or later, or for ESR users upgrade to Thunderbird ESR 17.0.1 or later
  4. 4. If using SeaMonkey: upgrade to SeaMonkey 2.15 or later
  5. 5. On Linux distributions (Ubuntu, openSUSE, SLED, SLES), use the system package manager to update: 'sudo apt-get update && sudo apt-get upgrade' (Ubuntu) or 'sudo zypper update' (openSUSE/SUSE)
  6. 6. After upgrade, verify the version to confirm the fix is applied
Caveat Minor: Upgrading across major version jumps (e.g., Firefox 10 to 18) may require reconfiguration of some add-ons or extensions that are not compatible with the newer version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-0761 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-0761 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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