# CVE-2002-1575: Other in n/a

> Remote attackers can use CRLF injection in CGI email parameters to manipulate email headers and use the server as a spam proxy.

- **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:** Yes
- **Published:** 11 Feb 2004
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-437, GHSA-98v6-784f-9j89

## What is CVE-2002-1575?

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

### Official description

cgiemail allows remote attackers to use cgiemail as a spam proxy via CRLF injection of encoded newline (%0a) characters in parameters such as "required-subject," which can be used to modify the CC, BCC, and other header fields in the generated email message.

## Which versions are affected by CVE-2002-1575?

It affects 1 product.


Products: Mit Cgiemail.

## How do I fix CVE-2002-1575?

Apply the vendor's patch.

## Is CVE-2002-1575 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-1652](https://insights.sbomify.com/CVE-2002-1652/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-1575 and fix it if it is affected.

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

## Sources

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

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