LiveActive security incident?Get immediate response
CVE Record

CVE-2011-2013: Integer overflow in the TCP/IP implementation in Microsoft Windows Vista SP2, Windows Server 2008 SP2, R2,...

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."

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

This is a critical Windows networking flaw in older Microsoft platforms. A remote attacker could send crafted UDP traffic to a closed port and potentially run code on the target system. The supplied bundle does not show active exploitation, but the impact is severe for any still-exposed legacy systems.

Executive priority

Treat this as high-priority legacy risk. The vulnerability is old, but any remaining affected systems represent severe remote-code-execution exposure and should be patched, isolated, or retired on an accelerated schedule.

Technical view

CVE-2011-2013 is an integer overflow in the Windows TCP/IP implementation, described as a reference counter overflow. A sequence of crafted UDP packets sent to a closed port may allow unauthenticated remote code execution on affected Windows Vista, Windows Server 2008, and Windows 7 versions.

Likely exposure

Exposure is most likely in legacy Windows Vista SP2, Windows Server 2008 SP2/R2/R2 SP1, and Windows 7 Gold/SP1 assets. Internet-facing or broadly reachable hosts are the primary concern, especially where UDP traffic can reach the system.

Exploitation context

The CVE record describes remote, unauthenticated arbitrary code execution through crafted UDP packets. The provided data says this CVE is not in KEV, and no cited source in the bundle confirms active exploitation.

Researcher notes

Evidence is sufficient for affected platform family, vulnerability class, impact, and vendor advisory linkage. The bundle does not provide exploit-in-the-wild evidence or detailed workaround text, so validation should rely on asset versioning, patch state, and vendor guidance.

Mitigation direction

  • Review Microsoft MS11-083 and apply the vendor security update or guidance.
  • Inventory affected legacy Windows versions across servers, workstations, and images.
  • Prioritize remediation for externally reachable or high-trust network systems.
  • Retire, isolate, or upgrade unsupported affected systems where patching is not viable.

Validation and detection

  • Confirm whether assets run the affected Windows versions listed in the CVE description.
  • Check patch status against Microsoft MS11-083 requirements.
  • Use the referenced OVAL definition for configuration or vulnerability scanning where supported.
  • Validate network exposure without sending crafted exploit traffic.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-190: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2011-2013 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2011-2013Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-190 · source CWE mapping

Integer Overflow or Wraparound

Integer Overflow or Wraparound represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.