PatchTheCVElibical project vulnerabilities
Recent CVEs affecting libical project products. 6 tracked.
libical project has 6 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 1. Most recent: 2017-01-27. Highest priority: CVE-2016-9584 (score 58/100).
- CVE-2016-9584 CRITICAL 9.1 UPGRADE libical allows remote attackers to cause a denial of service (use-after-free) and possibly read heap memory vi
- CVE-2016-5827 HIGH 7.5 DOWNGRADE The icaltime_from_string function in libical 0.47 and 1.0 allows remote attackers to cause a denial of service
- CVE-2016-5826 HIGH 7.5 DOWNGRADE The parser_get_next_char function in libical 0.47 and 1.0 allows remote attackers to cause a denial of service
- CVE-2016-5825 MEDIUM 5.5 DOWNGRADE The icalparser_parse_string function in libical 0.47 and 1.0 allows remote attackers to cause a denial of serv
- CVE-2016-5824 MEDIUM 5.5 DOWNGRADE MITIGATE libical 1.0 allows remote attackers to cause a denial of service (use-after-free) via a crafted ics file.
- CVE-2016-5823 MEDIUM 5.5 DOWNGRADE The icalproperty_new_clone function in libical 0.47 and 1.0 allows remote attackers to cause a denial of servi
FAQ
How do I fix libical project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is libical project being exploited right now?
None of the tracked libical project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which libical project CVE should I patch first?
CVE-2016-9584 currently ranks highest (58/100): libical allows remote attackers to cause a denial of service (use-after-free) and possibly read heap memory vi.