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

> Remote attackers can obtain sensitive information from Linksys routers due to improper buffer clearing in DHCP BOOTP replies.

- **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:** 23 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-f36j-2388-wq8x

## What is CVE-2004-0580?

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

### Official description

DHCP on Linksys BEFSR11, BEFSR41, BEFSR81, and BEFSRU31 Cable/DSL Routers, firmware version 1.45.7, does not properly clear previously used buffer contents in a BOOTP reply packet, which allows remote attackers to obtain sensitive information.

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

It affects 12 products.


Products: Linksys Befcmu10, Linksys Befn2ps4, Linksys Befsr11, Linksys Befsr41, Linksys Befsr41w, Linksys Befsr81, Linksys Befsru31, Linksys Befsx41, Linksys Befvp41, Linksys Rv082, Linksys Wap55ag, Linksys Wrt54g.

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

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

## Is CVE-2004-0580 being exploited?

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

Public exploit code:

- Linksys - DHCP Information Disclosure (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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