CVE-2013-3934
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 · uneditedStack-based buffer overflow in Kingsoft Writer 2012 8.1.0.3030, as used in Kingsoft Office 2013 before 9.1.0.4256, allows remote attackers to execute arbitrary code via a long font name in a WPS file.
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 · moderate confidenceStack-based buffer overflow vulnerability in Kingsoft Writer/Office when parsing WPS document files. The vulnerability is triggered by a specially crafted WPS file containing an overly long font name, which causes the application to write beyond buffer boundaries on the stack, enabling 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= 8.1.0.3385= 8.1.0.3030CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Kingsoft Office or Writer is installedCheck Program Files for Kingsoft Office folder, or look for Kingsoft entries in Add/Remove Programs (appwiz.cpl)Affected if Kingsoft Office or Kingsoft Writer is present on the system
-
Determine the installed version of Kingsoft OfficeRight-click the Kingsoft Office application shortcut, select Properties, and check the version number in the Details tab, or open Kingsoft Writer/Office and go to Help > AboutAffected if The version is 8.1.0.3385 for Kingsoft Office 2012 or 8.1.0.3030 for Kingsoft Writer 2012 (or earlier versions)
-
Confirm WPS file parsing is availableAttempt to open a .wps file with Kingsoft Writer, or check if WPS is a registered file type for the applicationAffected if WPS files can be opened or are associated with Kingsoft Writer/Office
-
Identify recently opened WPS filesCheck the application recent files list (File > Recent) or review Windows Prefetch/Temp folders for .wps files that may have been openedAffected if There are WPS files that have been opened with the affected application version
You are affected if you have Kingsoft Office 2012 version 8.1.0.3385 or Kingsoft Writer 2012 version 8.1.0.3030 installed AND you open or process WPS document files with this vulnerable version.
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.
dbcve · scopedUpgrade Kingsoft Office to version 9.1.0.4256 or later. Avoid opening WPS files from untrusted sources until the patch is applied, as the attack vector is a malicious document file.
Kingsoft Office 2013 version 9.1.0.4256 or later (or WPS Office if rebranded)
- 1. Verify current installed version of Kingsoft Office/WPS Office by opening the application and navigating to Help > About
- 2. Download Kingsoft Office 2013 version 9.1.0.4256 or later from the official Kingsoft/WPS website
- 3. Backup any important documents created with the current installation
- 4. Uninstall the current version of Kingsoft Writer 2012/Office 2012
- 5. Install the updated version (9.1.0.4256 or later)
- 6. Verify the installation was successful by checking the version number in Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3934 — 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-2013-3934 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