# CVE-2001-0870: Missing authorization in n/a

> Remote attackers can access sensitive network monitoring logs without authentication due to default server configuration in Alchemy Eye devices.

- **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:** 30 Nov 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-5wfq-334q-jxm8

## What is CVE-2001-0870?

CVE-2001-0870 is a medium-severity missing authorization vulnerability in n/a, published on 30 Nov 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

HTTP server in Alchemy Eye and Alchemy Network Monitor 1.9x through 2.6.18 is enabled without authentication by default, which allows remote attackers to obtain network monitoring logs with potentially sensitive information by directly requesting the eye.ini file.

## Which versions are affected by CVE-2001-0870?

It affects 2 products.


Products: Alchemy Lab Alchemy Eye, Dek Software Alchemy Network Monitor.

## How do I fix CVE-2001-0870?

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

## Is CVE-2001-0870 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0871](https://insights.sbomify.com/CVE-2001-0871/): Path traversal in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-0870 and fix it if it is affected.

What it is: CVE-2001-0870 is a medium-severity missing authorization vulnerability in n/a, published on 30 Nov 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-0870 in the wild and no public exploit code.

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-2001-0870/ (Markdown: https://insights.sbomify.com/CVE-2001-0870/index.md)
```

## Sources

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

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