LiveActive security incident?Get immediate response
CVE Record

CVE-2004-0571: Microsoft Word for Windows 6.0 Converter does not properly validate certain data lengths, which allows remo...

Microsoft Word for Windows 6.0 Converter does not properly validate certain data lengths, which allows remote attackers to execute arbitrary code via a .wri, .rtf, and .doc file sent by email or malicious web site, aka "Table Conversion Vulnerability," a different vulnerability than CVE-2004-0901.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This is a legacy Microsoft Word for Windows 6.0 Converter flaw. A malicious .wri, .rtf, or .doc file delivered by email or a website could cause arbitrary code execution. Treat it as serious where old Office conversion components remain in use.

Executive priority

Prioritize remediation for any legacy workstation or server that can open external documents. Business urgency depends on whether this obsolete converter exists in the environment; if absent, residual risk is low.

Technical view

CVE-2004-0571 is the MS04-041 “Table Conversion Vulnerability.” The converter fails to validate certain data lengths, enabling remote code execution through crafted document formats. The record distinguishes it from CVE-2004-0901. The bundle does not provide CVSS, CWE, or detailed affected-version metadata.

Likely exposure

Exposure is most likely on legacy Windows systems or Office-related installations that still include the Microsoft Word for Windows 6.0 Converter and open untrusted .wri, .rtf, or .doc files.

Exploitation context

The source states remote attackers can trigger code execution through email-delivered files or malicious websites. The bundle does not cite CISA KEV listing or active exploitation evidence, so active exploitation should not be assumed.

Researcher notes

The public bundle is sparse: no CVSS, CWE, precise product matrix, or exploit intelligence is included. Anchor validation on MS04-041 and OVAL checks, and avoid conflating this issue with CVE-2004-0901.

Mitigation direction

  • Review Microsoft MS04-041 for applicable security update guidance.
  • Apply vendor-approved updates on systems retaining the converter.
  • Remove or disable the legacy converter where business use is unnecessary.
  • Restrict opening untrusted .wri, .rtf, and .doc files on legacy hosts.
  • Use email and web controls to reduce delivery of risky document attachments.

Validation and detection

  • Inventory endpoints for legacy Office conversion components.
  • Check patch status against Microsoft MS04-041 applicability.
  • Use cited OVAL definitions where supported by your scanner.
  • Review email and web telemetry for suspicious document delivery.
  • Confirm vulnerable file types are blocked or handled safely on legacy systems.
Prepared
Confidence
medium
Sources
12

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-2004-0571 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
11Source 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.