dbcve.org
OpenofficeApplication · Apache

CVE-2010-3451

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
Use-after-free vulnerability in oowriter 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 malformed tables in an RTF 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

A use-after-free vulnerability exists in the oowriter component of OpenOffice.org versions 2.x and 3.x prior to version 3.3. The vulnerability is triggered when processing malformed table structures within RTF documents, allowing an attacker to potentially execute arbitrary code or cause application crash via memory corruption.

MitigationUpgrade OpenOffice.org to version 3.3 or later to remediate this vulnerability. Until upgrade is complete, exercise caution when opening RTF documents from untrusted sources.

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
Ubuntu LinuxOperating system
Affected:= 8.04= 9.10= 10.04= 10.10
Debian LinuxOperating system
Affected:= 5.0= 6.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. Check if OpenOffice Writer is installed
    On Linux (Debian/Ubuntu), run: dpkg -l | grep -i openoffice-writer or rpm -qa | grep -i openoffice-writer. On Windows, check Program Files for OpenOffice.org folder.
    Affected if OpenOffice Writer is not installed means not affected
  2. Determine installed OpenOffice version
    Run: oowriter --version or on Linux: dpkg -l | grep openoffice or rpm -qi openoffice-core. Alternatively, open OpenOffice Writer, go to Help > About to see version.
    Affected if The installed version is less than 3.3.0 (versions 2.x and 3.x prior to 3.3 are affected)
  3. Confirm RTF document handling capability
    Open any RTF file in OpenOffice Writer or check File > Open filter list for RTF support. The vulnerability triggers when processing malformed table structures in RTF documents.
    Affected if RTF files can be opened in Writer and the version is vulnerable

You are affected if OpenOffice Writer is installed with a version between 2.0.0 and 3.2.x inclusive (any version prior to 3.3.0).

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 to remediate this vulnerability. Until upgrade is complete, exercise caution when opening RTF documents from untrusted sources.

Recommended fix High confidence

OpenOffice.org 3.3.0 or later

  1. 1. Back up any important documents
  2. 2. Download OpenOffice.org 3.3.0 or later from the official Apache OpenOffice archive (https://archive.apache.org/dist/openoffice/)
  3. 3. Uninstall the existing OpenOffice installation
  4. 4. Install the OpenOffice 3.3.0 or newer version
  5. 5. Verify the installation by opening OpenOffice Writer and checking Help > About for version 3.3.0 or later

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

Fix this in Openoffice Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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