# CVE-2007-5337: Information disclosure in n/a

> Remote attackers can read arbitrary files on SSH/sftp servers via crafted web pages in Firefox on Linux with gnome-vfs support.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 21 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-gq79-35xw-52pq

## What is CVE-2007-5337?

CVE-2007-5337 is a medium-severity vulnerability in Mozilla Firefox, published on 21 Oct 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Mozilla Firefox before 2.0.0.8 and SeaMonkey before 1.1.5, when running on Linux systems with gnome-vfs support, might allow remote attackers to read arbitrary files on SSH/sftp servers that accept key authentication by creating a web page on the target server, in which the web page contains URIs with (1) smb: or (2) sftp: schemes that access other files from the server.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2007-5337?

It affects 3 products.


Products: Gnome Gnome-Vfs, Mozilla Firefox, Mozilla Seamonkey.

## How do I fix CVE-2007-5337?

Upgrade to a fixed version.

## Is CVE-2007-5337 being exploited?

There is no known exploitation of CVE-2007-5337 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5337 and fix it if it is affected.

What it is: CVE-2007-5337 is a medium-severity vulnerability in Mozilla Firefox, published on 21 Oct 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-5337 in the wild and no public exploit code.

Affected product: Mozilla Firefox. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2007-5337/ (Markdown: https://insights.sbomify.com/CVE-2007-5337/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2007-5337
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2007-5337
- OSV: https://osv.dev/vulnerability/CVE-2007-5337

---
From sbomify Insights: https://insights.sbomify.com/CVE-2007-5337/
Summaries are generated and may contain mistakes; the official description above is the record.