# CVE-2011-3208: Memory corruption in n/a > Remote attackers can execute arbitrary code via a crafted NNTP command due to a stack-based buffer overflow in Cyrus IMAP Server. - **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:** 14 Sep 2011 - **Updated:** 6 Aug 2024 - **Also known as:** GHSA-46rx-vcfq-hxc2, RHSA-2011:1317 ## What is CVE-2011-3208? CVE-2011-3208 is a high-severity memory corruption vulnerability in n/a, published on 14 Sep 2011. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description Stack-based buffer overflow in the split_wildmats function in nntpd.c in nntpd in Cyrus IMAP Server before 2.3.17 and 2.4.x before 2.4.11 allows remote attackers to execute arbitrary code via a crafted NNTP command. Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) ## Which versions are affected by CVE-2011-3208? It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `cyrus-imapd` | Red Hat:enterprise_linux:4::as | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-devel` | Red Hat:enterprise_linux:4::as | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-murder` | Red Hat:enterprise_linux:4::as | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-nntp` | Red Hat:enterprise_linux:4::as | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-utils` | Red Hat:enterprise_linux:4::as | All versions | 0:2.2.12-16.el4 | | `perl-Cyrus` | Red Hat:enterprise_linux:4::as | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-devel` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-murder` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-nntp` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-utils` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.2.12-16.el4 | | `perl-Cyrus` | Red Hat:enterprise_linux:4::desktop | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd` | Red Hat:enterprise_linux:4::es | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-devel` | Red Hat:enterprise_linux:4::es | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-murder` | Red Hat:enterprise_linux:4::es | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-nntp` | Red Hat:enterprise_linux:4::es | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-utils` | Red Hat:enterprise_linux:4::es | All versions | 0:2.2.12-16.el4 | | `perl-Cyrus` | Red Hat:enterprise_linux:4::es | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-devel` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-murder` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-nntp` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd-utils` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.2.12-16.el4 | | `perl-Cyrus` | Red Hat:enterprise_linux:4::ws | All versions | 0:2.2.12-16.el4 | | `cyrus-imapd` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-debuginfo` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-devel` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-perl` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-utils` | Red Hat:enterprise_linux:5::client_workstation | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd` | Red Hat:enterprise_linux:5::server | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-devel` | Red Hat:enterprise_linux:5::server | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-perl` | Red Hat:enterprise_linux:5::server | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd-utils` | Red Hat:enterprise_linux:5::server | All versions | 0:2.3.7-12.el5_7.1 | | `cyrus-imapd` | Red Hat:enterprise_linux:6::server | All versions | 0:2.3.16-6.el6_1.3 | | `cyrus-imapd-debuginfo` | Red Hat:enterprise_linux:6::server | All versions | 0:2.3.16-6.el6_1.3 | Products: Cmu Cyrus Imap Server. ## How do I fix CVE-2011-3208? Upgrade to a fixed version. ## Is CVE-2011-3208 being exploited? There is no known exploitation of CVE-2011-3208 in the wild and no public exploit code. ## Other vulnerabilities in n/a - [CVE-2011-1926](https://insights.sbomify.com/CVE-2011-1926/): Other in n/a (medium 5.1) - [CVE-2009-2632](https://insights.sbomify.com/CVE-2009-2632/): Memory corruption in n/a (medium 4.4) - [CVE-2011-3481](https://insights.sbomify.com/CVE-2011-3481/): Null dereference in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2011-3208 and fix it if it is affected. What it is: CVE-2011-3208 is a high-severity memory corruption vulnerability in n/a, published on 14 Sep 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-3208 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-3208/ (Markdown: https://insights.sbomify.com/CVE-2011-3208/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2011-3208 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2011-3208 - OSV: https://osv.dev/vulnerability/CVE-2011-3208 --- From sbomify Insights: https://insights.sbomify.com/CVE-2011-3208/ Summaries are generated and may contain mistakes; the official description above is the record.