VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

amarok: vulnerability history, versions and safety

amarok is a package in the Debian ecosystem. Vulert records 12 vulnerabilities for it across 2 releases, from Feb 2007 to May 2020. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded U12
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all amarok vulnerabilities

Vulert verdict on amarok i

Updated on 23 Oct 2026

Careful: 2 of the 12 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 12 vulnerabilities on record across 13 years, none in the last year.

What to do: Plan around the 2 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 12 over 13 years · 0 in the last year i
  • Latest disclosure 20 May 2020 i
  • Highest CVSS 5.5 i
  • With no published fix 2 i

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 Versions

Which versions are affected

Every version Vulert holds for amarok, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
3.3.1-1 U1 No Details →
3.2.2-1 U2 No Details →

Newest 2 of 2 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2007 4
  • 2008 2
  • 2009 4
  • 2020 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 12 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for amarok

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Memory Leak in Amarok 2.8.0 Allows Denial of Service 5.5 medium No fix published 20 May 2020
Critical Integer Overflow Vulnerability in Amarok Package N/A unrated 1.4.10-2 16 Jan 2009
Denial of Service Vulnerability in Amarok: Crash via Magnatune Album Browser N/A unrated 1.4.4-4 08 Feb 2007
Symlink Vulnerability in Amarok Package Allows Local File Overwrite N/A unrated 1.4.10-1 14 Aug 2008
Arbitrary Command Execution Vulnerability in Amarok Package N/A unrated 1.4.4-1 08 Feb 2007

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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 amarok

Is amarok safe to use?

Vulert records 12 vulnerabilities for amarok in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 12 not yet rated. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does amarok have?

12 vulnerabilities are recorded for amarok in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 12 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new amarok vulnerabilities disclosed?

0 vulnerabilities were recorded for amarok in the last 12 months, and the oldest entry in this database dates to 08 Feb 2007. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of amarok are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor amarok for upcoming vulnerabilities?

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