CVE-2002-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 · uneditedCross-site scripting vulnerability for Internet Information Server (IIS) 4.0, 5.0 and 5.1 allows remote attackers to execute arbitrary script as other web users via the error message used in a URL redirect (""302 Object Moved") message.
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 IIS 4.0, 5.0, and 5.1 where the '302 Object Moved' redirect error message does not properly sanitize user-supplied input, allowing remote attackers to inject arbitrary script that executes in the context of other web users' sessions.
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.
-
Identify if IIS is installedCheck for IIS by reviewing installed programs, or check for inetinfo.exe process running, or check the Windows Services list for 'IIS Admin Service' or 'World Wide Web Publishing Service'Affected if IIS is not installed on the system - if IIS is present, continue to version check
-
Determine IIS versionCheck the IIS version by reviewing the inetinfo.exe file properties (right-click inetinfo.exe in systemroot\System32), or check the registry key HKLM\SOFTWARE\Microsoft\InetStp\VersionStringAffected if The installed version is 4.0 or 5.0 - these versions are explicitly listed as affected in the CVE
-
Confirm Web service is enabledCheck if the World Wide Web Publishing Service is running, or attempt to access a local HTTP endpoint on port 80 to confirm IIS is responding to requestsAffected if The vulnerability only applies when IIS is actively serving HTTP requests - if the web service is disabled, the attack surface may not be exposed
-
Check if custom error pages or redirects are in useReview IIS configuration for custom 302 redirect handlers or ISAPI filters that may process redirect responses - check the IIS metabase or application configuration for redirect-related mappingsAffected if The vulnerability manifests through the 302 Object Moved redirect mechanism - custom error handling configurations may alter the exposure level
A system is affected if it is running IIS version 4.0 or 5.0 with the web service enabled and serving HTTP requests, as the 302 redirect error handling in these versions does not sanitize user-supplied input.
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 dataApply Microsoft security patches for this CVE, or upgrade to a supported IIS version. Implement input validation and output encoding on redirect error responses to prevent script injection.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-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-2002-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