dbcve.org
FirefoxWeb browser · Mozilla

CVE-2007-0009

MEDIUM · 6.8 CVSS v2.0 Published 2007-02-26
Fix available
A fix is available. Upgrade to 1.0.8 / 1.5.0.10 or later.
See remediation →
77/100
Remediation priority · High
High EPSS 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
Stack-based buffer overflow in the SSLv2 support in Mozilla Network Security Services (NSS) before 3.11.5, as used by Firefox before 1.5.0.10 and 2.x before 2.0.0.2, Thunderbird before 1.5.0.10, SeaMonkey before 1.0.8, and certain Sun Java System server products before 20070611, allows remote attackers to execute arbitrary code via invalid "Client Master Key" length values.

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

Stack-based buffer overflow in SSLv2 implementation of Mozilla NSS library allows remote code execution via malformed Client Master Key messages with invalid length values. The vulnerability exists in the SSLv2 handshake processing code.

MitigationUpgrade to NSS 3.11.5+ and corresponding browser/server versions (Firefox 1.5.0.10+/2.0.0.2+, Thunderbird 1.5.0.10+, SeaMonkey 1.0.8+) or disable SSLv2 support in affected applications.

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:>= 1.5, < 1.5.0.10>= 2.0, < 2.0.0.2
Debian LinuxOperating system
Affected:= 3.1= 4.0
Ubuntu LinuxOperating system
Affected:= 5.10= 6.06= 6.10
Network Security ServicesApplication
Affected:< 3.11.5
SeamonkeyApplication
Affected:< 1.0.8
ThunderbirdApplication
Affected:< 1.5.0.10

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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:P/I:P/A:P

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
    Run 'firefox --version' or look in Help > About Firefox. For command-line: 'rpm -q firefox' or 'dpkg -l firefox'
    Affected if Version is 1.5.0.0-1.5.0.9 or 2.0.0.0-2.0.0.1 (before 1.5.0.10 or 2.0.0.2)
  2. Check Thunderbird version
    Run 'thunderbird --version' or look in Help > About Thunderbird. For command-line: 'rpm -q thunderbird' or 'dpkg -l thunderbird'
    Affected if Version is before 1.5.0.10
  3. Check SeaMonkey version
    Run 'seamonkey --version' or look in Help > About SeaMonkey. For command-line: 'rpm -q seamonkey' or 'dpkg -l seamonkey'
    Affected if Version is before 1.0.8
  4. Check NSS library version
    Run 'rpm -q nss' or 'dpkg -l libnss3' or check the NSS version included in the application. Look for libnss3.so version or run 'strings /usr/lib/libnss3.so | grep NSS'
    Affected if NSS version is below 3.11.5 (e.g., 3.11, 3.11.4, etc.)
  5. Check if SSLv2 is enabled in the application or server
    For servers using NSS (like Apache with mod_nss), check the config file for 'SSLv2' or 'NSSProtocol' directives. For browsers, SSLv2 is handled internally by the NSS library - the vulnerability is in the library's SSLv2 handshake code.
    Affected if SSLv2 protocol support is enabled in the application/server configuration, and the NSS library version is vulnerable
  6. Check Debian/Ubuntu system package versions
    Run 'dpkg -l | grep -E "(firefox|thunderbird|seamonkey|nss)" for Debian-based systems to see installed package versions
    Affected if Running Debian 3.1, 4.0, Ubuntu 5.10, 6.06, or 6.10 with vulnerable browser/NSS package versions

You are affected if you have any of the listed browser or NSS versions AND SSLv2 is active/enabled in your environment, since the vulnerability requires both the vulnerable library version and SSLv2 handshake processing to be in use.

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.

From vendor data
Upgrade available Upgrade to 1.0.8 / 1.5.0.10 / 2.0.0.2 or later
Fixed in 1.0.81.5.0.102.0.0.2
Interim mitigation

Upgrade to NSS 3.11.5+ and corresponding browser/server versions (Firefox 1.5.0.10+/2.0.0.2+, Thunderbird 1.5.0.10+, SeaMonkey 1.0.8+) or disable SSLv2 support in affected applications.

Fix this in Firefox Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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