dbcve.org
OpenofficeApplication · Apache

CVE-2010-3452

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 crafted tags 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

Use-after-free vulnerability in OpenOffice Writer (oowriter) when parsing RTF documents. The vulnerability is triggered by crafted tags within malicious RTF files, leading to memory corruption that can cause application crashes or potentially allow arbitrary code execution with user privileges.

MitigationUpgrade OpenOffice.org to version 3.3 or later, which contains the fix for this vulnerability. Alternatively, avoid opening untrusted RTF documents from unknown or 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. Verify OpenOffice Writer is installed
    Run 'dpkg -l | grep -i openoffice-writer' on Debian/Ubuntu, or 'rpm -qa | grep -i openoffice' on RPM-based systems, or check for the executable at /usr/bin/oowriter
    Affected if OpenOffice Writer is not installed on the system
  2. Determine installed OpenOffice version
    Run 'oowriter --version' or check the package version via 'dpkg -l | grep openoffice' or 'rpm -qi <package>'
    Affected if The installed version is greater than or equal to 2.0.0 AND less than 3.3.0 (for example, 2.4.5, 3.0.1, 3.2.0)
  3. Check RTF document handling capability
    Verify the RTF import filter is present by checking for files in /usr/lib/openoffice/share/filter/ or by attempting to open a simple RTF file with oowriter
    Affected if RTF filter modules exist and the application can parse RTF documents

Your environment is affected if OpenOffice Writer version 2.0.0 through 3.2.x is installed and the RTF document parsing feature is available, meaning opening a crafted malicious RTF file could trigger the use-after-free vulnerability.

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, which contains the fix for this vulnerability. Alternatively, avoid opening untrusted RTF documents from unknown or untrusted sources.

Recommended fix High confidence

OpenOffice.org 3.3.0 or later

  1. 1. Backup any important documents and personal settings in OpenOffice.
  2. 2. Uninstall the current version of OpenOffice.org (versions 2.x or any version before 3.3.0).
  3. 3. Download OpenOffice 3.3.0 or a later stable release from the official Apache OpenOffice website (https://www.openoffice.org/download/).
  4. 4. Install the new version of OpenOffice.
  5. 5. Verify the installation by checking Help > About OpenOffice to confirm the version number.
Caveat Minimal risk - this is a security upgrade; verify any macros or extensions are compatible with the new version

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
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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