# CVE-2002-0107: Information disclosure in n/a

> Remote attackers can obtain sensitive information via malformed GET requests in the CacheFlow CacheOS web administration interface.

- **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:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vhpw-4qvj-p38w

## What is CVE-2002-0107?

CVE-2002-0107 is a medium-severity vulnerability in n/a, published on 25 Jun 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Web administration interface in CacheFlow CacheOS 4.0.13 and earlier allows remote attackers to obtain sensitive information via a series of GET requests that do not end in with HTTP/1.0 or another version string, which causes the information to be leaked in the error message.

## Which versions are affected by CVE-2002-0107?

It affects 1 product.


Products: Cacheflow Cacheos.

## How do I fix CVE-2002-0107?

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

## Is CVE-2002-0107 being exploited?

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

Public exploit code:

- Cacheflow CacheOS 3.1/4.0 Web Administration - Arbitrary Cached Page Code Leakage (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0107 and fix it if it is affected.

What it is: CVE-2002-0107 is a medium-severity vulnerability in n/a, published on 25 Jun 2002. 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-2002-0107 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-2002-0107/ (Markdown: https://insights.sbomify.com/CVE-2002-0107/index.md)
```

## Sources

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

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