CVE-2007-3072 json
Directory traversal vulnerability in Mozilla Firefox before 2.0.0.4 on Windows allows remote attackers to read arbitrary files via ..%5C (dot dot encoded backslash) sequences in a resource:// URI.
published 19y ago modified 5mo ago also EUVD-2007-3064
- cvss
- 7.1
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.6%
- EPSS 1.6% chance of exploitation in 30 days, percentile 75%
- public exploits
- 0
- none known
Summary
Directory traversal vulnerability in Mozilla Firefox before 2.0.0.4 on Windows allows remote attackers to read arbitrary files via ..%5C (dot dot encoded backslash) sequences in a resource:// URI.
Is CVE-2007-3072 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.58% chance of exploitation in the next 30 days, higher than 75% of all scored CVEs (FIRST EPSS, 2026-11-18).
Exploits and checks
- larholm.com http://larholm.com/2007/05/25/firefox-0day-local-file-reading/ referenced PoC, tagged "exploit" by a source, unverified
- ha.ckers.org http://ha.ckers.org/blog/20070516/read-firefox-settings-poc/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.1 | AV:N/AC:M/Au:N/C:C/I:N/A:N |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
- Technology feeds
References
-
larholm.com
/2007/05/25/firefox-0day-local-file-reading/
exploit
-
ha.ckers.org
/blog/20070516/read-firefox-settings-poc/
exploit
-
secunia.com
/advisories/25481
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/470500/100/0/threaded
mailing-list
-
osvdb.org
/35922
vdb-entry
- larholm.com /2007/06/04/unpatched-input-validation-flaw-in-firefox-2004/
- ha.ckers.org /blog/20070516/read-firefox-settings-poc/#comment-35888
- bugzilla.mozilla.org /show_bug.cgi?id=367428
Sources
- CVE List CVE-2007-3072
- NVD CVE-2007-3072
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.