Alerts This Week
Warning Icon 1 626
Alerts This Week
Warning Icon 1 626

Gentoo GLSA-201904-02 Normal: Libical Denial of Service Threat

gentoo
Calendar Grey April 2, 2019
Dist Gentoo Esm H88
Libical exhibits various security flaws on Gentoo, which could lead to Denial of Service. It is crucial to upgrade to ensure safety.
Multiple vulnerabilities have been found in Libical, the worst of which could result in a Denial of Service condition.

Summary

Multiple vulnerabilities have been discovered in Libical. Please review the referenced CVE identifiers for details.

Resolution

All Libical users should upgrade to the latest version: # emerge --sync # emerge --ask --oneshot --verbose ">=dev-libs/libical-3.0.0"

References

[ 1 ] CVE-2016-5823 https://nvd.nist.gov/vuln/detail/CVE-2016-5823 [ 2 ] CVE-2016-5824 https://nvd.nist.gov/vuln/detail/CVE-2016-5824

Availability

This GLSA and any updates to it are available for viewing at the Gentoo Security Website: https://security.gentoo.org/glsa/201904-02
style>.gentoo_availability{display:block;}

Concerns

Security is a primary focus of Gentoo Linux and ensuring the confidentiality and security of our users' machines is of utmost importance to us. Any security concerns should be addressed to security@gentoo.org or alternatively, you may file a bug at https://bugs.gentoo.org.

Severity: Normal
Title: Libical: Multiple vulnerabilities
Date: April 02, 2019
Bugs: #587572, #587574
ID: 201904-02

Synopsis

Multiple vulnerabilities have been found in Libical, the worst of which could result in a Denial of Service condition.

Background

An Open Source implementation of the iCalendar protocols and protocol data units.

Get the latest News and Insights

Get the latest Linux and open source security news straight to your inbox.

Affected Packages

------------------------------------------------------------------- Package / Vulnerable / Unaffected ------------------------------------------------------------------- 1 dev-libs/libical < 3.0.0 >= 3.0.0

Impact

===== Please review the referenced CVE identifiers for details.

Workaround

There is no known workaround at this time.

Related News

Your message here