FirefoxWeb browser · Mozilla

CVE-2009-3077

HIGH · 9.3 CVSS v2.0 Published 2009-09-10
Fix available
A fix is available. Upgrade to after 3.0.13 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
Mozilla Firefox before 3.0.14, and 3.5.x before 3.5.3, does not properly manage pointers for the columns (aka TreeColumns) of a XUL tree element, which allows remote attackers to execute arbitrary code via a crafted HTML document, related to a "dangling pointer vulnerability."

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 dangling pointer vulnerability exists in Mozilla Firefox's XUL tree element handling, specifically in the TreeColumns management code. The browser fails to properly maintain pointers when processing XUL tree columns, allowing a remote attacker to exploit the dangling pointer to execute arbitrary code via a crafted HTML document.

MitigationUpgrade Firefox to version 3.0.14 or 3.5.3 or later to patch the dangling pointer vulnerability. Given the CVSS 9.3 severity and remote code execution capability, immediate patching of affected browser installations is critical.

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.0.13= 0.1= 0.2= 0.3= 0.4= 0.5= 0.6= 0.6.1= 0.7= 0.7.1= 0.8= 0.9

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. Verify Firefox is installed
    Check for Firefox executable or check version via command line (firefox --version on Linux/Mac, or check Help > About in the browser)
    Affected if Firefox is installed and matches the version detection below
  2. Determine installed Firefox version
    Run 'firefox --version' or open Firefox, go to Help > About Mozilla Firefox to view the exact version number
    Affected if Version is 3.0.13 or earlier, or one of: 0.1, 0.2, 0.3, 0.4, 0.5, 0.6, 0.6.1, 0.7, 0.7.1, 0.8, or 0.9
  3. Confirm vulnerability trigger condition
    The vulnerability is triggered when Firefox processes a specially crafted HTML document containing malicious XUL tree elements. No specific browser setting needs to be enabled; the flaw exists in the core TreeColumns handling code.
    Affected if The installed Firefox version falls within the affected range AND the browser is used to process untrusted web content

If Firefox version is 3.0.13 or earlier, or any of the specific older versions (0.1-0.9), the browser is vulnerable to remote code execution via the XUL tree dangling pointer flaw when visiting a crafted malicious page.

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.0.13
Interim mitigation

Upgrade Firefox to version 3.0.14 or 3.5.3 or later to patch the dangling pointer vulnerability. Given the CVSS 9.3 severity and remote code execution capability, immediate patching of affected browser installations is critical.

Recommended fix High confidence

Firefox 3.0.14 or Firefox 3.5.3 (or migrate to a currently supported Firefox release)

  1. 1. Backup any important data (bookmarks, passwords, etc.) from the current Firefox profile
  2. 2. Download Firefox 3.0.14 (or Firefox 3.5.3 if currently on the 3.5 branch) from the Mozilla archives, or preferably download a modern supported Firefox version
  3. 3. Close all Firefox instances
  4. 4. Install the downloaded Firefox version
  5. 5. Import or sync bookmarks and settings to the new installation
  6. 6. Verify the browser launches successfully and test functionality
Caveat Firefox 3.0.x and 3.5.x are extremely outdated with many subsequent security fixes and feature changes; legacy extensions and websites may not work properly

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2009-3077 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2009-3077 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