CVE-2009-1536 json
ASP.NET in Microsoft .NET Framework 2.0 SP1 and SP2 and 3.5 Gold and SP1, when ASP 2.0 is used in integrated mode on IIS 7.0, does not prop…
published 2009-08-12 17 y ago modified 2026-06-16 4 mo ago also EUVD-2009-1532
- cvss
- 2.6
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 51.3%
- EPSS 51.3% chance of exploitation in 30 days, percentile 98%
- public exploits
- 0
- none known
Summary
ASP.NET in Microsoft .NET Framework 2.0 SP1 and SP2 and 3.5 Gold and SP1, when ASP 2.0 is used in integrated mode on IIS 7.0, does not properly manage request scheduling, which allows remote attackers to cause a denial of service (daemon outage) via a series of crafted HTTP requests, aka "Remote Unauthenticated Denial of Service in ASP.NET Vulnerability."
Patch / fix
- securityfocus.com/bid/35985 advisory
Exploit prediction
51.32% chance of exploitation in the next 30 days, higher than 98% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 2.6 | AV:N/AC:H/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-20 Improper Input Validation
References
-
securityfocus.com
/bid/35985
vdb-entry, patch, third-party-advisory
-
docs.microsoft.com
/en-us/security-updates/securitybulletins/2009/ms09-036
vendor-advisory
-
blogs.technet.com
/srd/archive/2009/08/11/ms09-035-asp-net-denial-of-service-vulnerability.aspx
vendor-advisory
-
oval.cisecurity.org
/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6393
vdb-entry, signature, third-party-advisory
-
us-cert.gov
/cas/techalerts/TA09-223A.html
third-party-advisory, us-government-resource
-
vupen.com
/english/advisories/2009/2231
vdb-entry, permissions-required, third-party-advisory
-
secunia.com
/advisories/36127
third-party-advisory
-
securitytracker.com
/id?1022715
vdb-entry, third-party-advisory
-
osvdb.org
/56905
vdb-entry, broken-link
Sources
- CVE List CVE-2009-1536
- NVD CVE-2009-1536
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.