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

> Remote attackers can spoof email messages by exploiting Sendmail's failure to reject localhost.localdomain from external hosts.

- **Severity:** Medium 4.3 (`AV:N/AC:M/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:** 27 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-r38f-v7c5-grvh, RHSA-2007:0252

## What is CVE-2006-7176?

CVE-2006-7176 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

The version of Sendmail 8.13.1-2 on Red Hat Enterprise Linux 4 Update 4 and earlier does not reject the "localhost.localdomain" domain name for e-mail messages that come from external hosts, which might allow remote attackers to spoof messages.

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sendmail` | Red Hat:enterprise_linux:4::as | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-cf` | Red Hat:enterprise_linux:4::as | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-doc` | Red Hat:enterprise_linux:4::as | All versions | 0:8.13.1-3.2.el4 |
| `sendmail` | Red Hat:enterprise_linux:4::desktop | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-cf` | Red Hat:enterprise_linux:4::desktop | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-doc` | Red Hat:enterprise_linux:4::desktop | All versions | 0:8.13.1-3.2.el4 |
| `sendmail` | Red Hat:enterprise_linux:4::es | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-cf` | Red Hat:enterprise_linux:4::es | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-doc` | Red Hat:enterprise_linux:4::es | All versions | 0:8.13.1-3.2.el4 |
| `sendmail` | Red Hat:enterprise_linux:4::ws | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-cf` | Red Hat:enterprise_linux:4::ws | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:8.13.1-3.2.el4 |
| `sendmail-doc` | Red Hat:enterprise_linux:4::ws | All versions | 0:8.13.1-3.2.el4 |

Products: Sendmail Sendmail.

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

Apply the vendor's patch.

## Is CVE-2006-7176 being exploited?

There is no known exploitation of CVE-2006-7176 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-2002-2261](https://insights.sbomify.com/CVE-2002-2261/): 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2006-7176 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-2006-7176 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-7176/ (Markdown: https://insights.sbomify.com/CVE-2006-7176/index.md)
```

## Sources

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

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