The index_urlfetch function in index.c in Cyrus IMAP 2.3.x before 2.3.19, 2.4.x before 2.4.18, 2.5.x before 2.5.4 allows remote attackers to
The index_urlfetch function in index.c in Cyrus IMAP 2.3.x before 2.3.19, 2.4.x before 2.4.18, 2.5.x before 2.5.4 allows remote attackers to obtain sensitive information or possibly have unspecified other impact via vectors related to the urlfetch range, which triggers an out-of-bounds heap read.
- Published
- Dec 3, 2015
- Updated
- Jun 16, 2026
- EPSS
- 3.3% · 88th 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
31
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 3.3%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| cyrus | imap | cpe:2.3:a:cyrus:imap |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
| opensuse | opensuse | cpe:2.3:o:opensuse:opensuse |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- cyrus imap2.3.0
- cyrus imap2.3.1
- cyrus imap2.3.10
- cyrus imap2.3.11
- cyrus imap2.3.12
- cyrus imap2.3.13
- cyrus imap2.3.14
- cyrus imap2.3.15
- cyrus imap2.3.16
- cyrus imap2.3.17
- cyrus imap2.3.18
- cyrus imap2.3.2
- cyrus imap2.3.3
- cyrus imap2.3.4
- cyrus imap2.3.5
- cyrus imap2.3.6
- cyrus imap2.3.7
- cyrus imap2.3.8
- cyrus imap2.3.9
- cyrus imap2.4.0
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| SUSE:Linux Enterprise Server 12 | cyrus-imapd | before 2.3.18-37.1 | 2.3.18-37.1 |
| SUSE:Linux Enterprise Software Development Kit 11 SP4 | cyrus-imapd | before 2.3.11-60.65.67.1 | 2.3.11-60.65.67.1 |
Same product
cyrus: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-11356The CalDAV feature in httpd in Cyrus IMAP 2.5.x through 2.5.12 and 3.0.x through 3.0.9 allows remote attackers to execute arbitrary code via41Plan
- CVE-2019-18928Cyrus IMAP 2.5.x before 2.5.14 and 3.x before 3.0.12 allows privilege escalation because an HTTP request may be interpreted in the authentic40Plan
- CVE-2017-14230In the mboxlist_do_find function in imap/mboxlist.c in Cyrus IMAP before 3.0.4, an off-by-one error in prefix calculation for the LIST comma37Monitor
- CVE-2021-33582Cyrus IMAP before 3.4.2 allows remote attackers to cause a denial of service (multiple-minute daemon hang) via input that is mishandled duri31Monitor
- CVE-2015-8078Integer overflow in the index_urlfetch function in imap/index.c in Cyrus IMAP 2.3.19, 2.4.18, and 2.5.6 allows remote attackers to have unsp31Monitor
- CVE-2015-8077Integer overflow in the index_urlfetch function in imap/index.c in Cyrus IMAP 2.3.19, 2.4.18, and 2.5.6 allows remote attackers to have unsp31Monitor
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 |
|---|---|---|
| suse:cyrus-imapd | 2.3.18-37.1 · SUSE:Linux Enterprise Server 12 | 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.
No commit or PR link among the references.
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
- www.openwall.com/lists/oss-security/2015/11/04/3
- lists.opensuse.org/opensuse-security-announce/2016-05/msg00066.html
- lists.opensuse.org/opensuse-security-announce/2016-06/msg00000.html
- lists.opensuse.org/opensuse-updates/2015-09/msg00037.html
- lists.opensuse.org/opensuse-updates/2015-09/msg00038.html
- www.openwall.com/lists/oss-security/2015/09/29/2
- www.openwall.com/lists/oss-security/2015/09/30/3
- cyrus.foundation/cyrus-imapd/commit/?id=07de4ff1bf2fa340b9d77b8e7de8d43d47a33921
- cyrus.foundation/cyrus-imapd/commit/?id=c21e179c1f6b968fe69bebe079176714e511587b
- docs.cyrus.foundation/imap/release-notes/2.3/x/2.3.19.html
- docs.cyrus.foundation/imap/release-notes/2.4/x/2.4.18.html
- docs.cyrus.foundation/imap/release-notes/2.5/x/2.5.4.html
Vendor advisories and official records. Exploit/PoC links are deliberately left out.