cbcvebase.
CVE-2006-1364
published 2006-03-23

CVE-2006-1364: Microsoft w3wp (aka w3wp.exe) does not properly handle when the AspCompat directive is not used when referencing COM components in ASP.NET, which allows remote…

PriorityP347high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EXPLOIT
EPSS
58.74%
99.0th percentile
Microsoft w3wp (aka w3wp.exe) does not properly handle when the AspCompat directive is not used when referencing COM components in ASP.NET, which allows remote attackers to cause a denial of service (resource consumption or crash) by repeatedly requesting each of several documents that refer to COM components, or are restricted documents located under the ASP.NET application path.

Affected

2 ranges
VendorProductVersion rangeFixed in
microsoftasp.net<= 1.1
microsoftasp.net

Detection & IOCsextracted from sources · hover to see the quote

processw3wp.exe
path/aspnet-app\web.config
path/aspnet-app\../aspnetlogs\log1.logs
  • Detect repeated HTTP GET requests using backslash path separators (e.g., /aspnet-app\...) targeting .aspx, web.config, and .logs files — a hallmark of this exploit's path traversal and COM-reference DoS pattern.
  • Alert on HTTP requests carrying the specific exploit User-Agent 'Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; .NET CLR 1.1.4322)' combined with Keep-Alive connections to port 80 in rapid succession.
  • Monitor for the presence of the hardcoded .ASPXAUTH cookie token value in HTTP requests, which the exploit injects to increase effectiveness against authenticated ASP.NET applications.
  • Detect resource exhaustion or crash of w3wp.exe triggered by repeated requests to ASP.NET pages referencing COM components without the AspCompat directive.
  • Flag HTTP GET requests targeting restricted paths under the ASP.NET application path (e.g., web.config, log files) using mixed forward/backslash separators indicative of path traversal attempts.
  • ·The exploit's target paths (e.g., /aspnet-app\com-ref-link1.aspx) are template placeholders; operators must substitute their actual ASP.NET application paths and COM-referencing page names when writing detection signatures.
  • ·The hardcoded ASP.NET_SessionId and .ASPXAUTH cookie values in the exploit are static samples; real-world attackers may substitute valid session tokens, so detection should not rely solely on these exact values.

CVSS provenance

nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.07.8HIGHAV:N/AC:L/Au:N/C:N/I:N/A:C
CVEs like this are exactly what “Exploited This Week” covers.

Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.