Openoffice.orgApplication · Openoffice

CVE-2009-0200

HIGH · 9.3 CVSS v2.0 Published 2009-09-02

Fix available

A fix is available. Upgrade to after 3.1 or later.

See remediation →

100/100

Remediation priority · Urgent

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

Integer underflow in OpenOffice.org (OOo) before 3.1.1 and StarOffice/StarSuite 7, 8, and 9 might allow remote attackers to execute arbitrary code via crafted records in the document table of a Word document, leading to a heap-based buffer overflow.

Technical summary

dbcve analysis · high confidence

Integer underflow vulnerability in OpenOffice.org's Word document parser when processing crafted records in the document table. The underflow leads to a heap-based buffer overflow that can be exploited for arbitrary code execution via specially crafted Word documents.

MitigationUpgrade OpenOffice.org to version 3.1.1 or later, or apply vendor-specific patches for StarOffice/StarSuite. Until patched, avoid opening Word 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

NVD · CPE data

Openoffice.orgApplication

Affected:<= 3.1= 1.0-ru= 1.0.0= 1.0.1= 1.0.2= 1.0.3.1= 1.1= 1.1.1= 1.1.2= 1.1.3= 1.1.4= 1.1.5

CVSS breakdown

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?

dbcve checks

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

Identify OpenOffice.org installation

On Linux systems, run 'rpm -qa | grep -i openoffice' or 'dpkg -l | grep openoffice'. On Windows, check Program Files for OpenOffice.org folder. On Mac, check /Applications for OpenOffice.org

Affected if If no OpenOffice.org package is found, the system is not affected by this CVE
Determine installed OpenOffice.org version

On Linux RPM systems: 'rpm -q --queryformat "%{VERSION}-%{RELEASE}" openoffice.org-core'. On Linux DEB systems: 'dpkg -s openoffice.org-core 2>/dev/null | grep Version'. On Windows: locate soffice.exe in the OpenOffice.org program folder, right-click, select Properties, and check the Version tab

Affected if If the installed version is 3.1 or lower, or matches any of these exact versions: 1.0-ru, 1.0.0, 1.0.1, 1.0.2, 1.0.3.1, 1.1, 1.1.1, 1.1.2, 1.1.3, 1.1.4, 1.1.5, then the installation is vulnerable
Confirm Word document import capability

Launch OpenOffice Writer, attempt to open a .doc file, or check if the Word document import filter is listed in Tools > Options > Load/Save > File Formats

Affected if If Word document filters are available and users can open .doc files, the vulnerable parser code is present and can be triggered

The environment is affected if OpenOffice.org version is 3.1 or lower, or matches any of the specific 1.0-x or 1.1.x versions listed, and the application is used to open Word documents.

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

Remediation

dbcve · scoped

Upgrade available Upgrade to a release after 3.1

Interim mitigation

Upgrade OpenOffice.org to version 3.1.1 or later, or apply vendor-specific patches for StarOffice/StarSuite. Until patched, avoid opening Word documents from untrusted sources.

Recommended fix High confidence

OpenOffice.org 3.1.1

Upgrade OpenOffice.org to version 3.1.1 or later to remediate the integer underflow vulnerability
For StarOffice/StarSuite, contact Oracle/Sun Microsystems for vendor-specific patches for versions 7, 8, and 9

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

Fix this in Openoffice.org Scoped from the published advisory

Consultation4.0 h
Implementation8.0 h
Testing6.0 h
Review / QA2.0 h

20.0 hours of engineering $3,500

Get the upgrade done

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2009-0200?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsUpgrade to after 3.1 or later

Severity 9.3 High

Exploit likelihood EPSS, next 30 days 6.7%

Affects: Openoffice.org

Remediation

A high-priority fix

Fix this in Openoffice.org 20 hrs · Moderate

Typical engagement from $3,500

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2009-0200 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

Affected products & versions

CVSS breakdown

Am I affected?

Remediation

References