dbcve.org
OfficeApplication · Microsoft

CVE-2010-3952

HIGH · 9.3 CVSS v2.0 Published 2010-12-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
The FlashPix image converter in the graphics filters in Microsoft Office XP SP3 and Office Converter Pack allows remote attackers to execute arbitrary code or cause a denial of service (heap memory corruption) via a crafted FlashPix image in an Office document, aka "FlashPix Image Converter Heap Corruption 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 · high confidence

A heap corruption vulnerability exists in the FlashPix image converter within Microsoft Office XP SP3 and Office Converter Pack graphics filters. Attackers can exploit this by embedding a specially crafted FlashPix image in an Office document, leading to arbitrary code execution or denial of service.

MitigationApply Microsoft Security Update MS10-105, or preferably migrate to a supported Office version as Office XP reached end of support in 2011.

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
OfficeApplication
Affected:= xp
Office Converter PackApplication
Affected:all versions

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check for Microsoft Office XP installation
    Check registry key HKLM\SOFTWARE\Microsoft\Office\10.0\Common\InstallRoot or inspect Program Files\Microsoft Office for Office XP directories
    Affected if Office XP is installed (the graphics filters including FlashPix converter are present)
  2. Check for Microsoft Office Converter Pack installation
    Check registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\OfficeConverterPack or inspect Program Files\Common Files\Microsoft Shared\TextConv for converter pack files
    Affected if Office Converter Pack is installed (contains the vulnerable FlashPix graphics filter)
  3. Verify FlashPix converter filter presence
    Search for fpx32lt.dll or fpxtiftf.dll in the Office graphics filters directory (typically Program Files\Common Files\Microsoft Shared\Graphics or TextConv)
    Affected if The FlashPix image converter DLL files exist in the Office graphics filters location
  4. Confirm Office XP Service Pack level
    Check registry HKLM\SOFTWARE\Microsoft\Office\10.0\Common\InstallRoot for SP3 indicator, or run winmsd.exe and check Office version details
    Affected if Office XP is at SP3 or earlier (vulnerability exists in SP3 per CVE description)

You are affected if either Microsoft Office XP with graphics filters or Microsoft Office Converter Pack is installed, as both contain the vulnerable FlashPix image converter component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft Security Update MS10-105, or preferably migrate to a supported Office version as Office XP reached end of support in 2011.

Recommended fix High confidence

Upgrade to a currently supported Microsoft Office version (Microsoft 365, Office 2019, or Office 2016). The original patch was MS10-105 for Office XP SP3.

  1. 1. Backup all important Office documents and personal files before making any changes.
  2. 2. Since Microsoft Office XP reached end of support in July 2014, the recommended remediation is to migrate to a currently supported Microsoft Office version (such as Microsoft 365, Office 2019, or Office 2016).
  3. 3. If immediate upgrade is not possible, apply the original security update MS10-105 from Microsoft which addresses this vulnerability in Office XP SP3 and Office Converter Pack.
  4. 4. For Office Converter Pack, verify all installed versions and apply any available updates, though this software is also obsolete.
Caveat Office XP has been out of support since 2014; no further security updates are available. Upgrading to newer Office versions may require license purchase and may have feature/interface changes.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Office Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-3952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-3952 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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