# CVE-2004-2146: Other in n/a

> Attackers can perform HTTP response splitting via CRLF injection in the fid parameter of thread-post.asp in MegaBBS.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Jul 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-26ww-4j8h-6752

## What is CVE-2004-2146?

CVE-2004-2146 is a medium-severity vulnerability in n/a, published on 1 Jul 2005. It can be exploited over the network, with no action from the victim.

### Official description

CRLF injection vulnerability in PD9 Software MegaBBS 2 and 2.1 allows attackers to conduct HTTP response splitting attacks via the fid parameter in a writenew action to thread-post.asp.

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

It affects 1 product.


Products: Pd9 Software Megabbs.

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

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

## Is CVE-2004-2146 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-2023](https://insights.sbomify.com/CVE-2008-2023/): SQL injection in n/a (high 7.5)
- [CVE-2004-2653](https://insights.sbomify.com/CVE-2004-2653/): Privilege escalation in n/a (high 7.5)
- [CVE-2004-2145](https://insights.sbomify.com/CVE-2004-2145/): SQL injection in n/a (high 7.5)
- [CVE-2006-0139](https://insights.sbomify.com/CVE-2006-0139/): Missing authorization in n/a (medium 5.0)
- [CVE-2008-2022](https://insights.sbomify.com/CVE-2008-2022/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-2146 is a medium-severity vulnerability in n/a, published on 1 Jul 2005. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2004-2146 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-2146/ (Markdown: https://insights.sbomify.com/CVE-2004-2146/index.md)
```

## Sources

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

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