CVE-2010-1524
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 · uneditedThe SpreadSheet Lotus 123 reader (wkssr.dll) in Autonomy KeyView 10.4 and 10.9, as used in multiple IBM, Symantec, and other products, allows remote attackers to execute arbitrary code via unspecified vectors related to allocation of an array of pointers and "string indexing," which triggers memory corruption.
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 confidenceMemory corruption vulnerability in the Lotus 123 spreadsheet reader (wkssr.dll) of Autonomy KeyView 10.4 and 10.9. The vulnerability involves improper allocation of an array of pointers combined with erroneous string indexing, leading to controlled memory corruption that can be exploited for arbitrary code execution when parsing specially crafted Lotus 123 files.
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.9CVSS 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.
-
Locate KeyView SDK installation and versionSearch for KeyView DLLs or check application installation directories for 'KeyView' named components. Common paths include /opt/keyview, /usr/local/keyview, or C:\Program Files\KeyView. Check version files or DLL properties for versions 10.4 or 10.9.Affected if KeyView version 10.4 or 10.9 is found installed on the system
-
Identify wkssr.dll presenceSearch for the file wkssr.dll in KeyView installation directories. This is the Lotus 123 spreadsheet reader component that contains the vulnerability.Affected if wkssr.dll exists in the KeyView installation path, confirming the vulnerable component is present
-
Verify Lotus 123 file processing capabilityCheck application logs, configuration files, or API settings to determine if the system is configured to process Lotus 123 (.wk1, .wk3, .wk4) spreadsheet files. This may be in filter configuration, export settings, or viewer preferences.Affected if Lotus 123 file processing is enabled or available in the KeyView configuration
If KeyView SDK versions 10.4 or 10.9 are installed with the wkssr.dll component and Lotus 123 file processing is available, the environment is affected by this vulnerability.
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 for affected IBM, Symantec, and other products using vulnerable KeyView versions. Until patches are available, restrict or disable processing of untrusted Lotus 123 files through the affected software.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1524 — 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-1524 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