CVE-2002-1745
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 · uneditedOff-by-one error in the CodeBrws.asp sample script in Microsoft IIS 5.0 allows remote attackers to view the source code for files with extensions containing with one additional character after .html, .htm, .asp, or .inc, such as .aspx files.
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 confidenceOff-by-one error in the CodeBrws.asp sample script in Microsoft IIS 5.0 allows remote attackers to bypass extension filtering and view source code for files by adding one character to common extensions (.html, .htm, .asp, .inc become .htmlx, .htmx, .aspx, .incx, etc.). This exposes sensitive server-side code and configuration information.
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
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 5.0 is installedCheck the IIS version by running 'iisweb.vbs /query' or checking the IIS metabase via IIS Manager, or run 'inetmgr' and look at the server propertiesAffected if IIS version 5.0 is installed and running
-
Locate the CodeBrws.asp scriptSearch the web root directories (typically C:\Inetpub\wwwroot\) and all subdirectories for a file named 'CodeBrws.asp'Affected if The CodeBrws.asp file exists on the server
-
Verify the script is accessible via HTTPAttempt to access the script over HTTP (e.g., GET http://yourserver/scripts/CodeBrws.asp or in any sample scripts directory)Affected if The CodeBrws.asp script responds to HTTP requests (returns 200 OK rather than 404)
-
Test extension bypass vulnerabilityRequest a known file with a modified extension: append 'x' to common extensions (e.g., request /test.htmlx, /test.htmx, /test.aspx, /test.incx) and see if source code is returned instead of being processed or blockedAffected if Files with modified extensions (like .htmlx, .aspx) return their source code instead of being filtered or executed
A server is affected if it runs IIS 5.0, has the CodeBrws.asp sample script present and accessible, and the extension-filtering bypass successfully exposes source code for files with modified extensions.
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 dataRemove or disable the CodeBrws.asp sample script from IIS production servers, and remove all sample scripts from production environments.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-1745 — 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-1745 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