Skip to content
Fencer Intel
high 7.5

CVE-2015-8078 json

Integer 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 uns…

published 10y ago modified 4mo ago also EUVD-2015-7971

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

Summary

Integer 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 unspecified impact via vectors related to urlfetch range checks and the section_offset variable. NOTE: this vulnerability exists because of an incomplete fix for CVE-2015-8076.

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

  • cyrus-imapd openSUSE Tumbleweed 2.4.18-3.4

opensuse advisories openSUSE-SU-2024:10015-1

Is CVE-2015-8078 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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-8078 updated cvss 5.8

cyrus-imapd: Integer overflow 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
    not affected: vulnerable code not present

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

2.75% chance of exploitation in the next 30 days, higher than 86% 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

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.