CVE-2011-0657

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

Score 9.8 from GitHub Security Advisory (severity: HIGH) published 2022-05-13. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekWeaponized
9.8EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High exploitation likelihood — EPSS 62%
  • Public exploit code is available (Metasploit)
CISA-KEV: Not listedEPSS PROB: 62%CVSS: 9.8Exploit: MetasploitExposed 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.

DNSAPI.dll in the DNS client in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 does not properly process DNS queries, which allows remote attackers to execute arbitrary code via (1) a crafted LLMNR broadcast query or (2) a crafted application, aka "DNS Query Vulnerability."

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
85
EG Risk 85/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)
Severity98% × 45%
The EG Score, 9.8 of 10.
Exploitation65% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 2 (Weaponized): a constant, not a probability.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high; 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
62%
EPSS %ILE
99th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend 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 at low or medium mission impact and sooner than that at high; 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 yes (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)3 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (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

April 13, 2011

Last Modified

April 29, 2026

Advisory Details (5)

Auto-updated Oct 8, 2026
No fix on record since 2011.
Web page

Secunia Research & Vulnerability Insights | Flexera

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

Microsoft Security Bulletin MS11-030 - Critical | Microsoft Learn

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

VUPEN Security - Vulnerability Research and Intelligence

http://www.vupen.com/english/advisories/2011/0948
Web page

CVE-2011-0657 - PSIRT.COM

http://www.securityfocus.com/bid/47242
Web page
http://www.securitytracker.com/id?1025332

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 20× 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 74 of 95 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. 26 repeat rows among the latest 100 are merged into the row they repeat. The 21 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 Metasploit module). 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 it no longer does, isolate the affected system or retire the product.

  • Metasploitauxiliary/dos/windows/llmnr/ms11_030_dnsapi✓ verified
    Published Jun 27, 2011

    Microsoft Windows DNSAPI.dll LLMNR Buffer Underrun DoS

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2011-0657?
CVE-2011-0657 is a critical-severity vulnerability; its CVE record was published on April 13, 2011. DNSAPI.dll in the DNS client in Microsoft Windows XP SP2 and SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 Gold, SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 does not properly process DNS queries, which allows remote attackers to execute arbitrary code via (1) a…
When was CVE-2011-0657 made public?
CVE-2011-0657 was made public on April 12, 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 April 13, 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-0657 actively exploited?
CVE-2011-0657 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model places it in Tier 2 (Weaponized), which is not evidence of exploitation: a Metasploit module exists for it. EchelonGraph does not test whether exploit code works. FIRST EPSS estimates a 62% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2011-0657?
CVE-2011-0657 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2011-0657?
No fix for CVE-2011-0657 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-0657

Explore →

Is Your Infrastructure Affected by CVE-2011-0657?

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

Book a Demo →Browse All CVEs