CVE-2010-0126
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 an unspecified library 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 a crafted compound file, as demonstrated using a Quattro Pro file, which is not properly handled by the Quattro speed reader (qpssr.dll).
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 confidenceHeap-based buffer overflow in the Quattro speed reader (qpssr.dll) in Autonomy KeyView 10.4 and 10.9 allows remote code execution via crafted Quattro Pro compound files. The vulnerability occurs when parsing maliciously constructed Quattro Pro files, leading to heap memory corruption that can be exploited to 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.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.
-
Identify KeyView installation and versionSearch for Autonomy KeyView SDK installations by checking common installation directories (e.g., C:\Program Files\Autonomy\KeyView\ or /opt/keyview/) and look for version information in product documentation, license files, or registry entries under HKEY_LOCAL_MACHINE\SOFTWARE\Autonomy\KeyView. Also check any application that embeds KeyView for version details.Affected if The installed version is exactly 10.4 or 10.9
-
Locate the vulnerable qpssr.dll componentSearch the KeyView installation directory for the file qpssr.dll (Quattro speed reader). Use file system search or commands like 'dir /s qpssr.dll' on Windows or 'find . -name qpssr.dll' on Unix-like systems.Affected if qpssr.dll exists in the KeyView installation directory, indicating the Quattro Pro parsing module is present
-
Verify Quattro Pro file parsing is enabledCheck KeyView configuration files (typically keyview.ini, kvconfig.xml, or similar) for settings related to Quattro Pro file handling. Look for parameters like 'EnableQuattroPro', 'QuattroFilter', or 'qpw' file type registration. Also check if the file filter for Quattro Pro (.qpw, .wb, .wq) is loaded.Affected if Quattro Pro file parsing or filtering is enabled in the KeyView configuration, allowing processing of .qpw or related file types
-
Inspect recent file processing activityReview application logs, KeyView audit logs, or proxy/email gateway logs for recent processing of Quattro Pro files (.qpw, .wb, .wq extensions). Check if the system accepts or filters Quattro Pro attachments from external sources.Affected if The system has recently processed or is configured to process untrusted Quattro Pro files from external sources
You are affected if Autonomy KeyView version 10.4 or 10.9 is installed with the qpssr.dll component present and Quattro Pro file parsing is enabled, allowing the system to process untrusted Quattro Pro compound files.
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 the vendor patch for Autonomy KeyView when available, or upgrade to a patched version. Until then, disable or restrict processing of untrusted Quattro Pro files in affected products and implement network-level filtering for these file types.
- Consultation6.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-0126 — 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-0126 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