# CVE-2006-2159: Other in n/a

> Remote attackers can spoof emails and inject MIME headers via CRLF injection in the email address field of help.php.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 May 2006
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3cg4-vq2p-w876

## What is CVE-2006-2159?

CVE-2006-2159 is a medium-severity vulnerability in n/a, published on 3 May 2006. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CRLF injection vulnerability in help.php in Russcom Network Loginphp allows remote attackers to spoof e-mails and inject MIME headers via CRLF sequences in the email address.

## Which versions are affected by CVE-2006-2159?

It affects 1 product.


Products: Russcom Network Loginphp.

## How do I fix CVE-2006-2159?

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

## Is CVE-2006-2159 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2160](https://insights.sbomify.com/CVE-2006-2160/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-2159 and fix it if it is affected.

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

## Sources

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

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