dbcve.org
OpenofficeApplication · Apache

CVE-2007-2834

HIGH · 9.3 CVSS v2.0 Published 2007-09-18
Fix available
A fix is available. Upgrade to 2.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Integer overflow in the TIFF parser in OpenOffice.org (OOo) before 2.3; and Sun StarOffice 6, 7, and 8 Office Suite (StarSuite); allows remote attackers to execute arbitrary code via a TIFF file with crafted values of unspecified length fields, which triggers allocation of an incorrect amount of memory, resulting in a heap-based buffer overflow.

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
How this class of weakness works · CWE-190

An arithmetic operation produces a value too large for its type and wraps around to an unexpected — often tiny or negative — number. That miscalculated value then drives a memory allocation or a bounds check, opening the door to corruption. The fix is checked arithmetic and validating sizes before they're used.

General guidance for the integer overflow class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.3.0
Debian LinuxOperating system
Affected:= 3.1= 4.0
Ubuntu LinuxOperating system
Affected:= 6.06= 6.10= 7.04
StarofficeApplication
Affected:= 6.0= 7.0= 8.0
StarsuiteApplication
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

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 2.3.0 or later
Fixed in 2.3.0
Vendor patch www.debian.org →
Recommended fix High confidence

OpenOffice.org 2.3.0 or later; Debian/Ubuntu security update packages; StarOffice/StarSuite with vendor patch

  1. Identify the current installed version of OpenOffice.org or StarOffice/StarSuite using the application's 'About' menu or command line tools like 'rpm -qi' or 'dpkg -l'
  2. For OpenOffice.org: Download and install OpenOffice.org version 2.3.0 or later from the official Apache OpenOffice website (https://www.openoffice.org/download/)
  3. For Debian-based systems (Debian 3.1, 4.0; Ubuntu 6.06, 6.10, 7.04): Run 'apt-get update' followed by 'apt-get upgrade' to apply the latest security patches, or specifically install the updated openoffice.org package
  4. For StarOffice/StarSuite: Apply vendor-provided patches from Sun Microsystems, or upgrade to a patched version of StarOffice/StarSuite 8 update 8 or later
  5. After patching/upgrading, verify the new version is installed by checking the application version again
  6. As a temporary mitigation before patching, avoid opening untrusted TIFF files from unknown or untrusted sources
Caveat Minor - upgrading OpenOffice may introduce minor UI changes between major versions; ensure compatibility with existing document templates and macros

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $3,200. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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