CVE-2002-0622
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 · uneditedThe Office Web Components (OWC) package installer for Microsoft Commerce Server 2000 allows remote attackers to execute commands by passing the commands as input to the OWC package installer, aka "OWC Package Command Execution".
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 is a command injection vulnerability in the Office Web Components (OWC) package installer bundled with Microsoft Commerce Server 2000. Attackers can execute arbitrary commands by injecting them as input during the OWC installer execution, allowing remote code execution.
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= 2000CVSS 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 2000 installationCheck the system for Microsoft Commerce Server 2000 by reviewing installed programs in Add/Remove Programs or querying the Windows Registry under HKLM\SOFTWARE\Microsoft\Commerce Server for version keys.Affected if Commerce Server 2000 is present on the system.
-
Confirm Office Web Components presenceCheck for the presence of Office Web Components (OWC) on the system. This may appear as 'Office Web Components' or 'Microsoft OWC' in installed programs, or check registry locations such as HKLM\SOFTWARE\Microsoft\DataWarehouse\Components\OWC or file system locations under the Commerce Server installation directory.Affected if OWC is installed as part of Commerce Server 2000.
-
Identify installer service exposureDetermine if the Commerce Server installer service or remote installation interface is enabled and running. This may involve checking Windows services, IIS configuration if web-based installation is used, or DCOM components related to the installer.Affected if The installer service interface is exposed or accessible.
-
Assess network accessibilityReview network configuration to determine if the installer port or service is accessible from the network. Check firewall rules, listening ports, and whether the system is reachable on typical installer ports.Affected if The installer interface is reachable from network locations.
A system is affected if Commerce Server 2000 with OWC is installed and its installer interface is accessible, allowing unauthenticated command injection during installer execution.
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 Commerce Server 2000 and OWC are deprecated products, the primary remediation is to uninstall or remove the OWC component if unused, or implement network segmentation/firewalling to limit exposure to the vulnerable installer interface.
- 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-0622 — 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-0622 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