# CVE-2007-1713: Other in n/a

> Remote attackers can inject arbitrary headers into emails via CRLF sequences in Subject lines using the BASP21 library.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** 27 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-568f-gm48-pf85

## What is CVE-2007-1713?

CVE-2007-1713 is a medium-severity vulnerability in n/a, published on 27 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

CRLF injection vulnerability in BSMTP.DLL in B21Soft BASP21 2003.0211, and BASP21 Pro 1.0.702.27 and earlier, allows remote attackers to inject arbitrary headers into e-mail messages via CRLF sequences in Subject lines.

## Which versions are affected by CVE-2007-1713?

It affects 1 product.


Products: B21soft Basp21.

## How do I fix CVE-2007-1713?

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

## Is CVE-2007-1713 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1713 and fix it if it is affected.

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

## Sources

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

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