CVE-2001-0902
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 · uneditedMicrosoft IIS 5.0 allows remote attackers to spoof web log entries via an HTTP request that includes hex-encoded newline or form-feed characters.
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 confidenceThis vulnerability allows remote attackers to inject fraudulent entries into Microsoft IIS 5.0 web server logs by sending HTTP requests containing hex-encoded newline (%0A) or form-feed (%0C) characters. This log spoofing could obscure malicious activity, hide attack traces, or mislead forensic investigations.
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= 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 run 'tasklist /FI "IMAGENAME eq inetinfo.exe"' in command promptAffected if IIS is installed and running as inetinfo.exe
-
Identify the exact IIS versionCheck the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\InetStp or run 'iisweb.vbs /query' if available, or view the About dialog in IIS ManagerAffected if The version reported is 5.0.x (any minor build of version 5.0)
-
Verify web service is enabledCheck if Default Web Site or any website is started in IIS Manager, or run 'net start' and look for 'World Wide Web Publishing Service'Affected if A website is actively running and accepting HTTP requests
-
Confirm HTTP logging is enabledOpen IIS Manager, right-click the website, select Properties, and verify 'Enable logging' is checked. Log files are typically in C:\WINDOWS\System32\LogFilesAffected if HTTP logging is enabled - without logging, the spoofing cannot occur but the vulnerability still exists in the software
The environment is affected if Microsoft IIS version 5.0 is running as a web server, regardless of logging status, since the vulnerable code path is present in the IIS 5.0 implementation.
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 dataSince IIS 5.0 is obsolete and no longer supported, upgrade to a currently supported IIS version (6.0 or later) and apply all cumulative security updates. Additionally, implement log integrity monitoring to detect anomalies.
- Consultation1.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,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2001-0902 — 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-2001-0902 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