CVE-2000-0161
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 · uneditedSample web sites on Microsoft Site Server 3.0 Commerce Edition do not validate an identification number, which allows remote attackers to execute SQL commands.
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 confidenceMicrosoft Site Server 3.0 Commerce Edition ships with sample web pages that fail to validate an identification number parameter before incorporating it into SQL queries, enabling remote attackers to inject and execute arbitrary SQL commands via SQL injection.
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= 3.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.
-
Verify Microsoft Site Server 3.0 installationCheck for Microsoft Site Server 3.0 Commerce Edition installation by reviewing installed programs or checking the server for Site Server components. On Windows servers, check Add/Remove Programs or review IIS sites for Site Server administration tools.Affected if Microsoft Site Server 3.0 Commerce Edition is installed on the server
-
Locate sample web application filesSearch the web root directories (typically C:\Inetpub\ or IIS site directories) for sample commerce pages. Look for directories containing sample e-commerce pages, commonly found in paths like /samples/commerce/ or similar documentation-provided example directories.Affected if Sample commerce application directories and ASP files from the Site Server installation remain on the server
-
Check if sample applications are accessibleReview IIS configuration or attempt to access known sample page URLs if they exist. Check the web server configuration for any mappings or virtual directories pointing to Site Server sample applications.Affected if Sample web pages are accessible via HTTP/HTTPS from the web server
-
Inspect parameter handling in sample pagesIf sample pages are found, examine the ASP source code for any page that accepts an identification number parameter and uses it in SQL queries without visible input validation. Look for query patterns like 'SELECT * FROM table WHERE ID = ' + request("id").Affected if Sample pages contain SQL queries that incorporate request parameters without validation routines
-
Review web application authentication and exposureDetermine if these sample pages are protected by authentication or accessible to unauthenticated users. Check IIS authentication settings and NTFS permissions on the sample directories.Affected if Sample commerce pages are accessible to unauthenticated or anonymous web users
A server is affected if Microsoft Site Server 3.0 Commerce Edition is installed AND the vulnerable sample web application pages with unvalidated ID parameters are present and accessible on the network.
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 dataDisable or remove the vulnerable sample web applications, apply any available Microsoft security patches, and implement strict input validation on all user-supplied parameters before SQL query execution.
- 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-2000-0161 — 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-2000-0161 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