# CVE-2004-2061: Server-side request forgery in n/a

> Remote attackers can exploit the show.pl script to read arbitrary local files or use the server as an open proxy via URL manipulation.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jpc9-rmm6-c6xg

## What is CVE-2004-2061?

CVE-2004-2061 is a critical server-side request forgery vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

RiSearch 1.0.01 and RiSearch Pro 3.2.06 allows remote attackers to use the show.pl script as an open proxy, or read arbitrary local files, by setting the url parameter to a (1) http://, (2) ftp://, or (3) file:// URL.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2004-2061?

It affects 2 products.


Products: Risearch Risearch, Risearch Risearch Pro.

## How do I fix CVE-2004-2061?

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

## Is CVE-2004-2061 being exploited?

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

Public exploit code:

- RiSearch 0.99 /RiSearch Pro 3.2.6 - show.pl Open Proxy Relay (exploitdb)
- RiSearch 0.99 /RiSearch Pro 3.2.6 - show.pl Arbitrary File Access (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2061 and fix it if it is affected.

What it is: CVE-2004-2061 is a critical server-side request forgery vulnerability in n/a, published on 10 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-2061 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-2004-2061/ (Markdown: https://insights.sbomify.com/CVE-2004-2061/index.md)
```

## Sources

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

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