# CVE-2001-0184: Denial of service in n/a

> Remote attackers can crash the Iris network analysis tool by sending a malformed packet that a user views, causing a denial of service.

- **Severity:** Low 2.6 (`AV:N/AC:H/Au:N/C:N/I:N/A:P`)
- **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:** 9 Mar 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-mfp2-hxqg-8hp9

## What is CVE-2001-0184?

CVE-2001-0184 is a low-severity denial of service vulnerability in n/a, published on 9 Mar 2001. 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

eEye Iris 1.01 beta allows remote attackers to cause a denial of service via a malformed packet, which causes Iris to crash when a user views the packet.

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

It affects 1 product.


Products: Eeye Digital Security Iris.

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

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

## Is CVE-2001-0184 being exploited?

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

Public exploit code:

- eEye Digital Security IRIS 1.0.1 - GET Denial of Service (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0734](https://insights.sbomify.com/CVE-2000-0734/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2001-0184 is a low-severity denial of service vulnerability in n/a, published on 9 Mar 2001. 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-2001-0184 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-2001-0184/ (Markdown: https://insights.sbomify.com/CVE-2001-0184/index.md)
```

## Sources

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

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