CVE-2010-0126: Buffer Overflow

Published Aug 17, 2010
·
Updated

Heap-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).

Affected Software

6 affected components
Autonomy Keyview Filter Sdk=10.9
Autonomy Keyview Viewer Sdk=10.4
Autonomy Keyview Filter Sdk=10.4
Autonomy Keyview Export Sdk=10.4
Autonomy Keyview Export Sdk=10.9
Autonomy Keyview Viewer Sdk=10.9

Event History

Aug 17, 2010
CVE Published
via MITRE·05:31 PM
Data Sourced
via MITRE·05:31 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2010-0126?

CVE-2010-0126 is considered a high severity vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2010-0126?

To fix CVE-2010-0126, update Autonomy KeyView to version 10.10 or later, which addresses the buffer overflow issue.

3

Who is affected by CVE-2010-0126?

CVE-2010-0126 affects users of Autonomy KeyView versions 10.4 and 10.9 within various products from IBM, Symantec, and others.

4

What type of vulnerability is CVE-2010-0126?

CVE-2010-0126 is classified as a heap-based buffer overflow vulnerability.

5

Can CVE-2010-0126 be exploited remotely?

Yes, CVE-2010-0126 can be exploited remotely through crafted compound files.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203