CVE-2004-2779

HIGHNVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2022-04-29. NVD baseline CVSS 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3%CVSS: 7.5Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

id3_utf16_deserialize() in utf16.c in libid3tag through 0.15.1b misparses ID3v2 tags encoded in UTF-16 with an odd number of bytes, triggering an endless loop allocating memory until an OOM condition is reached, leading to denial-of-service (DoS).

CVSS v3
7.5
EG Score
7.5(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation3% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
3%
EPSS %ILE
83%
KEV
Not listed

Published

February 20, 2018

Last Modified

November 20, 2024

Advisory Details (2)

Auto-updated Jul 25, 2026
Patch available.
generic

Bug 162647 – [id3demux] Consumes all available memory playing a tagged mp3

https://bugzilla.gnome.org/show_bug.cgi?id=162647
generic Patch Available

#304913 - libid3tag0: endless loop until OOM while parsing ID3v2 tag - Debian Bug report logs

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=304913

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 7× in last 7d / 26× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-25 14:11 UTCEPSS rescore
  2. 2026-07-24 14:11 UTCEPSS rescore
  3. 2026-07-23 00:47 UTCEG score recompute
  4. 2026-07-23 00:27 UTCEG score recompute
  5. 2026-07-22 23:51 UTCEG score recompute
  6. 2026-07-22 21:31 UTCEG score recompute
  7. 2026-07-21 17:18 UTCOSV refresh
  8. 2026-07-18 09:59 UTCEPSS rescore
  9. 2026-07-18 09:59 UTCEPSS rescore
  10. 2026-07-15 16:53 UTCEPSS rescore
  11. 2026-07-15 01:55 UTCEPSS rescore
  12. 2026-07-15 01:55 UTCEPSS rescore
  13. 2026-07-13 22:24 UTCEPSS rescore
  14. 2026-07-13 06:07 UTCEPSS rescore
  15. 2026-07-13 06:07 UTCEPSS rescore
  16. 2026-07-11 08:22 UTCEPSS rescore
  17. 2026-07-11 08:22 UTCEPSS rescore
  18. 2026-07-08 15:09 UTCEPSS rescore
  19. 2026-07-06 02:19 UTCEPSS rescore
  20. 2026-07-06 02:19 UTCEPSS rescore
  21. 2026-07-04 12:56 UTCOSV refresh
  22. 2026-07-02 14:00 UTCEPSS rescore
  23. 2026-07-01 15:01 UTCEPSS rescore
  24. 2026-06-29 14:02 UTCEPSS rescore
  25. 2026-06-29 14:02 UTCEPSS rescore
Show 56 more
  1. 2026-06-28 04:52 UTCEPSS rescore
  2. 2026-06-27 03:04 UTCEPSS rescore
  3. 2026-06-25 13:46 UTCEPSS rescore
  4. 2026-06-24 14:01 UTCEPSS rescore
  5. 2026-06-23 21:29 UTCEPSS rescore
  6. 2026-06-22 14:22 UTCEPSS rescore
  7. 2026-06-22 14:22 UTCEPSS rescore
  8. 2026-06-21 01:56 UTCEPSS rescore
  9. 2026-06-19 19:22 UTCEPSS rescore
  10. 2026-06-18 17:49 UTCEPSS rescore
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-17 17:49 UTCEPSS rescore
  13. 2026-06-17 17:49 UTCEPSS rescore
  14. 2026-06-16 17:49 UTCEPSS rescore
  15. 2026-06-16 17:49 UTCEPSS rescore
  16. 2026-06-16 00:39 UTCOSV refresh
  17. 2026-06-15 17:44 UTCEPSS rescore
  18. 2026-06-14 23:13 UTCEPSS rescore
  19. 2026-06-14 23:13 UTCEPSS rescore
  20. 2026-06-13 22:56 UTCEPSS rescore
  21. 2026-06-12 23:08 UTCEPSS rescore
  22. 2026-06-11 13:55 UTCEPSS rescore
  23. 2026-06-10 22:14 UTCEPSS rescore
  24. 2026-06-10 13:17 UTCEPSS rescore
  25. 2026-06-08 14:13 UTCEPSS rescore
  26. 2026-06-07 15:21 UTCEPSS rescore
  27. 2026-06-06 13:44 UTCEPSS rescore
  28. 2026-06-06 13:44 UTCEPSS rescore
  29. 2026-06-05 22:43 UTCEPSS rescore
  30. 2026-06-05 22:43 UTCEPSS rescore
  31. 2026-06-05 06:07 UTCEPSS rescore
  32. 2026-06-05 06:07 UTCEPSS rescore
  33. 2026-06-04 13:09 UTCEPSS rescore
  34. 2026-06-04 13:09 UTCEPSS rescore
  35. 2026-06-02 20:10 UTCEPSS rescore
  36. 2026-06-02 20:10 UTCEPSS rescore
  37. 2026-06-01 13:49 UTCEPSS rescore
  38. 2026-06-01 13:49 UTCEPSS rescore
  39. 2026-05-31 22:28 UTCEPSS rescore
  40. 2026-05-31 00:13 UTCEPSS rescore
  41. 2026-05-31 00:13 UTCEPSS rescore
  42. 2026-05-29 13:40 UTCEPSS rescore
  43. 2026-05-29 13:40 UTCEPSS rescore
  44. 2026-05-28 13:42 UTCEPSS rescore
  45. 2026-05-28 13:42 UTCEPSS rescore
  46. 2026-05-28 13:42 UTCEPSS rescore
  47. 2026-05-28 11:12 UTCEG score recompute
  48. 2026-05-28 11:12 UTCVendor advisory
  49. 2026-05-28 11:12 UTCGHSA enrichment
  50. 2026-05-27 13:37 UTCEPSS rescore
  51. 2026-05-26 13:41 UTCEPSS rescore
  52. 2026-05-26 13:41 UTCEPSS rescore
  53. 2026-05-26 07:16 UTCEPSS rescore
  54. 2026-05-26 07:16 UTCEPSS rescore
  55. 2026-05-24 16:42 UTCEPSS rescore
  56. 2026-05-23 04:48 UTCOSV refresh

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2004-2779?
CVE-2004-2779 is a high vulnerability published on February 20, 2018. id3utf16deserialize() in utf16.c in libid3tag through 0.15.1b misparses ID3v2 tags encoded in UTF-16 with an odd number of bytes, triggering an endless loop allocating memory until an OOM condition is reached, leading to denial-of-service (DoS).
When was CVE-2004-2779 disclosed?
CVE-2004-2779 was first published in the National Vulnerability Database on February 20, 2018, with the most recent update on November 20, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-2779 actively exploited?
CVE-2004-2779 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3% probability of exploitation in the next 30 days, which ranks it in the top 16.9% of all scored CVEs.
What is the CVSS score of CVE-2004-2779?
CVE-2004-2779 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2004-2779?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2004-2779, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2004-2779

Explore →

Is Your Infrastructure Affected by CVE-2004-2779?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs