Use-after-free vulnerability in libical

libical Updated 02 Oct 2025

Summary

28/05/2017
N/A
Yes i
Unrated
Not published

DLA-959-1: libical - security update. Affects libical versions < 0.48-2+deb7u1. Fixed in 0.48-2+deb7u1. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libical is an iCalendar library used for parsing, generating, and manipulating iCalendar data. It provides functionality for working with calendar events, tasks, and other calendar-related information. The library is commonly used in applications that handle calendar data, such as email clients and calendar applications. However, a use-after-free vulnerability has been discovered in libical, which could allow remote attackers to cause a denial of service and potentially read heap memory by exploiting a specially crafted .ICS file.

Vulnerability Detail

The use-after-free vulnerability in libical occurs when the library attempts to access memory that has already been freed. This can lead to a crash or potentially allow an attacker to read sensitive information from the heap. By crafting a malicious .ICS file, an attacker can trigger this vulnerability and cause the application using libical to crash or disclose sensitive information. This vulnerability poses a significant risk to applications that handle calendar data and rely on libical for parsing and manipulating iCalendar files.

How To Fix

Minimum fixed version

0.48-2+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libical

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is necessary to apply the patch provided in the updated libical package to mitigate the risk.

Conclusion

The use-after-free vulnerability in libical can be exploited by remote attackers to cause a denial of service and potentially read heap memory. It is crucial for users to upgrade their libical packages to the fixed version to mitigate the risk. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for libical →

Share this vulnerability

FAQ

libical is an iCalendar library used for parsing, generating, and manipulating iCalendar data. It is commonly used in applications that handle calendar information.

A use-after-free vulnerability occurs when a program attempts to access memory that has already been freed. This can lead to crashes or potentially allow attackers to read sensitive information.

This vulnerability can be exploited by crafting a specially crafted .ICS file and tricking an application using libical to process it. The attacker can then cause the application to crash or potentially read sensitive information.

The impact of this vulnerability can vary depending on the application using libical. In some cases, it can lead to a denial of service, crashing the application. In more severe cases, it may allow attackers to read sensitive information from the heap.

To protect your application, it is recommended to upgrade the libical package to the fixed version (0.48-2+deb7u1 or later). Additionally, it is good practice to validate and sanitize any user-supplied calendar data before processing it with libical.

Related vulnerabilities

Recent vulnerabilities recorded for libical.

How To Fix

Minimum fixed version

0.48-2+deb7u1

This is the first release that contains the fix.

sudo apt-get install --only-upgrade libical

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback