dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-3005

HIGH · 9.3 CVSS v2.0 Published 2011-09-29
Fix available
A fix is available. Upgrade to after 6.0.2 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 Mozilla Firefox 4.x through 6, Thunderbird before 7.0, and SeaMonkey before 2.4 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via crafted OGG headers in a .ogg file.

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

A use-after-free vulnerability exists in Mozilla Firefox 4.x-6, Thunderbird before 7.0, and SeaMonkey before 2.4 when parsing crafted OGG media files. The vulnerability occurs in the OGG container header processing where memory is freed but subsequently accessed, leading to potential code execution or denial of service.

MitigationUpgrade affected Mozilla products (Firefox to 7+, Thunderbird to 7.0+, SeaMonkey to 2.4+) to patch the vulnerability. Until patching is feasible, disable OGG media autoplay or avoid opening untrusted .ogg files.

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:= 4.0= 4.0.1= 5.0= 6.0
ThunderbirdApplication
Affected:<= 6.0.2= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.7= 0.7.1= 0.7.2= 0.7.3= 0.8
SeamonkeyApplication
Affected:<= 2.3.3= 1.0= 1.0.1= 1.0.2= 1.0.3= 1.0.4= 1.0.5= 1.0.6= 1.0.7= 1.0.8= 1.0.9= 1.0.99

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 Firefox version
    Open Firefox and navigate to Help > About Firefox, or type 'about:support' in the address bar. Record the version number shown.
    Affected if Version is 4.0, 4.0.1, 5.0, or 6.0 (any 4.x-6.x release).
  2. Identify installed Thunderbird version
    Open Thunderbird and navigate to Help > About Thunderbird. Record the version number shown.
    Affected if Version is 6.0.2 or lower, or one of the early versions listed (0.1 through 0.8).
  3. Identify installed SeaMonkey version
    Open SeaMonkey and navigate to Help > About SeaMonkey. Record the version number shown.
    Affected if Version is 2.3.3 or lower, or one of the 1.0.x versions listed (1.0 through 1.0.99).
  4. Determine if OGG media playback is possible
    Attempt to play an OGG file in the application, or check if media.ogg.enabled preference exists in about:config (for Firefox/Thunderbird) and is not explicitly disabled.
    Affected if OGG media can be played and the version is within the affected range, the vulnerability is present.

A user is affected if they run Firefox 4.x-6.x, Thunderbird 6.0.2 or earlier/0.x-0.8, or SeaMonkey 2.3.3 or earlier/1.0.x, and the application can parse OGG media files.

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 a release after 6.0.2
Interim mitigation

Upgrade affected Mozilla products (Firefox to 7+, Thunderbird to 7.0+, SeaMonkey to 2.4+) to patch the vulnerability. Until patching is feasible, disable OGG media autoplay or avoid opening untrusted .ogg files.

Recommended fix High confidence

Firefox 7.0+, Thunderbird 7.0+, or SeaMonkey 2.4+ (depending on product)

  1. 1. Identify which Mozilla product is affected (Firefox, Thunderbird, or SeaMonkey)
  2. 2. Check the current installed version of the product
  3. 3. For Firefox users: Upgrade to version 7.0 or later
  4. 4. For Thunderbird users: Upgrade to version 7.0 or later
  5. 5. For SeaMonkey users: Upgrade to version 2.4 or later
  6. 6. Verify the upgrade was successful by checking the new version number in the application's About menu
Caveat Standard upgrade risks apply - minor extension compatibility changes may occur between major versions

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

Fix this in Firefox Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2011-3005 — 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-2011-3005 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