dbcve.org
FirefoxWeb browser · Mozilla

CVE-2009-3070

HIGH · 10.0 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
Multiple unspecified vulnerabilities in the browser engine in Mozilla Firefox before 3.0.14 allow remote attackers to cause a denial of service (memory corruption and application crash) or possibly execute arbitrary code via unknown vectors.

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

Multiple critical memory corruption vulnerabilities in the Mozilla Firefox browser engine (versions before 3.0.14) that could allow remote attackers to crash the browser or potentially execute arbitrary code through unknown attack vectors. The vulnerabilities are in unspecified areas of the browser engine's processing of web content.

MitigationUpgrade Mozilla Firefox to version 3.0.14 or later to patch the vulnerabilities. Organizations should also consider implementing application whitelisting and restricting browser permissions to reduce exploit 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
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
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 installed Firefox version
    Open Firefox, click Help > About Firefox, or run 'firefox -version' from command line, or check the application file properties of firefox.exe
    Affected if The version displayed is 3.0.13 or lower, or is one of these early versions: 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
  2. Identify Firefox installation path
    Check common installation directories: C:\Program Files\Mozilla Firefox on Windows, /Applications/Firefox.app on macOS, or /usr/lib/firefox on Linux
    Affected if Firefox is installed and the version cannot be determined or matches the affected versions above
  3. Verify browser is in active use
    Check if Firefox has been launched recently or is set as the default browser by reviewing browser usage logs or checking recently accessed applications
    Affected if Firefox is actively used in the environment, increasing exposure to web-based attack vectors
  4. Confirm engine component presence
    Verify the presence of the Firefox browser engine components (libjs, xul.dll, or similar engine files) in the installation directory
    Affected if The browser engine files exist, meaning the vulnerable code is present on the system

A system is affected if Mozilla Firefox version 3.0.13 or earlier, or any version from 0.1 through 0.9, is installed and the browser is in use, as the memory corruption vulnerabilities reside in the browser engine processing web content.

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 Mozilla Firefox to version 3.0.14 or later to patch the vulnerabilities. Organizations should also consider implementing application whitelisting and restricting browser permissions to reduce exploit impact.

Recommended fix High confidence

Firefox 3.0.14 or later (or migrate to a currently supported Firefox ESR/release version)

  1. 1. Back up your current Firefox profile (bookmarks, passwords, settings) located in your user data directory
  2. 2. Download Firefox 3.0.14 or later from the official Mozilla website (www.mozilla.org)
  3. 3. Close any running Firefox instances
  4. 4. Install the Firefox 3.0.14 (or newer) version over your current installation
  5. 5. Launch the new Firefox version and verify the browser functions correctly
  6. 6. Restore your backed-up profile if needed
Caveat Very old extensions or plugins compatible only with Firefox 0.x-1.x versions may not work; ensure compatibility before production use

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-3070 — 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-2009-3070 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