# CVE-2005-2455: Information disclosure in n/a

> Remote web servers can read arbitrary local files and list installed scripts via Greasemonkey API functions, exposing sensitive user data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/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:** No
- **Published:** 4 Aug 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3gfm-pp5h-g7cc

## What is CVE-2005-2455?

CVE-2005-2455 is a medium-severity vulnerability in n/a, published on 4 Aug 2005. 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

Greasemonkey before 0.3.5 allows remote web servers to (1) read arbitrary files via a GET request to a file:// URL in the GM_xmlhttpRequest API function, (2) list installed scripts using GM_scripts, or obtain sensitive information via (3) GM_setValue and GM_getValue.

## Which versions are affected by CVE-2005-2455?

It affects 1 product.


Products: Greasemonkey Greasemonkey.

## How do I fix CVE-2005-2455?

No fix has been published for CVE-2005-2455 yet. Limit exposure of the affected software until one is available.

## Is CVE-2005-2455 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2455 exists.

Public exploit code:

- Greasemonkey 0.3.3 - Multiple Remote Information Disclosure Vulnerabilities (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2455 and fix it if it is affected.

What it is: CVE-2005-2455 is a medium-severity vulnerability in n/a, published on 4 Aug 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2455 exists.

Affected product: n/a. 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-2005-2455/ (Markdown: https://insights.sbomify.com/CVE-2005-2455/index.md)
```

## Sources

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

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