CVE-2017-17967
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 · uneditedpptreader.dll in Kingsoft WPS Office 10.1.0.6930 allows remote attackers to cause a denial of service via a crafted PPT file, aka CNVD-2017-35482.
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 confidenceA denial of service vulnerability exists in pptreader.dll of Kingsoft WPS Office version 10.1.0.6930. Attackers can trigger the vulnerability by crafting a malicious PPT (PowerPoint) file that causes the application to crash or become unresponsive when opened.
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= 10.1.0.6930CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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 Kingsoft WPS Office is installedCheck for WPS Office installation in Program Files (typically C:\Program Files\Kingsoft\WPS Office or C:\Program Files (x86)\Kingsoft\WPS Office) or look for the application in Add/Remove Programs.Affected if Kingsoft WPS Office is present on the system
-
Identify installed WPS Office versionRight-click on the WPS Office application icon, select Properties, and check the Version field, or look in the Windows Registry under HKEY_LOCAL_MACHINE\SOFTWARE\Kingsoft\WPS\Install or HKEY_CURRENT_USER\SOFTWARE\Kingsoft\WPS\Install for the version value.Affected if The installed version is exactly 10.1.0.6930
-
Confirm pptreader.dll is presentNavigate to the WPS Office installation directory (such as C:\Program Files\Kingsoft\WPS Office\office6\) and verify that pptreader.dll exists in that folder.Affected if pptreader.dll is present in the WPS Office installation directory
-
Check if PPT file handling is enabledVerify that WPS Office is configured to handle PPT/PPTX file associations, which can be confirmed by attempting to open a PPT file or checking file associations in Windows Default Programs settings.Affected if WPS Office is set as the default handler for PPT/PPTX files
The environment is affected if Kingsoft WPS Office version 10.1.0.6930 is installed and configured to open PPT files, since the denial of service triggers when a malicious PPT file is opened using the vulnerable pptreader.dll component.
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 dataUpdate Kingsoft WPS Office to the latest patched version. Until patched, avoid opening PPT files from untrusted or unknown sources, and consider deploying email/network filtering to block potentially malicious attachments.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17967 — 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-17967 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