CVE-2008-0075
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 · uneditedUnspecified vulnerability in Microsoft Internet Information Services (IIS) 5.1 through 6.0 allows remote attackers to execute arbitrary code via crafted inputs to ASP pages.
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 confidenceMicrosoft IIS versions 5.1 through 6.0 contain an unspecified vulnerability in Active Server Pages (ASP) processing that allows remote attackers to execute arbitrary code via crafted inputs to ASP pages. This is a critical RCE vulnerability exploitable without authentication.
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= 6.0CVSS 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
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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 checksWork through these to decide whether this CVE applies to you.
-
Verify IIS is installed and determine its versionOpen Command Prompt and run: inetmgr (IIS Manager) or check the version via registry at HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\Parameters\MajorVersion, or run 'iisreset /status' and check the Windows version via winverAffected if The installed IIS version is 5.1, 5.0, or 6.0
-
Confirm Active Server Pages (ASP) is enabledOpen IIS Manager (inetmgr), navigate to the server, click 'ISAPI Filters' or check 'Web Service Extensions' to see if Active Server Pages is allowed or set to 'Allowed'Affected if ASP is installed and enabled as a Web Service Extension
-
Check for accessible .asp pagesInspect the web root directory (typically C:\inetpub\wwwroot\) and subdirectories for .asp files, or attempt to access known ASP pages via browser (e.g., http://localhost/page.asp)Affected if Any .asp files exist and are served by IIS
-
Verify IIS is running and accepting requestsOpen Services.msc and confirm 'World Wide Web Publishing Service' is running, or run 'net start' and look for 'World Wide Web Publishing Service'Affected if IIS is actively running and serving content
A system is affected if it runs IIS version 5.1, 5.0, or 6.0 with ASP enabled and accessible .asp pages, making remote code execution possible without authentication.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade IIS to version 7.0 or later; if upgrading is not feasible, apply Microsoft security patches and consider disabling ASP if not required, or implement network-level filtering to restrict access to IIS servers.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2008-0075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2008-0075 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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