dbcve.org
OpenofficeApplication · Apache

CVE-2012-2665

HIGH · 7.5 CVSS v2.0 Published 2012-08-06
Fix available
A fix is available. Upgrade to 3.4.1 or later.
See remediation →
84/100
Remediation priority · High
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
Multiple heap-based buffer overflows in the XML manifest encryption tag parsing functionality in OpenOffice.org and LibreOffice before 3.5.5 allow remote attackers to cause a denial of service and possibly execute arbitrary code via a crafted Open Document Text (.odt) file with (1) a child tag within an incorrect parent tag, (2) duplicate tags, or (3) a Base64 ChecksumAttribute whose length is not evenly divisible by four.

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

Multiple heap-based buffer overflows exist in the XML manifest encryption tag parsing functionality of OpenOffice.org and LibreOffice versions prior to 3.5.5. The vulnerabilities are triggered when processing crafted Open Document Text (.odt) files containing malformed XML manifests with incorrect parent/child tag relationships, duplicate tags, or Base64-encoded ChecksumAttribute values with lengths not divisible by four, potentially allowing denial of service or arbitrary code execution.

MitigationUpgrade to LibreOffice 3.5.5 or later (or corresponding OpenOffice.org version) to patch the vulnerable XML manifest parsing code. Until upgraded, avoid opening .odt files 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:< 3.4.1
Ubuntu LinuxOperating system
Affected:= 10.04= 11.04= 11.10= 12.04
Debian LinuxOperating system
Affected:= 6.0= 7.0
Enterprise LinuxOperating system
Affected:= 6.0
Enterprise Linux DesktopOperating system
Affected:= 6.0
Enterprise Linux For Ibm Z SystemsOperating system
Affected:= 6.0
Enterprise Linux For Power Big EndianOperating system
Affected:= 6.0
Enterprise Linux ServerOperating system
Affected:= 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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 LibreOffice version
    Run 'libreoffice --version' or check the installed package version using your system's package manager (dpkg -r or rpm -q for Debian/RHEL systems)
    Affected if The installed LibreOffice version is prior to 3.5.5
  2. Check Apache OpenOffice version
    Run 'openoffice --version' or 'soffice --version', or check the installed package version using your system's package manager
    Affected if The installed Apache OpenOffice version is prior to 3.4.1
  3. Verify operating system bundled office suite version
    On Ubuntu, check with 'dpkg -l | grep -i office' or 'apt-cache policy libreoffice'. On RHEL/Debian systems, query the installed libreoffice-core or openoffice.org packages
    Affected if The OS-bundled office package version matches the vulnerable versions listed (Ubuntu 10.04-12.04, Debian 6.0-7.0, RHEL 6.0 variants) and the application version is below the fixed releases

You are affected if LibreOffice below 3.5.5 or Apache OpenOffice below 3.4.1 is installed, or if your Linux distribution shipped with a vulnerable bundled version of either suite.

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.

From vendor data
Upgrade available Upgrade to 3.4.1 or later
Fixed in 3.4.1
Interim mitigation

Upgrade to LibreOffice 3.5.5 or later (or corresponding OpenOffice.org version) to patch the vulnerable XML manifest parsing code. Until upgraded, avoid opening .odt files from untrusted sources.

Fix this in Openoffice Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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