dbcve.org
Internet Information ServerApplication · Microsoft

CVE-2007-2897

HIGH · 7.5 CVSS v2.0 Published 2007-05-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Microsoft Internet Information Services (IIS) 6.0 allows remote attackers to cause a denial of service (server instability or device hang), and possibly obtain sensitive information (device communication traffic); and might allow attackers with physical access to execute arbitrary code after connecting a data stream to a device COM port; via requests for a URI containing a '/' immediately before and after the name of a DOS device, as demonstrated by the /AUX/.aspx URI, which bypasses a blacklist for DOS device 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 · high confidence

IIS 6.0 contains a vulnerability where specially crafted URI requests containing a DOS device name (like /AUX/) wrapped in slashes bypass blacklist filtering, allowing remote attackers to cause denial of service and potentially access sensitive device communication traffic. The /AUX/.aspx proof-of-concept demonstrates how the blacklist for DOS device names can be circumvented.

MitigationApply Microsoft security updates for IIS 6.0 and implement URL request filtering to properly block or sanitize requests containing DOS device names (AUX, CON, PRN, etc.) regardless of surrounding slashes.

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 ServerApplication
Affected:= 6.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
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/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. Identify IIS version
    Check if the server is running Microsoft Internet Information Server (IIS) 6.0. On the server, open IIS Manager, or run 'inetmgr' from command prompt, or check the version via registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters' or by viewing the 'Version' property of the IIS service.
    Affected if The installed version is exactly IIS 6.0.
  2. Confirm URL filtering is enabled
    Check if URLScan or built-in Request Filtering is installed and enabled for the affected website. In IIS Manager, select the website, then look for 'Request Filtering' icon under the 'IIS' section. Verify the feature is enabled and not disabled.
    Affected if URL filtering is disabled or not configured.
  3. Verify DOS device name blocking
    Inspect the URL filtering rules or URLScan.ini configuration to confirm whether DOS device names (AUX, CON, PRN, NUL, COM1-9, LPT1-9, etc.) are explicitly blocked in all URI patterns, including those wrapped in slashes like /AUX/ or /CON/.
    Affected if The blacklist does not block DOS device names regardless of surrounding characters or slashes.
  4. Test for bypass vulnerability
    Send a test HTTP request to the server with a URI containing a DOS device name wrapped in slashes, such as 'GET /AUX/.aspx' or 'GET /CON/test.html'. Use a tool like curl or a browser to make the request and observe whether the request is rejected or allowed.
    Affected if The request with /AUX/.aspx or similar DOS device name patterns is processed by the server instead of being blocked.

If the environment runs IIS 6.0 without proper URL filtering that blocks DOS device names in all URI patterns including those with surrounding slashes, the system is vulnerable to CVE-2007-2897.

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

Apply Microsoft security updates for IIS 6.0 and implement URL request filtering to properly block or sanitize requests containing DOS device names (AUX, CON, PRN, etc.) regardless of surrounding slashes.

Fix this in Internet Information Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-2897 — 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-2007-2897 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