Vulnerability Database · Debian · libquicktime · Version

libquicktime 2:1.2.4-17

2:1.2.4-17 is affected by 4 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to.

Critical 0 High 0 Medium 2 Low 0 Unrated 2

Database updated 23/Oct/2026

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

libquicktime 2:1.2.4-17 vulnerabilities

4 vulnerabilities cover libquicktime 2:1.2.4-17. Open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Denial of Service Vulnerability in libquicktime 6.5 medium No fix published 02 Aug 2017
Denial of Service in libquicktime 6.5 medium No fix published 02 Aug 2017
Denial of Service Vulnerability in libquicktime: CVE-2017-12143 N/A unrated No fix published 02 Aug 2017
Denial of Service Vulnerability in libquicktime: CVE-2017-12145 N/A unrated No fix published 02 Aug 2017

Looking for another version, or everything Vulert holds for libquicktime?

All versions → Full vulnerability list →

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 →

Questions

About libquicktime 2:1.2.4-17

Is libquicktime 2:1.2.4-17 vulnerable?

Yes. 4 vulnerabilities in the Vulert database cover libquicktime 2:1.2.4-17: 0 critical, 0 high, 2 medium and 0 low, plus 2 not yet rated. Each entry above names the fixed version to move to.

How do I monitor libquicktime for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the libquicktime version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.