Is CVE-2016-5827 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2016-5827 being exploited in the wild.

How severe is CVE-2016-5827?

High severity, with a CVSS score of 7.5, published 27 January 2017.

Which products and versions are affected?

Libical Project Libical 0.47, 1.0.

Is there a fix for CVE-2016-5827?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2016-5827 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2016-5827?

Check whether you run Libical Project Libical at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2016-5827: libical out-of-bounds read in icaltime_from_string

CVE-2016-5827 · Severity: high · CVSS 7.5 · Published 2017-01-27

libical is a widely used library for handling iCalendar data, often found in email clients like Thunderbird and calendar applications. A vulnerability in how it processes calendar files allows a remote attacker to crash applications using the library by sending a specially crafted calendar invitation or file. This results in a denial of service, potentially disrupting scheduling and communication services.

Technologies: Libical Project Libical. Vendors: Libical Project.

Quick answers

Is CVE-2016-5827 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2016-5827 being exploited in the wild.
How severe is CVE-2016-5827?: High severity, with a CVSS score of 7.5, published 27 January 2017.
Which products and versions are affected?: Libical Project Libical 0.47, 1.0.
Is there a fix for CVE-2016-5827?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2016-5827 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2016-5827?: Check whether you run Libical Project Libical at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

An out-of-bounds heap read vulnerability exists in libical versions 0.47 and 1.0 within the icaltime_from_string function. The flaw is triggered when the icalparser_parse_string function processes a malformed iCalendar string, leading to a buffer over-read during time string conversion. A remote, unauthenticated attacker can exploit this by providing a specially crafted .ics file or string, causing the application to crash (denial of service). The issue was identified using AddressSanitizer (ASan) and affects components relying on libical for calendar parsing, such as the Mozilla Calendar (Lightning) extension.

Affected products

libical project libical 0.47, 1.0

Timeline

2016-06-25: disclosed: Public disclosure on oss-security mailing list
2017-01-27: advisory: NVD publication date

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.