# CVE-2011-1429: Security feature bypass in n/a

> Mutt fails to verify SMTPS server hostnames against X.509 certificates, allowing man-in-the-middle attackers to intercept email traffic.

- **Severity:** Medium 5.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Mar 2011
- **Updated:** 6 Aug 2024
- **Also known as:** AZL-36964, AZL-7291, DEBIAN-CVE-2011-1429, GHSA-h64v-56v4-2q6j, RHSA-2011:0959

## What is CVE-2011-1429?

CVE-2011-1429 is a medium-severity vulnerability in n/a, published on 16 Mar 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Mutt does not verify that the smtps server hostname matches the domain name of the subject of an X.509 certificate, which allows man-in-the-middle attackers to spoof an SSL SMTP server via an arbitrary certificate, a different vulnerability than CVE-2009-3766.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2011-1429?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mutt` | Red Hat:enterprise_linux:6::server | All versions | 5:1.5.20-2.20091214hg736b6a.el6_1.1 |
| `mutt-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 5:1.5.20-2.20091214hg736b6a.el6_1.1 |

Products: Mutt Mutt.

## How do I fix CVE-2011-1429?

Apply the vendor's patch.

## Is CVE-2011-1429 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-32055](https://insights.sbomify.com/CVE-2021-32055/): Memory corruption in n/a (critical 9.1)
- [CVE-2006-3242](https://insights.sbomify.com/CVE-2006-3242/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2642](https://insights.sbomify.com/CVE-2005-2642/): Memory corruption in n/a (high 7.5)
- [CVE-2004-0078](https://insights.sbomify.com/CVE-2004-0078/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0299](https://insights.sbomify.com/CVE-2003-0299/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-1429 and fix it if it is affected.

What it is: CVE-2011-1429 is a medium-severity vulnerability in n/a, published on 16 Mar 2011. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2011-1429 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-2011-1429/ (Markdown: https://insights.sbomify.com/CVE-2011-1429/index.md)
```

## Sources

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

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