# CVE-2004-0615: Cross-site scripting in n/a

> Remote attackers can inject arbitrary scripts via DHCP hostname requests, potentially compromising router administration interfaces.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wcmh-67fx-99w6

## What is CVE-2004-0615?

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

### Official description

Cross-site scripting (XSS) vulnerability in D-Link DI-614+ SOHO router running firmware 2.30, and DI-704 SOHO router running firmware 2.60B2, and DI-624, allows remote attackers to inject arbitrary script or HTML via the DHCP HOSTNAME option in a DHCP request.

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

It affects 3 products.


Products: D-Link Di-614\+, D-Link Di-704p, Dlink Di-624.

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

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

## Is CVE-2004-0615 being exploited?

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

Public exploit code:

- D-Link AirPlus DI-614+ / DI-624 / DI-704 - DHCP Log HTML Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-1264](https://insights.sbomify.com/CVE-2003-1264/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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