dbcve.org
OpenofficeApplication · Apache

CVE-2010-4643

HIGH · 9.3 CVSS v2.0 Published 2011-01-28
Fix available
A fix is available. Upgrade to 3.3.0 or later.
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
Heap-based buffer overflow in Impress in OpenOffice.org (OOo) 2.x and 3.x before 3.3 allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted Truevision TGA (TARGA) file in an ODF or Microsoft Office document.

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

Heap-based buffer overflow in OpenOffice.org Impress when parsing embedded Truevision TGA (TARGA) image files within ODF or Microsoft Office documents. A specially crafted TGA file can trigger overflow on the heap, leading to potential code execution or application crash.

MitigationUpgrade OpenOffice.org to version 3.3 or later. Until patched, avoid opening documents from untrusted sources that contain embedded TGA images.

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
OpenofficeApplication
Affected:>= 2.0.0, < 3.3.0

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. Identify OpenOffice installation and version
    Check for OpenOffice installation: On Windows, look in Program Files for OpenOffice.org folder, or run 'soffice --version' (Linux/Mac). Read the version from the folder name or command output.
    Affected if Version is 2.0.0 or higher but lower than 3.3.0 (e.g., 2.4.x, 3.0.x, 3.2.x)
  2. Confirm OpenOffice Impress component is present
    Verify the Impress component is installed: On Windows, check for Impress in the OpenOffice.org program folder; on Linux, run 'dpkg -l | grep openoffice-impress' or 'rpm -qa | grep openoffice-impress'.
    Affected if Impress is installed and version is in the affected range (>=2.0.0, <3.3.0)
  3. Verify TGA file parsing capability exists
    TGA image support is built into the Impress parser in affected versions. No additional configuration needed to be vulnerable - the parsing occurs automatically when a document containing a TGA image is opened in Impress.
    Affected if Documents with embedded TGA images can be opened and parsed by Impress in this version

User is affected if OpenOffice version is 2.0.0 through 3.2.x (inclusive) and Impress is used to open documents containing embedded TARGA/TGA images.

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
Upgrade available Upgrade to 3.3.0 or later
Fixed in 3.3.0
Interim mitigation

Upgrade OpenOffice.org to version 3.3 or later. Until patched, avoid opening documents from untrusted sources that contain embedded TGA images.

Recommended fix High confidence

OpenOffice 3.3.0 or later

  1. 1. Verify the current OpenOffice version by going to Help > About OpenOffice.
  2. 2. Download OpenOffice 3.3.0 or later from the official Apache OpenOffice website (https://www.openoffice.org/download/).
  3. 3. Close all OpenOffice applications.
  4. 4. Install the new version, ensuring to back up any user data and settings if desired.
  5. 5. After installation, verify the version shows 3.3.0 or higher in Help > About OpenOffice.
Caveat Minimal risk; standard minor version upgrade. Users should back up custom templates and macros before upgrading.

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

Fix this in Openoffice Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-4643 — 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-4643 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