CVE-2000-0088
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 the conversion utilities for Japanese, Korean and Chinese Word 5 documents allows an attacker to execute commands, aka the "Malformed Conversion Data" 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 · moderate confidenceBuffer overflow vulnerability in Microsoft Word's conversion utilities for Japanese, Korean, and Chinese Word 5 documents allows execution of arbitrary commands via malformed conversion data.
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= 97= 2000= 2000.0= 97= 2000= 97= 98= 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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/Au:N/C:C/I:C/A:C
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.
-
Identify installed Microsoft Word versionOpen Word, go to Help > About Microsoft Word, or run 'winword.exe /?' to view version information. Alternatively, check Add/Remove Programs or the program file properties for version details.Affected if Version is 97, 98, or 2000 (the affected versions)
-
Identify installed Microsoft Office versionOpen any Office application, go to Help > About, or check Add/Remove Programs for Microsoft Office entries. Version information may also appear in the program files directory.Affected if Office version is 97 or 2000 (the affected versions)
-
Identify installed Microsoft PowerPoint versionOpen PowerPoint, go to Help > About Microsoft PowerPoint, or check Add/Remove Programs for PowerPoint version.Affected if PowerPoint version is 97 or 2000 (the affected versions)
-
Check for Microsoft Office Converter Pack installationCheck Add/Remove Programs for 'Microsoft Office Converter Pack' or search for conversion-related files in the Office installation directory (commonly C:\Program Files\Microsoft Office\Office or Converter).Affected if Converter Pack version 2000.0 is installed
-
Confirm presence of East Asian Word 5 conversion utilitiesLook for conversion filters or converters in the Office installation path, particularly those handling Japanese, Korean, or Chinese document formats. Check program directories for files related to 'Wrd6cnv.exe' or East Asian text converters.Affected if The East Asian document conversion utilities for Word 5 are present and the affected product versions above are detected
A user is affected if they have Microsoft Word, PowerPoint, or Office version 97, 98, or 2000 (or Converter Pack 2000.0) installed AND the East Asian Word 5 conversion utilities are present on the system.
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 Microsoft security patch MS00-001 or upgrade to a non-vulnerable version of Microsoft Word; ensure updated antivirus protections are in place for defense-in-depth.
- Consultation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2000-0088 — 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-0088 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