dbcve.org
FirefoxWeb browser · Mozilla

CVE-2007-1562

MEDIUM · 6.8 CVSS v2.0 Published 2007-03-21
Fix available
A fix is available. Upgrade to 1.5.0.11 / 2.0.0.3 or later.
See remediation →
77/100
Remediation priority · High
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
The FTP protocol implementation in Mozilla Firefox before 1.5.0.11 and 2.x before 2.0.0.3 allows remote attackers to force the client to connect to other servers, perform a proxied port scan, or obtain sensitive information by specifying an alternate server address in an FTP PASV response.

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

The FTP protocol implementation in Mozilla Firefox before 1.5.0.11 and 2.x before 2.0.0.3 fails to properly validate server responses during the FTP PASV command sequence. When an FTP server responds to a PASV request with an alternate IP address (for data transfer), Firefox blindly connects to that specified address without verifying it matches the original server. A malicious FTP server can exploit this to force the browser to connect to arbitrary servers, enabling port scanning of internal networks or redirecting clients to malicious hosts for further attacks.

MitigationUpgrade Firefox to version 1.5.0.11 or 2.0.0.3 or later, which contains the fix for proper validation of FTP PASV response addresses. Users of older Firefox versions should avoid connecting to untrusted FTP servers until patched.

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.11>= 2.0, < 2.0.0.3
Ubuntu LinuxOperating system
Affected:= 5.10= 6.06= 6.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. Determine installed Firefox version
    In Firefox, go to Help > About Firefox. On Linux, run 'firefox --version' or check the package with 'dpkg -l firefox' or 'rpm -q firefox'.
    Affected if Version is 1.5.0.x where x < 11, or 2.0.0.x where x < 3 (including 2.0, 2.0.0.1, 2.0.0.2)
  2. Confirm FTP protocol is accessible
    In the Firefox address bar, try entering 'ftp://example.com' to verify the browser handles FTP URLs. Check if the 'network.protocol-handler.expose.ftp' preference is true in about:config.
    Affected if FTP URLs load or the protocol handler preference is enabled, meaning Firefox will process FTP connections
  3. Check for active FTP session usage
    Review browser activity or network logs while attempting to browse an FTP site. On Linux, also verify the installed firefox package version matches the affected range using the system package manager.
    Affected if FTP connections can be initiated and the installed Firefox package version falls within the vulnerable range

A user is affected if their Firefox version is 1.5.0 through 1.5.0.10 or 2.0.0 through 2.0.0.2 and they use the browser to connect to FTP servers.

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.5.0.11 / 2.0.0.3 or later
Fixed in 1.5.0.112.0.0.3
Interim mitigation

Upgrade Firefox to version 1.5.0.11 or 2.0.0.3 or later, which contains the fix for proper validation of FTP PASV response addresses. Users of older Firefox versions should avoid connecting to untrusted FTP servers until patched.

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,460
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,536.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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