Strix
26.1K

CVE-2015-8078

UnknownEPSS 2.75%

Last modified

CVE-2015-8078 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.75% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
2.75%

84.3th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
OpensuseLeap42.1
OpensuseOpensuse13.2
CyrusImap2.3.0
CyrusImap2.3.1
CyrusImap2.3.2
CyrusImap2.3.3
CyrusImap2.3.4
CyrusImap2.3.5
CyrusImap2.3.6
CyrusImap2.3.7
CyrusImap2.3.8
CyrusImap2.3.9
CyrusImap2.3.10
CyrusImap2.3.11
CyrusImap2.3.12
CyrusImap2.3.13
CyrusImap2.3.14
CyrusImap2.3.15
CyrusImap2.3.16
CyrusImap2.3.17
CyrusImap2.3.18
CyrusImap2.4.0
CyrusImap2.4.1
CyrusImap2.4.2
CyrusImap2.4.3
CyrusImap2.4.4
CyrusImap2.4.5
CyrusImap2.4.6
CyrusImap2.4.7
CyrusImap2.4.8
CyrusImap2.4.9
CyrusImap2.4.10
CyrusImap2.4.11
CyrusImap2.4.12
CyrusImap2.4.13
CyrusImap2.4.14
CyrusImap2.4.15
CyrusImap2.4.16
CyrusImap2.4.17
CyrusImap2.5.0
CyrusImap2.5.1
CyrusImap2.5.2
CyrusImap2.5.3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2015-8078?
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.
How severe is CVE-2015-8078?
Severity scoring for CVE-2015-8078 is pending analysis. The EPSS model estimates a 2.75% probability of exploitation in the next 30 days.
How do I fix CVE-2015-8078?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2015

View all 2015CVEs →

Are you affected by CVE-2015-8078?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST