dbcve.org
Openoffice.orgApplication · Openoffice

CVE-2010-2936

HIGH · 9.3 CVSS v2.0 Published 2010-08-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Integer overflow in simpress.bin in the Impress module 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 polygons in a PowerPoint document that triggers 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 · high confidence

Integer overflow in simpress.bin (Impress module) in OpenOffice.org 2.x and 3.x before 3.3 allows remote attackers to cause a denial of service or possibly execute arbitrary code via crafted polygons in a PowerPoint document that triggers a heap-based buffer overflow.

MitigationUpgrade OpenOffice.org to version 3.3 or later to patch the integer overflow vulnerability in the Impress module's polygon parsing logic.

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
Openoffice.orgApplication
Affected:= 3.2.1

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.org is installed
    Locate the OpenOffice.org installation directory. On Linux, common paths include /usr/lib/openoffice, /opt/openoffice, or /usr/bin/soffice. On Windows, check Program Files for OpenOffice.org folders.
    Affected if OpenOffice.org is not found on the system, then the vulnerability does not apply.
  2. Determine the installed OpenOffice.org version
    Run the OpenOffice.org binary with version flag: soffice --version (Linux/Unix) or look in the installation directory for a version file. On Windows, check the registry under HKEY_LOCAL_MACHINE\SOFTWARE\OpenOffice or examine the program file properties of soffice.exe.
    Affected if The installed version is 2.x or 3.x versions prior to 3.3 (for example, 3.2.1, 3.2, 3.1, 3.0, 2.x).
  3. Verify the Impress module is present
    Check for the presence of the simpress.bin module in the OpenOffice.org program directory. On Linux, this is typically in /usr/lib/openoffice/program/. On Windows, look in the program folder for simpress.bin or simpress.exe.
    Affected if The simpress.bin module exists and the version is vulnerable per step 2.
  4. Confirm the vulnerability window
    Review the version against the affected range: versions 2.x and 3.x before 3.3 are vulnerable. The specific version 3.2.1 is listed as affected.
    Affected if The installed version falls within 2.x through 3.2.x (inclusive), meaning the integer overflow in polygon parsing is present in the Impress module.

The environment is affected if OpenOffice.org versions 2.x or 3.x prior to 3.3 are installed with the Impress module (simpress.bin) present.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OpenOffice.org to version 3.3 or later to patch the integer overflow vulnerability in the Impress module's polygon parsing logic.

Recommended fix Moderate confidence

OpenOffice.org 3.3 or later

  1. 1. Back up any important OpenOffice.org documents and settings
  2. 2. Uninstall the current version of OpenOffice.org (version 3.2.1)
  3. 3. Download OpenOffice.org version 3.3 or later from the official Apache OpenOffice website (https://www.openoffice.org/)
  4. 4. Install the downloaded version following the standard installation procedure
  5. 5. Verify the installed version by opening OpenOffice and checking Help > About OpenOffice.org

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

Fix this in Openoffice.org Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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