# CVE-2011-3372: Auth bypass in n/a

> Remote attackers can bypass authentication in the Cyrus IMAPd NNTP server by sending an incomplete authentication sequence.

- **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:** 24 Dec 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-vq7q-vrrq-cr5f

## What is CVE-2011-3372?

CVE-2011-3372 is a high-severity authentication bypass vulnerability in n/a, published on 24 Dec 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

imap/nntpd.c in the NNTP server (nntpd) for Cyrus IMAPd 2.4.x before 2.4.12 allows remote attackers to bypass authentication by sending an AUTHINFO USER command without sending an additional AUTHINFO PASS command.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Cyrus Imapd.

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

Upgrade to a fixed version.

## Is CVE-2011-3372 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0546](https://insights.sbomify.com/CVE-2005-0546/): Memory corruption in n/a (high 7.5)
- [CVE-2006-2502](https://insights.sbomify.com/CVE-2006-2502/): Memory corruption in n/a (medium 5.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-3372 is a high-severity authentication bypass vulnerability in n/a, published on 24 Dec 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-3372 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-3372/ (Markdown: https://insights.sbomify.com/CVE-2011-3372/index.md)
```

## Sources

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

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