CVE-2008-0485

HIGHCVSS v2 · 9.39.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 8.9% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
9.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • Public exploit code is available (Exploit-DB (verified), epss top5pct, public exploit)
CISA-KEV: Not listedEPSS PROB: 9%CVSS v2: 9.3Exploit: Exploit-DB (verified) · epss top5pct · public exploitExposed: 0

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

Array index error in libmpdemux/demux_mov.c in MPlayer 1.0 rc2 and earlier might allow remote attackers to execute arbitrary code via a QuickTime MOV file with a crafted stsc atom tag.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3(low)
EG Risk
72(Track)
EG Risk 72/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
Severity93% × 45%
Exploitation65% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
9%
EPSS %ILE
95%
KEV
Not listed

Published

February 5, 2008

Last Modified

April 23, 2026

References (30)

Affected Packages

(6 across 6 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
mplayer—1.0~rc2-8—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mplayer—1.0~rc2-8—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mplayer—1.0~rc2-8—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mplayer—1.0~rc2-8—
Debian:4.0(1)
PackageVulnerable rangeFixed inDependents
mplayer1.0~rc1-12etch, 1.0~rc1-12etch11.0~rc1-12etch2—
Debian:5.0(1)
PackageVulnerable rangeFixed inDependents
mplayer—1.0~rc2-7+lenny1—

Data Freshness Timeline

(refreshed 1× in last 7d / 10× 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.

Showing the most recent 100 of 120 total refreshes for this CVE.

  1. 2026-09-18 19:20 UTCEPSS rescore
  2. 2026-09-17 19:20 UTCEPSS rescore
  3. 2026-09-15 03:04 UTCEPSS rescore
  4. 2026-09-14 20:44 UTCOSV refresh
  5. 2026-09-12 14:54 UTCEPSS rescore
  6. 2026-09-05 15:22 UTCEPSS rescore
  7. 2026-09-04 13:55 UTCEPSS rescore
  8. 2026-09-04 04:59 UTCEPSS rescore
  9. 2026-08-30 01:14 UTCEPSS rescore
  10. 2026-08-26 20:16 UTCOSV refresh
  11. 2026-08-10 10:39 UTCOSV refresh
  12. 2026-08-08 16:30 UTCEPSS rescore
  13. 2026-08-07 16:20 UTCEPSS rescore
  14. 2026-08-06 13:41 UTCEPSS rescore
  15. 2026-08-05 19:11 UTCEPSS rescore
  16. 2026-08-04 15:03 UTCEPSS rescore
  17. 2026-08-03 10:28 UTCEPSS rescore
  18. 2026-07-30 16:22 UTCEPSS rescore
  19. 2026-07-30 01:25 UTCEPSS rescore
  20. 2026-07-28 15:30 UTCEPSS rescore
  21. 2026-07-26 13:34 UTCEG score recompute▲ 9.30
  22. 2026-07-25 14:12 UTCEPSS rescore
  23. 2026-07-25 10:41 UTCOSV refresh
  24. 2026-07-24 14:11 UTCEPSS rescore
  25. 2026-07-23 14:13 UTCEPSS rescore
Show 75 more
  1. 2026-07-23 00:55 UTCEG score recompute
  2. 2026-07-23 00:34 UTCEG score recompute
  3. 2026-07-23 00:00 UTCEG score recompute
  4. 2026-07-22 21:39 UTCEG score recompute
  5. 2026-07-22 14:03 UTCEPSS rescore
  6. 2026-07-21 15:19 UTCEPSS rescore
  7. 2026-07-20 17:03 UTCEPSS rescore
  8. 2026-07-18 09:59 UTCEPSS rescore
  9. 2026-07-16 16:58 UTCEPSS rescore
  10. 2026-07-15 16:54 UTCEPSS rescore
  11. 2026-07-15 16:54 UTCEPSS rescore
  12. 2026-07-15 01:55 UTCEPSS rescore
  13. 2026-07-11 08:22 UTCEPSS rescore
  14. 2026-07-08 15:09 UTCEPSS rescore
  15. 2026-07-08 05:27 UTCOSV refresh
  16. 2026-07-06 02:19 UTCEPSS rescore
  17. 2026-07-05 02:26 UTCEPSS rescore
  18. 2026-07-04 06:27 UTCEPSS rescore
  19. 2026-07-04 06:27 UTCEPSS rescore
  20. 2026-07-02 14:00 UTCEPSS rescore
  21. 2026-07-01 15:02 UTCEPSS rescore
  22. 2026-07-01 15:02 UTCEPSS rescore
  23. 2026-06-30 23:19 UTCEPSS rescore
  24. 2026-06-30 23:19 UTCEPSS rescore
  25. 2026-06-29 14:02 UTCEPSS rescore
  26. 2026-06-29 14:02 UTCEPSS rescore
  27. 2026-06-28 14:03 UTCEPSS rescore
  28. 2026-06-28 04:52 UTCEPSS rescore
  29. 2026-06-27 03:04 UTCEPSS rescore
  30. 2026-06-25 13:46 UTCEPSS rescore
  31. 2026-06-25 13:46 UTCEPSS rescore
  32. 2026-06-24 14:02 UTCEPSS rescore
  33. 2026-06-24 14:02 UTCEPSS rescore
  34. 2026-06-23 21:29 UTCEPSS rescore
  35. 2026-06-23 21:29 UTCEPSS rescore
  36. 2026-06-21 14:53 UTCEPSS rescore
  37. 2026-06-21 01:56 UTCEPSS rescore
  38. 2026-06-21 01:56 UTCEPSS rescore
  39. 2026-06-19 19:22 UTCEPSS rescore
  40. 2026-06-19 19:22 UTCEPSS rescore
  41. 2026-06-19 17:25 UTCOSV refresh
  42. 2026-06-18 17:49 UTCEPSS rescore
  43. 2026-06-18 17:49 UTCEPSS rescore
  44. 2026-06-17 17:49 UTCEPSS rescore
  45. 2026-06-17 17:49 UTCEPSS rescore
  46. 2026-06-16 17:49 UTCEPSS rescore
  47. 2026-06-16 17:49 UTCEPSS rescore
  48. 2026-06-16 17:49 UTCEPSS rescore
  49. 2026-06-15 17:44 UTCEPSS rescore
  50. 2026-06-13 22:57 UTCEPSS rescore
  51. 2026-06-12 23:08 UTCEPSS rescore
  52. 2026-06-10 22:14 UTCEPSS rescore
  53. 2026-06-10 13:17 UTCEPSS rescore
  54. 2026-06-07 15:21 UTCEPSS rescore
  55. 2026-06-06 13:44 UTCEPSS rescore
  56. 2026-06-06 13:44 UTCEPSS rescore
  57. 2026-06-05 22:44 UTCEPSS rescore
  58. 2026-06-05 22:44 UTCEPSS rescore
  59. 2026-06-05 06:07 UTCEPSS rescore
  60. 2026-06-04 13:09 UTCEPSS rescore
  61. 2026-06-04 13:09 UTCEPSS rescore
  62. 2026-06-04 13:09 UTCEPSS rescore
  63. 2026-06-02 20:10 UTCEPSS rescore
  64. 2026-06-02 20:10 UTCEPSS rescore
  65. 2026-06-01 13:49 UTCEPSS rescore
  66. 2026-06-01 13:49 UTCEPSS rescore
  67. 2026-06-01 13:49 UTCEPSS rescore
  68. 2026-05-31 22:28 UTCEPSS rescore
  69. 2026-05-31 22:28 UTCEPSS rescore
  70. 2026-05-31 00:13 UTCEPSS rescore
  71. 2026-05-31 00:13 UTCEPSS rescore
  72. 2026-05-30 23:06 UTCEG score recompute
  73. 2026-05-30 23:06 UTCGHSA enrichment
  74. 2026-05-29 13:40 UTCEPSS rescore
  75. 2026-05-28 13:42 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-31076✓ verified
    First seen Feb 4, 2008

    MPlayer 1.0rc2 - 'demux_mov.c' Remote Code Execution

    Open source ↗

Related CVEs(same product)

Frequently asked(4)

What is CVE-2008-0485?
CVE-2008-0485 is a high vulnerability published on February 5, 2008. Array index error in libmpdemux/demux_mov.c in MPlayer 1.0 rc2 and earlier might allow remote attackers to execute arbitrary code via a QuickTime MOV file with a crafted stsc atom tag.
When was CVE-2008-0485 disclosed?
CVE-2008-0485 was first published in the National Vulnerability Database on February 5, 2008, with the most recent update on April 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2008-0485 actively exploited?
CVE-2008-0485 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9% probability of exploitation in the next 30 days, which ranks it in the top 5.0% of all scored CVEs.
How do I remediate CVE-2008-0485?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2008-0485, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2008-0485

Explore →

Is Your Infrastructure Affected by CVE-2008-0485?

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

Book a Demo →Browse All CVEs