Microsoft .NET Framework 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine TCP connection…
No fixed version listed yet.Check the vendor advisory. References ↓
The flaw is in Microsoft .NET Framework (versions 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1), where the framework does not properly determine TCP connection states, specifically within the ASP.NET component. An remote attacker can send crafted HTTP requests that exploit stale or closed connections to cause a denial of service by hanging the ASP.NET daemon through persistent resource consumption, requiring only network access to the affected server with no authentication or user interaction indicated.
Official description · CVE.org
Microsoft .NET Framework 1.1 SP1, 2.0 SP2, 3.5, 3.5.1, 4, 4.5, and 4.5.1 does not properly determine TCP connection states, which allows remote attackers to cause a denial of service (ASP.NET daemon hang) via crafted HTTP requests that trigger persistent resource consumption for a (1) stale or (2) closed connection, as exploited in the wild in February 2014, aka "POST Request DoS Vulnerability."
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 1 day before it was disclosed.
- First seen exploitedVulnCheck KEV evidence1 day before
- Disclosedday 0
What security researchers reported
Not named in any threat report yetAlso mentioned in 1 community threat pulse (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.