CVE-2000-0419
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 2000 UA ActiveX Control is marked as "safe for scripting," which allows remote attackers to conduct unauthorized activities via the "Show Me" function in Office Help, aka the "Office 2000 UA 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 confidenceThe Office 2000 UA ActiveX Control is incorrectly marked as 'safe for scripting,' allowing remote attackers to execute unauthorized operations through the 'Show Me' function in Office Help. This client-side vulnerability can be exploited via malicious web pages to perform actions in the security context of the ActiveX control.
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= 2000= 2000= 2000= 2000= 1.0= 2000= 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 Office 2000 is installedOpen Control Panel > Add/Remove Programs, look for Microsoft Office 2000 or any of the affected products (Access 2000, Excel 2000, FrontPage 2000, Outlook 2000, PowerPoint 2000, Project 2000, PhotoDraw 2000). Alternatively, check the version by looking in the program's About dialog or in the registry under HKLM\SOFTWARE\Microsoft\Office\9.0\Common\InstallRootAffected if Office 2000 or any listed affected product is installed (version 9.0)
-
Locate the UA ActiveX control fileSearch for ua.dll or uactrl.dll on the system. Typical locations include C:\Program Files\Microsoft Office\Office\, C:\Program Files\Common Files\Microsoft Shared\, or within the installation directory of the specific Office applicationAffected if The ua.dll or uactrl.dll file exists on the system (this is the vulnerable UA ActiveX control)
-
Check registry for the ActiveX control safety settingsOpen regedit and navigate to HKCR\CLSID\{XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} where the CLSID corresponds to the UA control. Check the value of the 'ScriptSafe' or 'SafeForScripting' subkey, or examine the component category registration under the CLSID. Also check HKLM\SOFTWARE\Microsoft\Internet Explorer\ActiveX Compatibility for kill-bit settingsAffected if The UA ActiveX control is registered and either lacks a kill-bit or is marked as safe for scripting in the registry
-
Confirm Internet Explorer can instantiate the controlOpen Internet Explorer, press F12 to access developer tools, and attempt to create an instance of the UA control via the console: document.createElement('object') and set the CLSID, or view the 'Manage Add-ons' dialog to see if the UA ActiveX control is listed as loadedAffected if The UA ActiveX control appears in IE's manage add-ons list or can be instantiated in the browser context
A system is affected if Office 2000 (or any listed affected product) is installed, the UA ActiveX control file exists, and IE is able to load the control without it being disabled by a kill-bit or other security setting.
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 ActiveX controls in affected systems, apply the Microsoft security patch if available, or implement the ActiveX kill-bit registry setting to disable the vulnerable control. Consider upgrading from Office 2000 as it is no longer supported.
- Consultation2.0 h
- Implementation1.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0419 — 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-0419 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