# CVE-2005-0493: Other in n/a

> Remote attackers can bypass email validation and send spam via CRLF injection in the email parameter of Biz Mail Form.

- **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:** 21 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-ccmr-7hqh-p3p5

## What is CVE-2005-0493?

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

### Official description

CRLF injection vulnerability in bizmail.cgi in Biz Mail Form before 2.2 allows remote attackers to bypass the email check and send spam e-mail via CRLF sequences and forged mail headers in the email parameter.

## Which versions are affected by CVE-2005-0493?

It affects 1 product.


Products: Seth M. Knorr Biz Mail Form.

## How do I fix CVE-2005-0493?

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

## Is CVE-2005-0493 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0493 and fix it if it is affected.

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

## Sources

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

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