CVE-2012-4886
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 wpsio.dll in Kingsoft WPS Office 2012 possibly 8.1.0.3238 allows remote attackers to execute arbitrary code via a long BSTR string.
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 confidenceStack-based buffer overflow in wpsio.dll in Kingsoft WPS Office 2012 allows remote attackers to execute arbitrary code via a specially crafted document containing an overly long BSTR (Binary String) value that overflows a stack-allocated buffer.
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.3238CVSS 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
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/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.
-
Verify Kingsoft WPS Office 2012 is installedCheck the program files directory for Kingsoft WPS Office installation, or look in Add/Remove Programs for Kingsoft Office 2012 entryAffected if Kingsoft WPS Office 2012 is installed on the system
-
Check the installed version of Kingsoft WPS Office 2012Locate the main executable (wps.exe or similar) and check its version properties, or use the program's About dialog to find the exact version numberAffected if Version equals exactly 8.1.0.3238
-
Verify wpsio.dll exists in the installation directoryFind the Kingsoft Office installation directory (typically C:\Program Files\Kingsoft\Office6) and confirm wpsio.dll is presentAffected if wpsio.dll file exists in the Kingsoft Office installation folder
-
Inspect the file version of wpsio.dllRight-click on wpsio.dll, select Properties, and check the File Version fieldAffected if wpsio.dll file version matches the main application version 8.1.0.3238
The system is affected only if Kingsoft WPS Office 2012 version 8.1.0.3238 is installed and the vulnerable wpsio.dll component is present; the vulnerability requires the user to open a specially crafted document with an overly long BSTR value.
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 dataApply available vendor patches from Kingsoft for WPS Office 2012; if no patch exists, implement application whitelisting, restrict document handling from untrusted sources, and consider migrating to an actively supported office suite.
- Consultation8.0 h
- Implementation16.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 $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-4886 — 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-2012-4886 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