dbcve.org
Internet Information ServicesApplication · Microsoft

CVE-2001-0151

MEDIUM · 5.0 CVSS v2.0 Published 2001-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
High EPSS Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
IIS 5.0 allows remote attackers to cause a denial of service via a series of malformed WebDAV requests.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

IIS 5.0 contains a denial of service vulnerability where processing a series of malformed WebDAV (Web-based Distributed Authoring and Versioning) requests causes the web server to become unresponsive or crash, preventing legitimate access.

MitigationDisable WebDAV if not required, or deploy a WAF/filter to block malformed WebDAV requests. Consider upgrading from IIS 5.0 as it is end-of-life.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Internet Information ServicesApplication
Affected:= 5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
None
Integrity
None
Availability
Partial

AV:N/AC:L/Au:N/C:N/I:N/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm IIS is installed
    Check if Microsoft Internet Information Services is running on the system. On Windows, open IIS Manager (inetmgr) or check the Windows Services list for 'IIS Admin Service' or 'World Wide Web Publishing Service'.
    Affected if IIS is not present on the system, then not affected by this CVE.
  2. Identify the IIS version
    Run 'inetmgr' to open IIS Manager and check the version, or check the file version of %SystemRoot%\System32\inetsrv\inetinfo.exe. For IIS 5.0, the version should be 5.0.
    Affected if The installed version is not exactly 5.0, then not affected by this CVE.
  3. Check if WebDAV is enabled
    In IIS Manager, expand the server node, right-click on the website (typically Default Web Site), select Properties, then go to the 'Home Directory' tab and check for WebDAV authoring rules or check the WebDAV authoring permissions. Alternatively, check if the WebDAV module is loaded in IIS.
    Affected if WebDAV is explicitly enabled and accessible to remote attackers, then the system may be affected by this CVE.

The system is affected only if it is running exactly IIS version 5.0 with WebDAV enabled and accessible to process incoming WebDAV requests.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable WebDAV if not required, or deploy a WAF/filter to block malformed WebDAV requests. Consider upgrading from IIS 5.0 as it is end-of-life.

Fix this in Internet Information Services Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2001-0151 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2001-0151 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data