Skip to content
Fencer Intel
high 7.5

CVE-2015-8076 json

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 t…

published 2015-12-03 10 y ago modified 2026-06-17 4 mo ago also EUVD-2015-7969

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
3.3%
EPSS 3.3% chance of exploitation in 30 days, percentile 88%
public exploits
0
none known

Summary

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.

Patch / fix

  • cyrus-imapd SLES for SAP 11 SP4, SLES 11 SP4, SLE Software Development Kit 11 SP4 2.3.11-60.65.67.1
  • cyrus-imapd SLES for SAP 12 SP1, SLES for SAP 12, SLES 12 SP1 +1 more 2.3.18-37.1

suse advisories SUSE-SU-2016:1459-1SUSE-SU-2016:1457-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2015-8076 updated cvss 3.5

cyrus-imapd: Out of bounds heap read in index_urlfetch

  • Red Hat Enterprise Linux 5 cyrus-imapd Red Hat Enterprise Linux 6 cyrus-imapd, cyrus-imapd-utils Red Hat Enterprise Linux 7 cyrus-imapd, cyrus-imapd-utils
    affected: no fix planned “Will not fix”

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

3.26% chance of exploitation in the next 30 days, higher than 88% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.