How severe is CVE-2003-0969?

CVE-2003-0969 has a CVSS 2.0 base score of 7.5, rated high severity.

Is CVE-2003-0969 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2003-0969?

CVE-2003-0969 affects Mpg321. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2003-0969?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2003-0969 published?

CVE-2003-0969 was published on 2004-01-20 and last updated on 2026-06-16.

CVE-2003-0969

CVE-2003-0969 is a high-severity vulnerability in Mpg321 with a CVSS 2.0 base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low.

Key facts

Severity: High (CVSS 2.0 base score 7.5)
EPSS exploit prediction: 3% (85th percentile)
Actively exploited: Not listed in CISA KEV
Affected product: Mpg321
Published: 2004-01-20
Last modified: 2026-06-16

Description

mpg321 0.2.10 allows remote attackers to overwrite memory and possibly execute arbitrary code via an mp3 file that passes certain strings to the printf function, possibly triggering a format string vulnerability.

Frequently asked questions

What is CVE-2003-0969?: mpg321 0.2.10 allows remote attackers to overwrite memory and possibly execute arbitrary code via an mp3 file that passes certain strings to the printf function, possibly triggering a format string vulnerability.
How severe is CVE-2003-0969?: CVE-2003-0969 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2003-0969 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 3% (85th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2003-0969?: CVE-2003-0969 affects Mpg321. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2003-0969?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2003-0969 published?: CVE-2003-0969 was published on 2004-01-20 and last updated on 2026-06-16.

References

Affected products (1)

cpe:2.3:a:mpg321:mpg321:0.2.10:*:*:*:*:*:*:*

More vulnerabilities in Mpg321

CVE-2002-0272 — Critical (CVSS 10.0): Buffer overflows in mpg321 before 0.2.9 allows local and possibly remote attackers to execute arbitrary code via a long…

All CVEs affecting Mpg321 →