Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

mpg321 vulnerabilities and fixes

Recent CVEs affecting mpg321, with upgrade or downgrade steps. 1 tracked.

mpg321 has 1 tracked vulnerability, 0 critical. A fixed release or vendor patch exists for 0. Most recent: 2019-07-24. Highest priority: CVE-2019-14247 (score 42/100).

FAQ

How do I fix mpg321 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 mpg321 being exploited right now?

None of the tracked mpg321 CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.

Which mpg321 CVE should I patch first?

CVE-2019-14247 currently ranks highest (42/100): The scan() function in mad.c in mpg321 0.3.2 allows remote attackers to trigger an out-of-bounds write via a z.

← Back to latest CVEs