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

> Man-in-the-middle attackers can spoof SSL chat servers by bypassing hostname verification in WeeChat, exposing user communications.

- **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:** Not needed
- **Fix available:** Yes
- **Published:** 16 Mar 2011
- **Updated:** 17 Sep 2024
- **Also known as:** DEBIAN-CVE-2011-1428, GHSA-4663-xvr2-gqpr

## What is CVE-2011-1428?

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

### Official description

Wee Enhanced Environment for Chat (aka WeeChat) 0.3.4 and earlier does not properly verify that the 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 chat server via an arbitrary certificate, related to incorrect use of the GnuTLS API.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Flashtux Weechat.

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

Upgrade to a fixed version.

## Is CVE-2011-1428 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-5534](https://insights.sbomify.com/CVE-2012-5534/): Command injection in n/a (high 7.5)
- [CVE-2012-5854](https://insights.sbomify.com/CVE-2012-5854/): Memory corruption in n/a (high 7.5)
- [CVE-2009-0661](https://insights.sbomify.com/CVE-2009-0661/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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