CVE-2007-0870
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 · uneditedUnspecified vulnerability in Microsoft Word 2000 allows remote attackers to cause a denial of service (crash) via unknown vectors, a different vulnerability than CVE-2006-5994, CVE-2006-6456, CVE-2006-6561, and CVE-2007-0515, a variant of Exploit-MS06-027.
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 confidenceUnspecified vulnerability in Microsoft Word 2000 allows remote attackers to cause a denial of service (crash) via unknown vectors. This is a variant of Exploit-MS06-027 and affects only Word 2000, distinct from several related CVEs from 2006-2007.
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
- High
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:H/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.
-
Verify Microsoft Word 2000 is installedOpen Word, go to Help > About Microsoft Word, or check the program file version at C:\Program Files\Microsoft Office\Office\WINWORD.EXE by right-clicking and viewing Properties > VersionAffected if The version displays as 9.0.0.x (Word 2000) or the product name shows Microsoft Word 2000
-
Confirm this is the only Office version presentCheck Add/Remove Programs in Control Panel for Microsoft Office 2000 or Microsoft Word 2000 entry, or check C:\Program Files\Microsoft Office\Office\ for the WINWORD.EXE executableAffected if Word 2000 is the sole or primary Microsoft Word installation on the system
-
Verify the vulnerability is reachableThis CVE triggers via unknown vectors causing a crash. The flaw is inherent to Word 2000 when parsing specially crafted files or receiving specific inputAffected if Word 2000 is installed and can be invoked to process documents
If Microsoft Word 2000 (version 9.0.x) is installed on the system, the environment is affected by 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 dataSince Microsoft Word 2000 has been deprecated and is past end-of-support, the primary remediation is to upgrade to a supported Microsoft Office version. Organizations still running Word 2000 should prioritize migration to modern Office 365 or supported Office versions as part of legacy software decommissioning.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-0870 — 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 sources- archives.neohapsis.com
- osvdb.org
- secunia.com
- www.avertlabs.com
- www.avertlabs.com
- www.kb.cert.org
- www.microsoft.com
- www.securityfocus.com
- www.securityfocus.com
- www.securitytracker.com
- www.us-cert.gov
- www.vupen.com
- www.vupen.com
- docs.microsoft.com
- exchange.xforce.ibmcloud.com
- oval.cisecurity.org
- nvd.nist.gov
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-0870 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