CVE-2011-2013

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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, ghsa, nvd
Weaponized
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 34%CVSS: 9.8Exploit: NoneExposed: 0

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

Integer overflow in the TCP/IP implementation in Microsoft Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 allows remote attackers to execute arbitrary code by sending a sequence of crafted UDP packets to a closed port, aka "Reference Counter Overflow Vulnerability."

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
98.2%
KEV
Not listed

Published

November 8, 2011

Last Modified

April 29, 2026

Advisory Details (1)

Auto-updated May 10, 2026
No patch confirmed yet.
generic

Microsoft Security Bulletin MS11-083 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2011/ms11-083

Data Freshness Timeline

(refreshed 8× in last 7d / 34× 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-06 16:23 UTCEPSS rescore
  2. 2026-07-05 02:26 UTCEPSS rescore
  3. 2026-07-04 06:27 UTCEPSS rescore
  4. 2026-07-02 14:01 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-07-01 15:02 UTCEPSS rescore
  7. 2026-06-30 23:19 UTCEPSS rescore
  8. 2026-06-30 23:19 UTCEPSS rescore
  9. 2026-06-28 04:53 UTCEPSS rescore
  10. 2026-06-28 04:52 UTCEPSS rescore
  11. 2026-06-27 03:05 UTCEPSS rescore
  12. 2026-06-27 03:05 UTCEPSS rescore
  13. 2026-06-25 13:46 UTCEPSS rescore
  14. 2026-06-24 14:02 UTCEPSS rescore
  15. 2026-06-24 14:02 UTCEPSS rescore
  16. 2026-06-23 21:30 UTCEPSS rescore
  17. 2026-06-23 21:30 UTCEPSS rescore
  18. 2026-06-21 01:56 UTCEPSS rescore
  19. 2026-06-21 01:56 UTCEPSS rescore
  20. 2026-06-19 19:22 UTCEPSS rescore
  21. 2026-06-19 19:22 UTCEPSS rescore
  22. 2026-06-18 17:49 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-17 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 62 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-15 17:44 UTCEPSS rescore
  4. 2026-06-12 23:08 UTCEPSS rescore
  5. 2026-06-11 13:56 UTCEPSS rescore
  6. 2026-06-10 22:14 UTCEPSS rescore
  7. 2026-06-10 13:17 UTCEPSS rescore
  8. 2026-06-08 14:14 UTCEPSS rescore
  9. 2026-06-08 14:14 UTCEPSS rescore
  10. 2026-06-07 15:22 UTCEPSS rescore
  11. 2026-06-07 15:22 UTCEPSS rescore
  12. 2026-06-06 13:45 UTCEPSS rescore
  13. 2026-06-06 13:44 UTCEPSS rescore
  14. 2026-06-05 22:44 UTCEPSS rescore
  15. 2026-06-05 06:08 UTCEPSS rescore
  16. 2026-06-05 06:07 UTCEPSS rescore
  17. 2026-06-04 13:09 UTCEPSS rescore
  18. 2026-06-04 13:09 UTCEPSS rescore
  19. 2026-06-02 20:10 UTCEPSS rescore
  20. 2026-06-02 20:10 UTCEPSS rescore
  21. 2026-05-31 22:28 UTCEPSS rescore
  22. 2026-05-31 22:28 UTCEPSS rescore
  23. 2026-05-31 00:14 UTCEPSS rescore
  24. 2026-05-31 00:14 UTCEPSS rescore
  25. 2026-05-29 13:41 UTCEPSS rescore
  26. 2026-05-29 13:40 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-28 13:42 UTCEPSS rescore
  29. 2026-05-28 13:42 UTCEPSS rescore
  30. 2026-05-27 13:38 UTCEPSS rescore
  31. 2026-05-27 13:38 UTCEPSS rescore
  32. 2026-05-26 07:16 UTCEPSS rescore
  33. 2026-05-26 07:16 UTCEPSS rescore
  34. 2026-05-22 21:15 UTCEPSS rescore
  35. 2026-05-22 21:15 UTCEPSS rescore
  36. 2026-05-22 21:15 UTCEPSS rescore
  37. 2026-05-20 22:37 UTCEPSS rescore
  38. 2026-05-20 22:37 UTCEPSS rescore
  39. 2026-05-20 22:37 UTCEPSS rescore
  40. 2026-05-20 11:21 UTCEPSS rescore
  41. 2026-05-20 11:21 UTCEPSS rescore
  42. 2026-05-20 11:21 UTCEPSS rescore
  43. 2026-05-20 10:17 UTCEG score recompute
  44. 2026-05-20 10:17 UTCGHSA enrichment
  45. 2026-05-20 06:10 UTCEG score recompute
  46. 2026-05-20 06:10 UTCGHSA enrichment
  47. 2026-05-20 02:02 UTCEG score recompute
  48. 2026-05-20 02:02 UTCGHSA enrichment
  49. 2026-05-19 21:55 UTCEG score recompute
  50. 2026-05-19 21:55 UTCGHSA enrichment
  51. 2026-05-19 17:48 UTCEG score recompute
  52. 2026-05-19 17:48 UTCGHSA enrichment
  53. 2026-05-19 13:41 UTCEG score recompute
  54. 2026-05-19 13:41 UTCGHSA enrichment
  55. 2026-05-19 09:33 UTCEG score recompute
  56. 2026-05-19 09:32 UTCGHSA enrichment
  57. 2026-05-19 05:25 UTCEG score recompute
  58. 2026-05-19 05:25 UTCGHSA enrichment
  59. 2026-05-19 01:18 UTCEG score recompute
  60. 2026-05-19 01:18 UTCGHSA enrichment
  61. 2026-05-18 21:29 UTCEPSS rescore
  62. 2026-05-18 21:29 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-36285✓ verified
    First seen Nov 8, 2011

    Microsoft Windows - TCP/IP Stack Reference Counter Integer Overflow (MS11-083)

    Open source ↗

Frequently asked(5)

What is CVE-2011-2013?
CVE-2011-2013 is a critical vulnerability published on November 8, 2011. Integer overflow in the TCP/IP implementation in Microsoft Windows Vista SP2, Windows Server 2008 SP2, R2, and R2 SP1, and Windows 7 Gold and SP1 allows remote attackers to execute arbitrary code by sending a sequence of crafted UDP packets to a closed port, aka "Reference Counter Overflow…
When was CVE-2011-2013 disclosed?
CVE-2011-2013 was first published in the National Vulnerability Database on November 8, 2011, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2011-2013 actively exploited?
CVE-2011-2013 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2011-2013?
CVE-2011-2013 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2011-2013?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2011-2013, 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-2011-2013

Explore →

Is Your Infrastructure Affected by CVE-2011-2013?

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

Start Free Scan →Browse All CVEs