# CVE-2004-0679: Weak cryptography in n/a

> Remote attackers can brute force weak IP cloaking hashes to reveal other users' IP addresses in UnrealIRCd.

- **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:** 13 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wv5x-mhvx-xm35

## What is CVE-2004-0679?

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

### Official description

The IP cloaking feature (cloak.c) in UnrealIRCd 3.2, and possibly other versions, uses a weak hashing scheme to hide IP addresses, which could allow remote attackers to use brute force methods to gain other user's IP addresses.

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

It affects 1 product.


Products: Unreal Unrealircd.

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

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

## Is CVE-2004-0679 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1675](https://insights.sbomify.com/CVE-2002-1675/): Code injection in n/a (medium 6.4)
- [CVE-2006-1214](https://insights.sbomify.com/CVE-2006-1214/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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