CVE-2010-0131
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 the SpreadSheet Lotus 123 reader (wkssr.dll), as used in Autonomy KeyView 10.4 and 10.9, Symantec Mail Security, and possibly other products, allows remote attackers to execute arbitrary code via unspecified vectors related to floating point conversion in unknown record types.
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 the Lotus 123 spreadsheet parser (wkssr.dll) used by Autonomy KeyView and Symantec Mail Security. The vulnerability occurs during floating point conversion in unknown record types when parsing malicious .wk1/.wk3/.wk4 Lotus 123 files, allowing attackers to overwrite stack memory and execute arbitrary code.
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.4= 10.9= 10.4= 10.9= 10.4= 10.9all versionsCVSS 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 Autonomy KeyView SDK installationSearch for KeyView installation directories or check product version via registry keys under HKEY_LOCAL_MACHINE\SOFTWARE\Autonomy\KeyView or similar paths, or use 'wmic product' command to list installed Autonomy productsAffected if Autonomy KeyView Export, Filter, or Viewer SDK versions 10.4 or 10.9 are installed
-
Identify Symantec Mail Security installationCheck for Symantec Mail Security via Windows Add/Remove Programs, or search for 'Symantec Mail Security' in registry under HKEY_LOCAL_MACHINE\SOFTWARE\Symantec, or run 'wmic product' to list installed productsAffected if Symantec Mail Security of any version is installed
-
Locate the vulnerable wkssr.dll librarySearch for wkssr.dll in the KeyView installation directory (commonly under C:\Program Files\Autonomy\KeyView or similar), or search the entire system using 'dir /s wkssr.dll' in Command Prompt or Get-ChildItem -Recurse in PowerShellAffected if wkssr.dll exists on the system, indicating the Lotus 123 parser component is present
-
Confirm Lotus 123 file processing is enabledReview the application configuration for KeyView or Symantec Mail Security to determine if processing of .wk1, .wk3, or .wk4 file attachments is permitted; check mail gateway or filtering policiesAffected if The affected application is configured to process or scan Lotus 123 spreadsheet attachments from incoming emails or untrusted sources
The environment is affected if Autonomy KeyView SDK (versions 10.4 or 10.9) or any version of Symantec Mail Security is installed AND the system processes or scans Lotus 123 files (.wk1/.wk3/.wk4) from untrusted sources.
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 vendor patches from Autonomy KeyView (10.4/10.9) or Symantec Mail Security. Until patches are available, disable or restrict processing of untrusted Lotus 123 attachments/files in affected applications.
- Consultation4.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0131 — 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-2010-0131 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