CVE-2002-0148
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 · uneditedCross-site scripting vulnerability in Internet Information Server (IIS) 4.0, 5.0 and 5.1 allows remote attackers to execute arbitrary script as other users via an HTTP error page.
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 confidenceCross-site scripting vulnerability in Internet Information Server (IIS) versions 4.0, 5.0, and 5.1 allows remote attackers to inject arbitrary script into HTTP error pages. When users encounter these malicious error pages, the injected script executes in their browser context, potentially stealing session cookies or performing actions on behalf of the user.
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= 4.0= 5.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm IIS is installed and runningOpen Services (services.msc) and look for 'IIS Admin Service' or 'World Wide Web Publishing Service', or run 'iisreset /status' from an elevated command promptAffected if IIS service is running and serving web content
-
Identify the installed IIS versionRun 'iisreset /?' or check the version in the IIS snap-in (inetmgr), or look in HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp in the Windows registryAffected if Version is 4.0, 5.0, or 5.1
-
Verify the server returns HTTP error pagesTrigger an error by requesting a non-existent page (http://yourserver/nonexistent123.html) or a malformed request and observe the responseAffected if The server returns a default IIS error page rather than a custom application-level error page
-
Check if custom error handling is enabledIn IIS Manager, select the website, open 'Error Pages' feature, or check the web.config file for customErrors element, or examine the <httpErrors> configuration in applicationHost.configAffected if Default IIS error pages are being served (custom error handling is not configured)
You are affected if IIS version 4.0, 5.0, or 5.1 is running and serving default IIS error pages to clients, allowing injected script to execute in users' browsers.
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 from legacy IIS 4.0/5.0/5.1 to a supported IIS version (IIS 10.0 on Windows Server 2016 or later) as these older versions are no longer supported and contain multiple unpatched vulnerabilities. If upgrade is not immediately feasible, apply all available Microsoft security patches and consider implementing web application firewall rules to filter malicious error page requests.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.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 $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0148 — 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-2002-0148 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