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

> Remote attackers can inject arbitrary web script or HTML via User Agent or Referrer headers in DasBlog's Activity and Events Viewer.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/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:** 20 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j37c-fr9j-g7mj

## What is CVE-2004-1657?

CVE-2004-1657 is a medium-severity cross-site scripting vulnerability in n/a, published on 20 Feb 2005. 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 the Activity and Events Viewer for Newtelligence DasBlog allows remote attackers to inject arbitrary web script or HTML via the (1) User Agent or (2) Referrer HTTP headers.

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

It affects 1 product.


Products: Newtelligence Dasblog.

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

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

## Is CVE-2004-1657 being exploited?

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

Public exploit code:

- Newtelligence DasBlog 1.x - Request Log HTML Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-7292](https://insights.sbomify.com/CVE-2014-7292/): Open redirect in n/a (medium 5.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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