OpenofficeApplication · Apache
CVE-2017-12607
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 · uneditedA vulnerability in OpenOffice's PPT file parser before 4.1.4, and specifically in PPTStyleSheet, allows attackers to craft malicious documents that cause denial of service (memory corruption and application crash) potentially resulting in arbitrary code execution.
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 confidenceMemory corruption vulnerability in OpenOffice's PowerPoint file parser (PPTStyleSheet component) allows attackers to craft malicious PPT files that cause denial of service through memory corruption and application crashes, with potential for arbitrary code execution.
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
< 4.1.4
Debian LinuxOperating system
= 7.0= 8.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Verify OpenOffice installationCheck if Apache OpenOffice is installed by searching for the application binary or package. On Linux, run 'dpkg -l | grep -i openoffice' or 'rpm -qa | grep -i openoffice'. On Windows, check Program Files for OpenOffice folder.Affected if OpenOffice is found on the system
-
Determine installed OpenOffice versionOn Linux, run 'dpkg -l | grep -i openoffice' and look at the version number. On Windows, right-click the OpenOffice executable in Program Files, select Properties, and check the Details tab for version information.Affected if The version number is lower than 4.1.4 (for example, 4.1.3, 4.1.2, etc.)
-
Check Debian package version if applicableOn Debian systems, run 'apt-cache policy openoffice.org' or check the installed package version with 'dpkg -l | grep -i openoffice' to confirm the version matches Debian 7.0 or 8.0 packages.Affected if Running Debian 7.0 or 8.0 with OpenOffice packages from the affected distribution
-
Identify PPT file handling capabilityThe vulnerability triggers when OpenOffice processes a malicious PPT (PowerPoint) file using the PPTStyleSheet component. Check if users have the ability to open PPT files in OpenOffice Impress or Calc.Affected if OpenOffice can open or import PPT files and the version is below 4.1.4
You are affected if Apache OpenOffice version 4.1.4 or later is NOT installed and users open untrusted PPT files in the application.
Generated from the published advisory. Verify against your own configuration.
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 data4.1.4
Upgrade to OpenOffice 4.1.4 or later; avoid opening untrusted PPT files from unknown sources until patched.
Fix this in Openoffice
Scoped from the published advisory
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12607 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12607 in production — separate from our analysis above.
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.
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.
- 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