LiveActive security incident?Get immediate response
CVE Record

CVE-2010-2569: pubconv.dll (aka the Publisher Converter DLL) in Microsoft Publisher 2002 SP3, 2003 SP3, and 2007 SP2 does...

pubconv.dll (aka the Publisher Converter DLL) in Microsoft Publisher 2002 SP3, 2003 SP3, and 2007 SP2 does not properly handle an unspecified size field in certain older file formats, which allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) via a crafted Publisher file, aka "Size Value Heap Corruption in pubconv.dll Vulnerability."

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old Microsoft Publisher file-handling flaw. A malicious Publisher document could make vulnerable Publisher versions crash or potentially run attacker-controlled code when opened. Business urgency depends on whether legacy Publisher 2002, 2003, or 2007 installations still exist and receive files from email, web, or shared storage. Exposure is most likely in legacy desktop environments where affected Publisher versions are installed and users can open Publisher documents from untrusted sources. The provided structured affected list is incomplete, but the CVE description names Publisher 2002 SP3, 2003 SP3, and 2007 SP2. Prioritize if legacy Office/Publisher remains in use. This is document-based code execution risk, so one opened file could compromise a workstation. If no affected Publisher versions exist, urgency drops to verification and asset-record cleanup. Mitigation focus: Review Microsoft MS10-103 for vendor update and workaround guidance.; Prioritize remediation for systems with Publisher 2002, 2003, or 2007 installed.; Restrict untrusted Publisher files at email and web gateways where feasible..

Prepared

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-2010-2569 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
3Source 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.