# CVE-2002-2261: Security feature bypass in n/a

> Remote attackers can bypass Sendmail relay restrictions by spoofing a blank DNS hostname, allowing unauthorized email relaying.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-2261, GHSA-vqjv-jhp4-724w

## What is CVE-2002-2261?

CVE-2002-2261 is a high-severity vulnerability in n/a, published on 18 Oct 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sendmail 8.9.0 through 8.12.6 allows remote attackers to bypass relaying restrictions enforced by the 'check_relay' function by spoofing a blank DNS hostname.

Weakness: CWE-264

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

It affects 1 product.


Products: Sendmail Sendmail.

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

Upgrade to a fixed version.

## Is CVE-2002-2261 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2246](https://insights.sbomify.com/CVE-2007-2246/): Denial of service in n/a (high 7.8)
- [CVE-2006-0058](https://insights.sbomify.com/CVE-2006-0058/): Race condition in n/a (high 7.6)
- [CVE-2009-4565](https://insights.sbomify.com/CVE-2009-4565/): Security feature bypass in n/a (high 7.5)
- [CVE-1999-1592](https://insights.sbomify.com/CVE-1999-1592/): Other in n/a (high 7.5)
- [CVE-2006-7175](https://insights.sbomify.com/CVE-2006-7175/): Weak cryptography in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-2261 is a high-severity vulnerability in n/a, published on 18 Oct 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-2002-2261 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-2261/ (Markdown: https://insights.sbomify.com/CVE-2002-2261/index.md)
```

## Sources

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

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