Denial of Service Vulnerability in libquicktime: CVE-2017-12145

libquicktime Updated 02 Oct 2025

Summary

02/08/2017
N/A
No i
Unrated
Not published

DEBIAN-CVE-2017-12145: In libquicktime 1.2.4, an allocation failure was found in the function quicktime_read_ftyp in ftyp.c, which allows attackers to cause a denial of service via a crafted file. Affects libquicktime versions 2:1.2.4-12 – 2:1.2.4-17. No fix is published. 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 Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

libquicktime is an open-source library designed for reading and writing QuickTime files. It provides functionalities for multimedia applications to handle video and audio data efficiently. However, certain versions of libquicktime are susceptible to a vulnerability that can be exploited through specially crafted files, leading to potential denial of service attacks.

Vulnerability Detail

The vulnerability identified as CVE-2017-12145 arises from an allocation failure in the function quicktime_read_ftyp located in ftyp.c of libquicktime version 1.2.4. Attackers can exploit this flaw by providing a maliciously crafted file that triggers the allocation failure, resulting in a denial of service condition. This vulnerability affects multiple Debian versions, including Debian 11, 12, 13, and 14, and is classified as having unimportant urgency.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

As a temporary workaround, avoid opening or processing QuickTime files from untrusted sources. Implementing strict file validation and sanitization can help mitigate the risk of exploitation until a patch is applied.

Conclusion

CVE-2017-12145 represents a significant denial of service vulnerability in libquicktime that can be exploited through malicious QuickTime files. Users are advised to update their packages promptly and implement workarounds to mitigate risks until a fix is applied.

See every vulnerability recorded for libquicktime →

Share this vulnerability

FAQ

CVE-2017-12145 is a vulnerability in libquicktime that can lead to denial of service due to an allocation failure when processing specially crafted QuickTime files.

The vulnerability affects libquicktime versions in Debian 11, 12, 13, and 14.

You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

If immediate updates are not possible, ensure to avoid processing untrusted QuickTime files and implement file validation to reduce risk.

For more information on vulnerabilities and how to monitor them, you can visit Vulert at https://vulert.com, which provides real-time alerts for open-source vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for libquicktime.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. 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