CVE-2011-0042

HIGHNVD 7.87.9
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 7.9 because EPSS predicted 33% probability of exploitation within the next 30 days (98th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction (continuous uplift above 30%)
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated
7.9EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 33%CVSS: 7.8Exploit: No code on recordExposed services: Not assessed

No fix has been recorded since the CVE record was published in 2011 — if the vendor still supports the product, apply the fixed version it names; if not, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

SBE.dll in the Stream Buffer Engine in Windows Media Player and Windows Media Center in Microsoft Windows XP SP2 and SP3, Windows XP Media Center Edition 2005 SP3, Windows Vista SP1 and SP2, Windows 7 Gold and SP1, and Windows Media Center TV Pack for Windows Vista does not properly parse Digital Video Recording (.dvr-ms) files, which allows remote attackers to execute arbitrary code via a crafted file, aka "DVR-MS Vulnerability."

CVSS v3
7.8
EG Score
7.9HIGHhigh confidence
EG Risk
52
EG Risk 52/100

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 (value × EchelonGraph’s weight)
Severity79% × 45%
The EG Score, 7.9 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix has been recorded since the CVE record was published in 2011. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.
EPSS PROB
33%
EPSS %ILE
98th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix has been recorded since the CVE record was published in 2011. If the vendor still supports the product, apply the fixed version it names within your standard update timelines; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 9, 2011

Last Modified

April 29, 2026

Advisory Details (4)

Auto-updated May 2, 2026
No fix on record since 2011.
Web page

About Secunia Research | Flexera

http://secunia.com/advisories/43626
Web page

Microsoft Security Bulletin MS11-015 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2011/ms11-015
Web page

VUPEN Security - Vulnerability Research and Intelligence

http://www.vupen.com/english/advisories/2011/0615
Web page
http://www.securityfocus.com/bid/46680

Weakness Classification(1)

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

Data Freshness Timeline

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

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 75 of 79 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 25 repeat rows among the latest 100 are merged into the row they repeat. The 4 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 01:45 UTCEG score recompute
  2. 2026-10-11 13:38 UTCEPSS rescoreEPSS 33% · 98th percentile
  3. 2026-10-10 19:54 UTCEPSS rescoreEPSS 33% · 98th percentile
  4. 2026-10-09 20:00 UTCEPSS rescoreEPSS 33% · 98th percentile
  5. 2026-10-08 16:34 UTCEPSS rescoreEPSS 33% · 98th percentile
  6. 2026-10-07 23:38 UTCEPSS rescoreEPSS 33% · 98th percentile
  7. 2026-10-06 15:10 UTCEPSS rescoreEPSS 33% · 98th percentile
  8. 2026-09-30 14:58 UTCEPSS rescoreEPSS 33% · 98th percentile
  9. 2026-09-29 08:13 UTCEG score recompute
  10. 2026-09-26 15:52 UTCEPSS rescoreEPSS 33% · 98th percentile
  11. 2026-09-24 13:57 UTCEPSS rescoreEPSS 33% · 98th percentile
  12. 2026-09-16 13:58 UTCEPSS rescoreEPSS 33% · 98th percentile
  13. 2026-09-15 03:04 UTCEPSS rescoreEPSS 33% · 98th percentile
  14. 2026-09-12 14:54 UTCEPSS rescoreEPSS 33% · 98th percentile
  15. 2026-09-06 13:41 UTCEPSS rescoreEPSS 33% · 98th percentile
  16. 2026-09-05 15:22 UTCEPSS rescoreEPSS 33% · 98th percentile
  17. 2026-09-04 13:55 UTCEPSS rescoreEPSS 33% · 98th percentile
  18. 2026-08-25 13:43 UTCEPSS rescoreEPSS 33% · 98th percentile
  19. 2026-08-19 16:58 UTCEPSS rescoreEPSS 33% · 98th percentile
  20. 2026-08-18 13:42 UTCEPSS rescoreEPSS 33% · 98th percentile
  21. 2026-08-15 01:25 UTCEPSS rescoreEPSS 33% · 98th percentile
  22. 2026-08-08 16:31 UTCEPSS rescoreEPSS 33% · 98th percentile
  23. 2026-08-06 13:41 UTCEPSS rescoreEPSS 33% · 98th percentile
  24. 2026-08-05 19:12 UTCEPSS rescoreEPSS 33% · 98th percentile
  25. 2026-08-04 15:04 UTCEPSS rescoreEPSS 33% · 98th percentile
Show 50 more
  1. 2026-08-01 04:10 UTCEPSS rescoreEPSS 33% · 98th percentile
  2. 2026-07-30 01:26 UTCEPSS rescoreEPSS 33% · 98th percentile
  3. 2026-07-23 14:14 UTCEPSS rescoreEPSS 33% · 98th percentile
  4. 2026-07-23 01:04 UTCEG score recompute
  5. 2026-07-23 00:39 UTCEG score recompute
  6. 2026-07-23 00:07 UTCEG score recompute▲ 0.10
  7. 2026-07-22 21:46 UTCEG score recompute
  8. 2026-07-22 14:03 UTCEPSS rescoreEPSS 33% · 98th percentile
  9. 2026-07-20 17:03 UTCEPSS rescoreEPSS 33% · 98th percentile
  10. 2026-07-19 02:25 UTCEPSS rescoreEPSS 33% · 98th percentile
  11. 2026-07-18 10:00 UTCEPSS rescoreEPSS 33% · 98th percentile
  12. 2026-07-16 16:58 UTCEPSS rescoreEPSS 33% · 98th percentile
  13. 2026-07-15 16:54 UTCEPSS rescoreEPSS 33% · 98th percentile
  14. 2026-07-15 01:55 UTCEPSS rescoreEPSS 33% · 98th percentile
  15. 2026-07-13 22:25 UTCEPSS rescoreEPSS 33% · 98th percentile
  16. 2026-07-13 06:08 UTCEPSS rescoreEPSS 33% · 98th percentile
  17. 2026-07-11 08:22 UTCEPSS rescoreEPSS 33% · 98th percentile
  18. 2026-07-08 15:10 UTCEPSS rescoreEPSS 33% · 98th percentile
  19. 2026-07-06 16:23 UTCEPSS rescoreEPSS 33% · 98th percentile
  20. 2026-07-05 02:26 UTCEPSS rescoreEPSS 33% · 98th percentile
  21. 2026-07-02 14:01 UTCEPSS rescoreEPSS 33% · 98th percentile
  22. 2026-07-01 15:02 UTCEPSS rescoreEPSS 33% · 98th percentile
  23. 2026-06-28 04:52 UTCEPSS rescoreEPSS 33% · 98th percentile
  24. 2026-06-27 03:05 UTCEPSS rescoreEPSS 33% · 98th percentile
  25. 2026-06-25 13:46 UTCEPSS rescoreEPSS 33% · 98th percentile
  26. 2026-06-24 14:02 UTCEPSS rescoreEPSS 33% · 98th percentile
  27. 2026-06-23 21:30 UTCEPSS rescoreEPSS 33% · 98th percentile
  28. 2026-06-21 01:56 UTCEPSS rescoreEPSS 33% · 98th percentile
  29. 2026-06-18 17:49 UTCEPSS rescoreEPSS 33% · 98th percentile
  30. 2026-06-17 17:49 UTCEPSS rescoreEPSS 33% · 98th percentile
  31. 2026-06-16 17:49 UTCEPSS rescoreEPSS 33% · 98th percentile
  32. 2026-06-15 17:44 UTCEPSS rescoreEPSS 33% · 98th percentile
  33. 2026-06-14 23:14 UTCEPSS rescoreEPSS 63% · 98th percentile
  34. 2026-06-13 22:57 UTCEPSS rescoreEPSS 63% · 98th percentile
  35. 2026-06-12 23:08 UTCEPSS rescoreEPSS 63% · 98th percentile
  36. 2026-06-11 13:56 UTCEPSS rescoreEPSS 63% · 98th percentile
  37. 2026-06-10 22:14 UTCEPSS rescoreEPSS 63% · 98th percentile
  38. 2026-06-10 13:17 UTCEPSS rescoreEPSS 63% · 98th percentile
  39. 2026-06-08 14:14 UTCEPSS rescoreEPSS 63% · 98th percentile
  40. 2026-06-06 13:44 UTCEPSS rescoreEPSS 63% · 98th percentile
  41. 2026-06-05 22:44 UTCEPSS rescoreEPSS 63% · 98th percentile
  42. 2026-06-05 06:07 UTCEPSS rescoreEPSS 63% · 98th percentile
  43. 2026-06-04 13:09 UTCEPSS rescoreEPSS 63% · 98th percentile
  44. 2026-06-02 20:10 UTCEPSS rescoreEPSS 63% · 98th percentile
  45. 2026-06-01 13:49 UTCEPSS rescoreEPSS 63% · 98th percentile
  46. 2026-05-29 13:40 UTCEPSS rescoreEPSS 63% · 98th percentile
  47. 2026-05-29 08:33 UTCEG score recompute
  48. 2026-05-29 08:33 UTCGHSA enrichmentGHSA-hvf6-hpg3-c749 · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-05-22 21:15 UTCEPSS rescoreEPSS 63% · 98th percentile
  50. 2026-05-20 22:37 UTCEPSS rescoreEPSS 63% · 98th percentile

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2011-0042?
CVE-2011-0042 is a high-severity vulnerability; its CVE record was published on March 9, 2011. SBE.dll in the Stream Buffer Engine in Windows Media Player and Windows Media Center in Microsoft Windows XP SP2 and SP3, Windows XP Media Center Edition 2005 SP3, Windows Vista SP1 and SP2, Windows 7 Gold and SP1, and Windows Media Center TV Pack for Windows Vista does not properly parse Digital…
When was CVE-2011-0042 made public?
CVE-2011-0042 was made public on March 8, 2011: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on March 9, 2011. EchelonGraph's copy of the record carries a last-modified date of April 29, 2026; the record at its source may have been updated since.
Is CVE-2011-0042 actively exploited?
CVE-2011-0042 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 33% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2011-0042?
CVE-2011-0042 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.9 (HIGH).
How do I remediate CVE-2011-0042?
No fix for CVE-2011-0042 has been recorded since its CVE record was published in 2011. If the vendor still supports the product, apply the fixed version it names; if it no longer does, isolate the affected system (restrict network access to it, for example with a firewall, or keep it off the internet) or retire the product.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2011-0042

Explore →

Is Your Infrastructure Affected by CVE-2011-0042?

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

Book a Demo →Browse All CVEs