CVE-2011-3665
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 · uneditedMozilla Firefox 4.x through 8.0, Thunderbird 5.0 through 8.0, and SeaMonkey before 2.6 allow remote attackers to cause a denial of service (application crash) or possibly have unspecified other impact via an Ogg VIDEO element that is not properly handled after scaling.
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 vulnerability in Mozilla Firefox 4.x-8.0, Thunderbird 5.0-8.0, and SeaMonkey before 2.6 allows remote attackers to cause a denial of service via an Ogg VIDEO element that is not properly handled after scaling, leading to application crash or potentially other unspecified impact.
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= 4.0= 4.0.1= 5.0= 5.0.1= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0<= 2.5= 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= 5.0= 6.0= 6.0.1= 6.0.2= 7.0= 7.0.1= 8.0CVSS 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
- Partial
- Availability
- Partial
AV:N/AC:L/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.
-
Identify the installed Mozilla productOpen the application and navigate to Help > About (Firefox/Thunderbird) or Help > About SeaMonkey to see the product name and versionAffected if The product is Firefox, Thunderbird, or SeaMonkey
-
Determine the exact version numberNote the full version number displayed in the About dialog (for example, 7.0.1, 6.0.2, or 2.5)Affected if The version falls within the affected ranges: Firefox 4.0-8.0, Thunderbird 5.0-8.0, or SeaMonkey 2.5 and earlier
-
Check if Ogg VIDEO support is enabledIn Firefox, type 'about:config' in the address bar, then search for 'media.ogg' related preferences. Look for 'media.video.enabled' or 'media.ogg.enabled' and verify if they are set to trueAffected if Ogg VIDEO support is enabled (the vulnerability requires an Ogg VIDEO element to be processed)
You are affected if you run Firefox 4.0-8.0, Thunderbird 5.0-8.0, or SeaMonkey 2.5 or earlier with Ogg VIDEO support enabled and a scaled Ogg VIDEO element is processed.
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 Firefox 8.0+, Thunderbird 8.0+, or SeaMonkey 2.6+ to obtain the vendor patch for this vulnerability.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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-2011-3665 — 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-2011-3665 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