# CVE-2004-2095: Information disclosure in n/a

> Remote attackers can identify simulated IP addresses by sending specific TCP packets, compromising the honeypot's stealth.

- **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:** 27 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-q386-47j2-f4xv

## What is CVE-2004-2095?

CVE-2004-2095 is a medium-severity vulnerability in n/a, published on 27 May 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Honeyd before 0.8 replies to TCP packets with the SYN and RST flags set, which allows remote attackers to identify IP addresses that are being simulated by Honeyd.

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

It affects 1 product.


Products: Niels Provos Honeyd.

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

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

## Is CVE-2004-2095 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-4292](https://insights.sbomify.com/CVE-2006-4292/): Denial of service in n/a (medium 5.0)
- [CVE-2006-0752](https://insights.sbomify.com/CVE-2006-0752/): Niels Provos Honeyd before 1.5 replies to certain illegal IP packet fragments that other IP stack implementations would drop, which allows r (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2095 is a medium-severity vulnerability in n/a, published on 27 May 2005. 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-2004-2095 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-2004-2095/ (Markdown: https://insights.sbomify.com/CVE-2004-2095/index.md)
```

## Sources

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

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