# CVE-2000-0588: SawMill 5.0.21 CGI program allows remote attackers to read the first line of arbitrary files by listing the file in the rfcf parameter, whos


- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Oct 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cvw6-7vx8-mh9x

## What is CVE-2000-0588?

CVE-2000-0588 is a medium-severity vulnerability in n/a, published on 13 Oct 2000. 

### Official description

SawMill 5.0.21 CGI program allows remote attackers to read the first line of arbitrary files by listing the file in the rfcf parameter, whose contents SawMill attempts to parse as configuration commands.

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

## Which versions are affected by CVE-2000-0588?

It affects 1 product.


Products: Sawmill Sawmill.

## How do I fix CVE-2000-0588?

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

## Is CVE-2000-0588 being exploited?

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

Public exploit code:

- Flowerfire Sawmill 5.0.21 - File Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-5496](https://insights.sbomify.com/CVE-2017-5496/): Information disclosure in n/a (critical 9.8)
- [CVE-2013-4947](https://insights.sbomify.com/CVE-2013-4947/): Other in n/a (high 7.5)
- [CVE-2005-1900](https://insights.sbomify.com/CVE-2005-1900/): Auth bypass in n/a (high 7.5)
- [CVE-2000-0589](https://insights.sbomify.com/CVE-2000-0589/): Weak cryptography in n/a (high 7.5)
- [CVE-2002-0265](https://insights.sbomify.com/CVE-2002-0265/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0588 and fix it if it is affected.

What it is: CVE-2000-0588 is a medium-severity vulnerability in n/a, published on 13 Oct 2000. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0588 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-2000-0588/ (Markdown: https://insights.sbomify.com/CVE-2000-0588/index.md)
```

## Sources

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

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