FirefoxWeb browser · Mozilla
CVE-2007-3073
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 · uneditedDirectory traversal vulnerability in Mozilla Firefox 2.0.0.4 and earlier on Mac OS X and Unix allows remote attackers to read arbitrary files via ..%2F (dot dot encoded slash) sequences in a resource:// URI.
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 directory traversal vulnerability in Mozilla Firefox 2.0.0.4 and earlier on Mac OS X and Unix allows remote attackers to read arbitrary files by using ..%2F (dot-dot encoded slash) sequences within resource:// URIs, enabling unauthorized file system access.
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
<= 2.0.0.4CVSS 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
- None
- Availability
- None
AV:N/AC:L/Au:N/C:C/I:N/A:N
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.
-
Confirm Firefox is installedCheck for Firefox installation in typical locations: /Applications/Firefox.app on Mac, or /usr/lib/firefox, /usr/local/firefox on Unix. Also check user's home directory for ~/.firefox or ~/.mozilla/firefox.Affected if Firefox browser is found on the system
-
Identify Firefox versionRun 'firefox -version' from command line, or open Firefox and go to Help > About Firefox. Alternatively, check the version file in the application bundle: /Applications/Firefox.app/Contents/MacOS/firefox-bin --version on Mac, or examine the version in the executable or manifest.Affected if Version is 2.0.0.4 or any earlier 2.x release (e.g., 2.0.0.3, 2.0.0.2, 2.0, etc.)
-
Verify operating systemRun 'uname -a' or check /etc/os-release on Unix, or 'sw_vers' on Mac to confirm the OS type.Affected if System is Mac OS X or any Unix-like OS (Linux, BSD, Solaris). This vulnerability does not affect Windows.
-
Confirm resource:// URI handler is accessibleIn Firefox address bar, type 'resource://' and press Enter. This built-in Firefox protocol handler should display a listing of internal resources.Affected if resource:// URIs are functional (this is the default state in unpatched Firefox, required for the exploit to work)
System is affected if Firefox version 2.0.0.4 or earlier is installed on Mac OS X or Unix, where the resource:// URI handler is accessible and allows the dot-dot encoded slash traversal to reach filesystem paths.
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.
From vendor dataUpgrade to a patched Firefox version beyond 2.0.0.4; the vulnerable versions are extremely outdated (2007) and should be replaced with a current supported browser release.
Fix this in Firefox
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing2.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-3073 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-3073 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