CVE-2002-0623
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 · uneditedBuffer overflow in AuthFilter ISAPI filter on Microsoft Commerce Server 2000 and 2002 allows remote attackers to execute arbitrary code via long authentication data, aka "New Variant of the ISAPI Filter Buffer Overrun".
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 · moderate confidenceBuffer overflow vulnerability in the AuthFilter ISAPI filter in Microsoft Commerce Server 2000 and 2002 allows remote attackers to execute arbitrary code by sending excessively long authentication data to the filter.
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= 2000= 2002CVSS 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 Commerce Server installationCheck if Microsoft Commerce Server is installed on the system by reviewing installed programs in Add/Remove Programs, or look for Commerce Server directories in the file systemAffected if Commerce Server is present on the system
-
Identify the installed Commerce Server versionCheck the installed version of Commerce Server using the program's About dialog, version information in the installation directory, or Windows installer recordsAffected if The installed version is exactly 2000 or exactly 2002 (not newer patched versions)
-
Locate the AuthFilter ISAPI filterExamine the IIS metabase or configuration to determine if the AuthFilter ISAPI filter is registered and loaded. For Commerce Server 2000/2002, this filter is typically named 'CommerceAuth' or similar and handles authentication requestsAffected if The AuthFilter ISAPI filter is present in the IIS configuration
-
Confirm the filter is enabled and activeVerify in IIS that the AuthFilter ISAPI filter is not only registered but actively enabled for the Commerce Server web sitesAffected if The AuthFilter ISAPI filter is enabled and processing requests for Commerce Server sites
The environment is affected if Microsoft Commerce Server version 2000 or 2002 is installed AND the AuthFilter ISAPI filter is enabled in IIS, allowing remote attackers to send excessively long authentication data to trigger the buffer overflow.
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 available Microsoft security patches for Commerce Server, or disable/remove the AuthFilter ISAPI filter if patches are unavailable; consider upgrading to a supported Commerce Server version.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2002-0623 — 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-0623 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