dbcve.org
FirefoxWeb browser · Mozilla

CVE-2011-3232

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
YARR, as used in Mozilla Firefox before 7.0, 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 JavaScript.

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

Buffer overflow vulnerability in the YARR (Yet Another Regular Regex) JavaScript regular expression engine used in Firefox, Thunderbird, and SeaMonkey, allowing remote attackers to crash the application or potentially execute arbitrary code via crafted JavaScript.

MitigationUpdate affected software to Firefox 7.0+, Thunderbird 7.0+, or SeaMonkey 2.4+ respectively, or later patched 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.22= 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
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 Mozilla product
    Check for Firefox, Thunderbird, or SeaMonkey installation. On Windows, look in Program Files. On Linux, check /usr/lib or use package manager. On macOS, check /Applications.
    Affected if Any of these three products is installed
  2. Determine Firefox version
    For Firefox: Click Help > About Firefox, or run 'firefox --version' from command line, or check the executable file properties.
    Affected if Firefox version is 3.6 through 3.6.22 inclusive, or any version listed as affected (3.6, 3.6.2-3.6.12, 3.6.22)
  3. Determine Thunderbird version
    For Thunderbird: Click Help > About Thunderbird, or run 'thunderbird --version' from command line, or check the executable file properties.
    Affected if Thunderbird version is 6.0.2 or lower, or any version listed as affected (0.1-0.7.3, 0.8, or 6.0.2)
  4. Determine SeaMonkey version
    For SeaMonkey: Click Help > About SeaMonkey, or run 'seamonkey --version' from command line, or check the executable file properties.
    Affected if SeaMonkey version is 2.3.3 or lower, or any version listed as affected (1.0-1.0.9, 1.0.99, or 2.3.3)
  5. Verify YARR engine presence
    The YARR (Yet Another Regular Regex) engine is a core JavaScript component in these Mozilla products and is always enabled by default for regex processing. No configuration check needed.
    Affected if The YARR engine is present in all affected versions - this is not a configurable feature but a built-in engine component.

A user is affected if they have any Firefox version 3.6.x through 3.6.22, any Thunderbird version 6.0.2 or lower, or any SeaMonkey version 2.3.3 or lower (including all 1.0.x variants listed), as these all contain the vulnerable YARR JavaScript regex engine.

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

Update affected software to Firefox 7.0+, Thunderbird 7.0+, or SeaMonkey 2.4+ respectively, or later patched versions.

Recommended fix High confidence

Firefox 7.0+, Thunderbird 7.0+, SeaMonkey 2.4+

  1. Upgrade Firefox to version 7.0 or later
  2. Upgrade Thunderbird to version 7.0 or later
  3. Upgrade SeaMonkey to version 2.4 or later
Caveat Minor - may require user acceptance of new version defaults, legacy extension compatibility in older applications

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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