CVE-2010-0135
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 · uneditedHeap-based buffer overflow in the WordPerfect 5.x reader (wosr.dll), as used in Autonomy KeyView 10.4 and 10.9 and possibly other products, allows remote attackers to execute arbitrary code via unspecified vectors related to "data blocks."
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 confidenceHeap-based buffer overflow vulnerability in wosr.dll (WordPerfect 5.x reader) within Autonomy KeyView 10.4 and 10.9 allows remote attackers to execute arbitrary code via malformed data blocks in WordPerfect 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.
-
Confirm KeyView installationSearch for Autonomy KeyView installation directories or check program files for KeyView components (common paths: /opt/keyview, /usr/keyview, C:\Program Files\Autonomy\KeyView, or check registry for KeyView entries)Affected if KeyView software is present on the system
-
Identify KeyView versionLocate version information in KeyView installation directory, check accompanying version files, or run 'strings wosr.dll | grep -i version' on the wosr.dll file if foundAffected if Installed version is 10.4 or 10.9 specifically
-
Locate vulnerable wosr.dll componentSearch for wosr.dll in KeyView installation directories (typically in /lib, /bin, or /export subdirectories)Affected if wosr.dll file exists and corresponds to version 10.4 or 10.9
-
Verify WordPerfect processing capabilityCheck if WordPerfect filter/export/viewer modules are loaded or available in the KeyView installation - look for associated WordPerfect-related DLLs or configuration files enabling .wpd processingAffected if WordPerfect file processing modules are present and accessible in the KeyView environment
The environment is affected if Autonomy KeyView version 10.4 or 10.9 is installed with the wosr.dll WordPerfect reader component present and functional.
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 patch or upgrade KeyView to a patched version; consider disabling WordPerfect file processing capabilities in KeyView if not required.
- Consultation8.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0135 — 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-0135 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