CVE-2015-8076
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOut-of-bounds heap read vulnerability in the index_urlfetch function in Cyrus IMAP index.c. The flaw allows remote attackers to read sensitive heap memory via specially crafted urlfetch range requests.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 42.1= 13.2= 2.3.0= 2.3.1= 2.3.2= 2.3.3= 2.3.4= 2.3.5= 2.3.6= 2.3.7= 2.3.8= 2.3.9= 2.3.10= 2.3.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Cyrus IMAP versionRun 'cyrus-imapd -v' or 'rpm -q cyrus-imapd' (RPM-based) or 'dpkg -l | grep cyrus-imapd' (DEB-based) to retrieve the package versionAffected if Version is 2.3.0 through 2.3.11 inclusive, or package name matches Opensuse Leap 42.1 or Opensuse 13.2 with Cyrus IMAP installed
-
Confirm OpenSUSE system versionRun 'cat /etc/os-release' or 'lsb_release -a' to check the installed operating system versionAffected if Running OpenSUSE Leap 42.1 or OpenSUSE 13.2 with Cyrus IMAP package installed regardless of version
-
Verify urlfetch feature availabilityCheck the Cyrus IMAP configuration file (typically /etc/imapd.conf or /etc/cyrus/imapd.conf) for urlfetch-related settings such as 'urlfetch' or 'httpkeepalive' optionsAffected if The urlfetch module or feature is compiled in or enabled in the configuration, as the vulnerability exists in the index_urlfetch function
-
Identify running Cyrus IMAP daemon processesRun 'ps aux | grep cyrus' or 'systemctl status cyrus-imapd' to see if the Cyrus IMAP service is activeAffected if The Cyrus IMAP daemon is running and serving requests, making the vulnerable code path accessible to remote attackers
-
Check for http/gateway functionalityExamine the imapd.conf for 'httpkeepalive', 'httpport', or similar HTTP-related configurations that enable the urlfetch featureAffected if HTTP or gateway features are enabled in the Cyrus IMAP configuration, as the vulnerability is triggered via urlfetch range requests
A system is affected if it runs Cyrus IMAP version 2.3.0-2.3.11 or is OpenSUSE Leap 42.1/OpenSUSE 13.2 with Cyrus IMAP installed, and the urlfetch or HTTP gateway feature is enabled in the configuration.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpgrade Cyrus IMAP to version 2.3.19, 2.4.18, 2.5.4 or later to patch the vulnerability.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-8076 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-8076 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data