CVE-2009-3077
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 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 confidenceA 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.
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<= 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.9CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Firefox is installedCheck 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
-
Determine installed Firefox versionRun 'firefox --version' or open Firefox, go to Help > About Mozilla Firefox to view the exact version numberAffected 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
-
Confirm vulnerability trigger conditionThe 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.
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 · scopedUpgrade 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.
Firefox 3.0.14 or Firefox 3.5.3 (or migrate to a currently supported Firefox release)
- 1. Backup any important data (bookmarks, passwords, etc.) from the current Firefox profile
- 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. Close all Firefox instances
- 4. Install the downloaded Firefox version
- 5. Import or sync bookmarks and settings to the new installation
- 6. Verify the browser launches successfully and test functionality
Generated from the published advisory — verify against the referenced sources before acting.
- 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-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- www.mozilla.org
- lists.opensuse.org
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- secunia.com
- www.debian.org
- www.novell.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.redhat.com
- www.securityfocus.com
- www.ubuntu.com
- www.vupen.com
- bugzilla.mozilla.org
- oval.cisecurity.org
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2009-3077 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