CVE-2005-2224 microsoft asp.net: Infinite Loop
microsoft asp.net: no CVSS score yet. EPSS 18% estimated probability of exploitation activity in the next 30 days.
aspnet_wp.exe in Microsoft ASP.NET web services allows remote attackers to cause a denial of service (CPU consumption from infinite loop) via a crafted SOAP message to an RPC/Encoded method.
- EPSS
- 18% (unchanged from 18% a week ago; 18% 30 days ago) estimated probability of exploitation activity in the next 30 days; 97th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-835 Loop with Unreachable Exit Condition (Infinite Loop)
- Published
- Modified
- NVD analysis
- Analyzed, since modified
- Record from
- the NVD, synced
Fix and patched versions
- Vendor advisory: http://secunia.com/advisories/16005
- Vendor advisory: http://www.spidynamics.com/spilabs/advisories/aspRCP.html
Ask an AI about this CVE
Show the prompt
Explain CVE-2005-2224 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2005-2224?via=ask-ai-copy and https://cve.bz/cve/CVE-2005-2224?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2005-2224 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.