CVE-2000-0329
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 · uneditedA Microsoft ActiveX control allows a remote attacker to execute a malicious cabinet file via an attachment and an embedded script in an HTML mail, aka the "Active Setup Control" vulnerability.
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 2000-era vulnerability in a Microsoft ActiveX control (the 'Active Setup Control') that allows remote code execution via specially crafted HTML email messages containing malicious cabinet (.cab) files and embedded script. An attacker can trick a user into opening a malicious email attachment, leading to arbitrary code execution on the vulnerable system.
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= 4.0= 4.0.1= 4.1= 5= 5.0= 4.0= 98= 2000= 4.27.3110.1= 4.72.2106.4= 4.72.3120.0= 4.72.3612.1700= 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
- High
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:H/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.
-
Check Internet Explorer versionOpen a command prompt and run 'reg query "HKLM\SOFTWARE\Microsoft\Internet Explorer" /v Version' or launch IE and go to Help > About Internet ExplorerAffected if The version reported is 4.0, 4.0.1, 4.1, 5, or 5.0 (these specific versions are in the affected range)
-
Check Microsoft Outlook versionLaunch Outlook and go to Help > About Microsoft Outlook, or check the installed programs list in Control PanelAffected if The version is 98 or 2000 (these specific versions are in the affected range)
-
Check Outlook Express versionLaunch Outlook Express and go to Help > About Outlook Express, or check the version in the application's propertiesAffected if The version matches one of: 4.27.3110.1, 4.72.2106.4, 4.72.3120.0, 4.72.3612.1700, or 5.0 (exact version match required)
-
Verify the Active Setup Control component is presentCheck for the presence of the shdocvw.dll or actxprxy.dll ActiveX control files in the system32 or system directoryAffected if These ActiveX control DLLs exist in their expected Windows system directories (indicating the vulnerable component is installed)
-
Confirm HTML email rendering is enabledIn Outlook or Outlook Express, check whether HTML email format is enabled in the mail settings or security zone settingsAffected if HTML email rendering is turned on (the attack vector requires HTML email to be processed)
If any of the specific affected versions of Internet Explorer, Outlook, or Outlook Express are installed AND the Active Setup Control component is present, the system is potentially vulnerable to this CVE.
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 the historical Microsoft security patches from the year 2000 that addressed this vulnerability, or migrate away from affected legacy Windows/Internet Explorer configurations. Consider disabling ActiveX controls in Outlook or using a modern email client as a longer-term defensive measure.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0329 — 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-0329 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