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 al
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.
- Published
- Sep 14, 2011
- Updated
- Jun 16, 2026
- EPSS
- 5.4% · 92th percentile
- CWE
- CWE-119
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
32
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 2 / 30 · 5.4%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| cmu | cyrus imap server | cpe:2.3:a:cmu:cyrus_imap_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cmu cyrus imap serverup to 2.3.16 inclusive
- cmu cyrus imap server2.0.17
- cmu cyrus imap server2.1.16
- cmu cyrus imap server2.1.17
- cmu cyrus imap server2.1.18
- cmu cyrus imap server2.2.10
- cmu cyrus imap server2.2.11
- cmu cyrus imap server2.2.12
- cmu cyrus imap server2.2.13
- cmu cyrus imap server2.2.13p1
- cmu cyrus imap server2.2.14
- cmu cyrus imap server2.2.8
- cmu cyrus imap server2.2.9
- cmu cyrus imap server2.3.0
- cmu cyrus imap server2.3.1
- cmu cyrus imap server2.3.10
- cmu cyrus imap server2.3.11
- cmu cyrus imap server2.3.12
- cmu cyrus imap server2.3.13
- cmu cyrus imap server2.3.14
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:5.0 | cyrus-imapd-2.2 | before 2.2.13-14+lenny5 | 2.2.13-14+lenny5 |
| Debian:6.0 | cyrus-imapd-2.2 | before 2.2.13-19+squeeze2 | 2.2.13-19+squeeze2 |
| Red Hat:enterprise_linux:4::as | cyrus-imapd | before 0:2.2.12-16.el4 | 0:2.2.12-16.el4 |
| Red Hat:enterprise_linux:4::as | cyrus-imapd-debuginfo | before 0:2.2.12-16.el4 | 0:2.2.12-16.el4 |
| Red Hat:enterprise_linux:4::as | cyrus-imapd-devel | before 0:2.2.12-16.el4 | 0:2.2.12-16.el4 |
| Red Hat:enterprise_linux:4::as | cyrus-imapd-murder | before 0:2.2.12-16.el4 | 0:2.2.12-16.el4 |
| Red Hat:enterprise_linux:4::as | cyrus-imapd-nntp | before 0:2.2.12-16.el4 | 0:2.2.12-16.el4 |
| Red Hat:enterprise_linux:4::as | cyrus-imapd-utils | before 0:2.2.12-16.el4 | 0:2.2.12-16.el4 |
| Red Hat:enterprise_linux:4::as | perl-Cyrus | before 0:2.2.12-16.el4 | 0:2.2.12-16.el4 |
| Red Hat:enterprise_linux:5::client_workstation | cyrus-imapd | before 0:2.3.7-12.el5_7.1 | 0:2.3.7-12.el5_7.1 |
| Red Hat:enterprise_linux:5::client_workstation | cyrus-imapd-debuginfo | before 0:2.3.7-12.el5_7.1 | 0:2.3.7-12.el5_7.1 |
| Red Hat:enterprise_linux:5::client_workstation | cyrus-imapd-devel | before 0:2.3.7-12.el5_7.1 | 0:2.3.7-12.el5_7.1 |
| Red Hat:enterprise_linux:5::client_workstation | cyrus-imapd-perl | before 0:2.3.7-12.el5_7.1 | 0:2.3.7-12.el5_7.1 |
| Red Hat:enterprise_linux:5::client_workstation | cyrus-imapd-utils | before 0:2.3.7-12.el5_7.1 | 0:2.3.7-12.el5_7.1 |
| Red Hat:enterprise_linux:6::server | cyrus-imapd | before 0:2.3.16-6.el6_1.3 | 0:2.3.16-6.el6_1.3 |
| Red Hat:enterprise_linux:6::server | cyrus-imapd-debuginfo | before 0:2.3.16-6.el6_1.3 | 0:2.3.16-6.el6_1.3 |
| Red Hat:enterprise_linux:6::server | cyrus-imapd-devel | before 0:2.3.16-6.el6_1.3 | 0:2.3.16-6.el6_1.3 |
| Red Hat:enterprise_linux:6::server | cyrus-imapd-utils | before 0:2.3.16-6.el6_1.3 | 0:2.3.16-6.el6_1.3 |
Same product
cmu: all recordsOther highest-scoring records for the same primary product.
- CVE-2011-1926The STARTTLS implementation in Cyrus IMAP Server before 2.4.7 does not properly restrict I/O buffering, which allows man-in-the-middle attac21Monitor
- CVE-2011-3481The index_get_ids function in index.c in imapd in Cyrus IMAP Server before 2.4.11, when server-side threading is enabled, allows remote atta18Monitor
- CVE-2009-2632Buffer overflow in the SIEVE script component (sieve/script.c), as used in cyrus-imapd in Cyrus IMAP Server 2.2.13 and 2.3.14, and Dovecot 117Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:cyrus-imapd-2.2 | 2.2.13-19+squeeze2 · Debian:6.0 | Package registry (OSV) |
| red hat:cyrus-imapd | 0:2.2.12-16.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:cyrus-imapd-debuginfo | 0:2.2.12-16.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:cyrus-imapd-devel | 0:2.2.12-16.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:cyrus-imapd-murder | 0:2.2.12-16.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:cyrus-imapd-nntp | 0:2.2.12-16.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:cyrus-imapd-perl | 0:2.3.7-12.el5_7.1 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:cyrus-imapd-utils | 0:2.2.12-16.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:perl-Cyrus | 0:2.2.12-16.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
- asg.andrew.cmu.edu/archive/message.php?mailbox=archive.cyrus-announce&msg=199
- asg.andrew.cmu.edu/archive/message.php?mailbox=archive.cyrus-announce&msg=200
- git.cyrusimap.org/cyrus-imapd/commit/?id=0f8f026699829b65733c3081657b24e2174f4f4d
- git.cyrusimap.org/cyrus-imapd/commit/?id=3244c18c928fa331f6927e2b8146abe90feafddd
- lists.opensuse.org/opensuse-updates/2011-09/msg00019.html
- secunia.com/advisories/45938
- secunia.com/advisories/45975
- secunia.com/advisories/46064
- securitytracker.com/id?1026031
- www.debian.org/security/2011/dsa-2318
- www.mandriva.com/security/advisories?name=MDVSA-2011:149
- www.osvdb.org/75307
- www.redhat.com/support/errata/RHSA-2011-1317.html
- www.securityfocus.com/bid/49534
- bugzilla.redhat.com/show_bug.cgi?id=734926
- exchange.xforce.ibmcloud.com/vulnerabilities/69679
- hermes.opensuse.org/messages/11723935
Vendor advisories and official records. Exploit/PoC links are deliberately left out.