dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-0074

HIGH · 10.0 CVSS v2.0 Published 2011-05-07
Fix available
A fix is available. Upgrade to after 3.1.9 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
Unspecified vulnerability in the browser engine in Mozilla Firefox 3.5.x before 3.5.19 and 3.6.x before 3.6.17, Thunderbird before 3.1.10, and SeaMonkey before 2.0.14 allows remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors, a different vulnerability than CVE-2011-0072, CVE-2011-0075, CVE-2011-0077, and CVE-2011-0078.

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 · moderate confidence

Memory corruption vulnerability in Mozilla's browser engine affecting Firefox 3.5.x/3.6.x, Thunderbird before 3.1.10, and SeaMonkey before 2.0.14. Allows remote attackers to cause denial of service through memory corruption and potentially execute arbitrary code via unknown vectors.

MitigationUpgrade affected Mozilla products to the patched versions (Firefox 3.5.19/3.6.17, Thunderbird 3.1.10, SeaMonkey 2.0.14 or later). These are legacy versions; consider migrating to supported product versions.

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:= 3.6= 3.6.2= 3.6.3= 3.6.4= 3.6.6= 3.6.7= 3.6.8= 3.6.9= 3.6.10= 3.6.11= 3.6.12= 3.6.13
SeamonkeyApplication
Affected:<= 2.0.13= 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.1
ThunderbirdApplication
Affected:<= 3.1.9= 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

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
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 checks

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

  1. Check Firefox version
    Open Firefox, click Help > About Firefox, or run 'firefox -v' from command line
    Affected if Version is 3.6, 3.6.2, 3.6.3, 3.6.4, 3.6.6, 3.6.7, 3.6.8, 3.6.9, 3.6.10, 3.6.11, 3.6.12, or 3.6.13
  2. Check Thunderbird version
    Open Thunderbird, click Help > About Thunderbird, or run 'thunderbird -v' from command line
    Affected if Version is 3.1.9 or earlier, or falls in the 0.1 through 0.8 range
  3. Check SeaMonkey version
    Open SeaMonkey, click Help > About SeaMonkey, or run 'seamonkey -v' from command line
    Affected if Version is 2.0.13 or earlier, or falls in the 1.0.x or 1.1.x series

Any installed Mozilla Firefox 3.6.x (specific minor versions), Thunderbird 3.1.9 or earlier, or SeaMonkey 2.0.13 or earlier is affected by this memory corruption vulnerability.

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 3.1.9
Interim mitigation

Upgrade affected Mozilla products to the patched versions (Firefox 3.5.19/3.6.17, Thunderbird 3.1.10, SeaMonkey 2.0.14 or later). These are legacy versions; consider migrating to supported product versions.

Recommended fix High confidence

Firefox 3.6.17+, Firefox 3.5.19+, Thunderbird 3.1.10+, Seamonkey 2.0.14+ (or migrate to supported modern versions)

  1. Identify the exact Firefox/Thunderbird/Seamonkey version currently installed
  2. For Firefox 3.6.x users: Upgrade to Firefox 3.6.17 or later (or migrate to a supported Firefox ESR/lts release)
  3. For Firefox 3.5.x users: Upgrade to Firefox 3.5.19 or later
  4. For Thunderbird users: Upgrade to Thunderbird 3.1.10 or later
  5. For Seamonkey users: Upgrade to Seamonkey 2.0.14 or later
  6. Restart the application after upgrading
  7. Verify the installed version matches or exceeds the fixed release
Caveat These are very old legacy versions; upgrading may require migrating to modern browser versions which have different UI/extensions/compatibility considerations

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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