Show filters
69 Total Results
Displaying 1-10 of 69
Sort by:
Attacker Value
Unknown

CVE-2011-5279

Disclosure Date: April 23, 2014 (last updated October 05, 2023)
CRLF injection vulnerability in the CGI implementation in Microsoft Internet Information Services (IIS) 4.x and 5.x on Windows NT and Windows 2000 allows remote attackers to modify arbitrary uppercase environment variables via a \n (newline) character in an HTTP header.
0
Attacker Value
Unknown

CVE-2009-4444

Disclosure Date: December 29, 2009 (last updated October 04, 2023)
Microsoft Internet Information Services (IIS) 5.x and 6.x uses only the portion of a filename before a ; (semicolon) character to determine the file extension, which allows remote attackers to bypass intended extension restrictions of third-party upload applications via a filename with a (1) .asp, (2) .cer, or (3) .asa first extension, followed by a semicolon and a safe extension, as demonstrated by the use of asp.dll to handle a .asp;.jpg file.
0
Attacker Value
Unknown

CVE-2009-1122

Disclosure Date: June 10, 2009 (last updated October 04, 2023)
The WebDAV extension in Microsoft Internet Information Services (IIS) 5.0 on Windows 2000 SP4 does not properly decode URLs, which allows remote attackers to bypass authentication, and possibly read or create files, via a crafted HTTP request, aka "IIS 5.0 WebDAV Authentication Bypass Vulnerability," a different vulnerability than CVE-2009-1535.
0
Attacker Value
Unknown

CVE-2003-1566

Disclosure Date: January 15, 2009 (last updated October 04, 2023)
Microsoft Internet Information Services (IIS) 5.0 does not log requests that use the TRACK method, which allows remote attackers to obtain sensitive information without detection.
0
Attacker Value
Unknown

CVE-2003-1567

Disclosure Date: January 15, 2009 (last updated October 04, 2023)
The undocumented TRACK method in Microsoft Internet Information Services (IIS) 5.0 returns the content of the original request in the body of the response, which makes it easier for remote attackers to steal cookies and authentication credentials, or bypass the HttpOnly protection mechanism, by using TRACK to read the contents of the HTTP headers that are returned in the response, a technique that is similar to cross-site tracing (XST) using HTTP TRACE.
0
Attacker Value
Unknown

CVE-2008-0074

Disclosure Date: February 12, 2008 (last updated October 04, 2023)
Unspecified vulnerability in Microsoft Internet Information Services (IIS) 5.0 through 7.0 allows local users to gain privileges via unknown vectors related to file change notifications in the TPRoot, NNTPFile\Root, or WWWRoot folders.
0
Attacker Value
Unknown

CVE-2007-2815

Disclosure Date: May 22, 2007 (last updated October 04, 2023)
The "hit-highlighting" functionality in webhits.dll in Microsoft Internet Information Services (IIS) Web Server 5.0 only uses Windows NT ACL configuration, which allows remote attackers to bypass NTLM and basic authentication mechanisms and access private web directories via the CiWebhitsfile parameter to null.htw.
0
Attacker Value
Unknown

CVE-2006-0026

Disclosure Date: July 11, 2006 (last updated October 04, 2023)
Buffer overflow in Microsoft Internet Information Services (IIS) 5.0, 5.1, and 6.0 allows local and possibly remote attackers to execute arbitrary code via crafted Active Server Pages (ASP).
0
Attacker Value
Unknown

CVE-2005-2678

Disclosure Date: August 23, 2005 (last updated February 22, 2025)
Microsoft IIS 5.1 and 6 allows remote attackers to spoof the SERVER_NAME variable to bypass security checks and conduct various attacks via a GET request with an http://localhost URI, which makes it appear as if the request is coming from localhost.
0
Attacker Value
Unknown

CVE-2005-2089

Disclosure Date: July 05, 2005 (last updated February 22, 2025)
Microsoft IIS 5.0 and 6.0 allows remote attackers to poison the web cache, bypass web application firewall protection, and conduct XSS attacks via an HTTP request with both a "Transfer-Encoding: chunked" header and a Content-Length header, which causes IIS to incorrectly handle and forward the body of the request in a way that causes the receiving server to process it as a separate HTTP request, aka "HTTP Request Smuggling."
0