LiveActive security incident?Get immediate response
CVE Record

CVE-2005-0558: Buffer overflow in Microsoft Word 2000, Word 2002, and Word 2003 allows remote attackers to execute arbitra...

Buffer overflow in Microsoft Word 2000, Word 2002, and Word 2003 allows remote attackers to execute arbitrary code via a crafted document.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A malicious Word document could cause older Microsoft Word versions to run attacker-controlled code when the file is opened. This is mainly a risk for environments that still have Word 2000, Word 2002, or Word 2003 installed or accessible on legacy systems.

Executive priority

Prioritize remediation if any affected Word versions remain in production or reachable legacy environments. The business risk is arbitrary code execution from a malicious document, but urgency depends on whether these obsolete Office versions still exist in the estate.

Technical view

The CVE describes a buffer overflow in Microsoft Word 2000, Word 2002, and Word 2003 triggered by a crafted document. Successful exploitation can execute arbitrary code in the context of the user running Word. The source bundle does not provide CVSS, CWE, or detailed root-cause data.

Likely exposure

Exposure is most likely in legacy desktops, virtual desktops, archives, or isolated business systems that retain Word 2000, Word 2002, or Word 2003. Modern Office deployments are not identified as affected in the provided sources.

Exploitation context

The CVE states remote attackers can exploit this through a crafted document. The bundle does not cite CISA KEV listing, active exploitation, public exploit reliability, or in-the-wild activity. Treat it as a document-delivery risk where affected Word versions remain.

Researcher notes

Available evidence is sparse: the bundle confirms product versions, crafted-document trigger, and arbitrary code execution impact. It does not include CVSS, CWE mapping, exploit maturity, or detailed affected file/component data. Avoid expanding scope beyond Word 2000, Word 2002, and Word 2003.

Mitigation direction

  • Review and apply Microsoft guidance from MS05-023 for affected systems.
  • Retire or isolate Word 2000, Word 2002, and Word 2003 installations.
  • Block or quarantine unexpected legacy Word documents from untrusted senders.
  • Use endpoint controls to restrict execution from document-handling workflows.

Validation and detection

  • Inventory endpoints for Word 2000, Word 2002, and Word 2003.
  • Check patch status against Microsoft MS05-023 guidance.
  • Review mail and file gateways for controls on untrusted Word documents.
  • Use OVAL definitions, where supported, to validate affected-system detection.
Prepared
Confidence
medium
Sources
5

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2005-0558 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
7Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.