dbcve.org
Openoffice.orgApplication · Openoffice

CVE-2010-2935

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
simpress.bin in the Impress module in OpenOffice.org (OOo) 2.x and 3.x before 3.3 does not properly handle integer values associated with dictionary property items, which allows remote attackers to cause a denial of service (application crash) or possibly execute arbitrary code via a crafted PowerPoint document that triggers a heap-based buffer overflow, related to an "integer truncation error."

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

Heap-based buffer overflow in OpenOffice.org Impress (simpress.bin) module caused by integer truncation error when processing dictionary property items in crafted PowerPoint documents. The integer truncation leads to insufficient buffer allocation resulting in heap overflow that can trigger denial of service or potentially allow arbitrary code execution.

MitigationUpgrade to OpenOffice.org 3.3 or later which contains the fix. Until then, exercise caution with untrusted PowerPoint files and consider disabling OLE preview handlers.

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. Verify OpenOffice.org installation
    Check if OpenOffice.org is installed on the system. On Linux: dpkg -l | grep -i openoffice or rpm -qa | grep -i openoffice. On Windows: Check Program Files for OpenOffice.org folder or look in registry under HKEY_LOCAL_MACHINE\SOFTWARE\OpenOffice.
    Affected if OpenOffice.org is installed and the version cannot be determined or matches 3.2.1
  2. Determine installed OpenOffice.org version
    Run: soffice --version or look in the OpenOffice.org installation directory for a version file. Compare the version number against the affected version 3.2.1.
    Affected if The installed version is exactly 3.2.1, which matches the single affected version listed in the CVE
  3. Confirm Impress module presence
    Locate the simpress.bin module which handles PowerPoint import in Impress. This is typically found within the OpenOffice.org program directory. Check for the file existence: on Linux typically /usr/lib/openoffice/program/simpress.bin, on Windows in the program folder.
    Affected if The simpress.bin module exists and is from OpenOffice.org version 3.2.1
  4. Assess exposure to untrusted PowerPoint files
    Review recent file access logs or check user directories for recently opened .ppt or .pptx files. Check browser download folders and temporary directories for PowerPoint files. Audit any PowerPoint files received from external sources.
    Affected if Users have opened or previewed untrusted PowerPoint documents using the affected OpenOffice.org 3.2.1 installation

The environment is affected if OpenOffice.org version 3.2.1 is installed with the Impress (simpress.bin) module present and users have processed untrusted PowerPoint documents with it.

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 to OpenOffice.org 3.3 or later which contains the fix. Until then, exercise caution with untrusted PowerPoint files and consider disabling OLE preview handlers.

Recommended fix High confidence

OpenOffice.org 3.3 or later

  1. Download OpenOffice.org version 3.3 or later from the official OpenOffice website or your distribution's package repository
  2. Close any running OpenOffice.org applications
  3. Uninstall the current version of OpenOffice.org (version 3.2.1)
  4. Install the updated version (3.3 or later)
  5. Verify the installation by opening OpenOffice.org Impress and confirming the application runs without errors
Caveat Minor - user interface and feature changes between 3.2.1 and 3.3; review release notes for detailed changes

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

Fix this in Openoffice.org Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing5.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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