Vulnerability Note VU#126159

Autonomy Keyview IDOL contains multiple vulnerabilities in file parsers

Original Release date: 07 Jun 2011 | Last revised: 04 Jun 2012


Autonomy Keyview IDOL contains multiple vulnerabilities in file parsers. These vulnerabilities could allow a remote attacker to execute arbitrary code on an affected system.


Autonomy Keyview IDOL is a set of libraries that can decode over 1,000 different file formats. The Autonomy Keyview IDOL libraries are used by a variety of applications, including IBM Lotus Notes, Lotus Domino, Symantec Mail Security, Hyland OnBase, and many others. These vulnerabilities result from a number of underlying issues. Some of these cases demonstrated memory corruption with attacker-controlled input and could be exploited to run arbitrary code. For example, code execution was verified by CERT/CC for a stack buffer overflow in the .WRI file parser.


By causing an application to process a specially-crafted file with the Autonomy Keyview IDOL library, a remote, unauthenticated attacker may be able to cause an affected application to crash, resulting in a denial of service, or executing arbitrary code with the privileges of the vulnerable application. Depending on what application is using Keyview IDOL, these may happen as the result of some user interaction, such as single-clicking on a file, or it may happen with no user interaction at all.


Apply an Update

Autonomy has released version 10.13.1 of Keyview IDOL to address these issues.

Autonomy customers can download the update from Autonomy's Customer Support website.

The following versions of Symantec products have been released to address these vulnerabilities. Symantec customers may retrieve these versions through their normal support methods.

    • Symantec Mail Security for Microsoft Exchange 6.5.6 or 6.0.13
    • Symantec Mail Security for Domino 7.5.12 or 8.0.9
    • Symantec Brightmail and Messaging Gateway 9.5.1
    • Symantec Data Loss Prevention 11.1.1
If you are unable to apply an update to address these vulnerabilities please consider the following workarounds.

Use the Microsoft Enhanced Mitigation Experience Toolkit

The Microsoft Enhanced Mitigation Experience Toolkit (EMET) can be used to help prevent exploitation of this and other vulnerabilities.

Enable DEP in Microsoft Windows

Consider enabling Data Execution Prevention (DEP) in supported versions of Windows. DEP should not be treated as a complete workaround, but it can mitigate the execution of attacker-supplied code in some cases. Microsoft has published detailed technical information about DEP in Security Research & Defense blog posts "Understanding DEP as a mitigation technology" part 1 and part 2. DEP should be used in conjunction with the application of patches or other mitigations described in this document.

Note that when relying on DEP for exploit mitigation, it is important to use a system that supports Address Space Layout Randomization (ASLR) as well. ASLR is not supported by Windows XP or Windows Server 2003 or earlier. ASLR was introduced with Microsoft Windows Vista and Windows Server 2008. Please see the Microsoft SRD blog entry: On the effectiveness of DEP and ASLR for more details.

Workaround for IBM Lotus Notes

Delete the keyview.ini file in the Notes program directory (C:\ProgramData\Lotus\Notes\Data\Shared).
This disables ALL viewers. When a user clicks View (for any file attachment), a dialog box will display with the message "Unable to locate the viewer configuration file."

Delete or rename the affected DLL file.
After removing the dll file, when a user tries to view a file that requires that viewer, a dialog box will display with the message "The viewer display window could not be initialized." All other file types work without returning the error message.

Comment out lines in keyview.ini that reference affected DLL file.
To comment a line, you precede it with a semi-colon (;). When a user tries to view the specific file type, a dialog box will display with the message "The viewer display window could not be initialized."

[KVWKBVE] --> this is the section of the keyview.ini
;188=xlssr.dll ---> this would be the result of the Excel dll commented out

Workaround for Symantec Mail Security

Symantec Mail Security is susceptible only if the attachment content scanning option is enabled.

To disable the content filtering rules for Symantec Mail Security for Microsoft Exchange:

    • Select the "Policies" tab and then choose "Content Filtering" to display the list of currently enabled rules
    • Ensure that all rules using attachment content are "disabled"
To disable the content filtering rules for Symantec Mail Security for Domino:
    • Select the "Content Filtering" tab to display the list of current enabled rules
    • Click on the checkmark to the left of any rules that utilize attachment content filtering, changing it to a red "X", and disabling the rule

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
AutonomyAffected03 Feb 201118 Mar 2011
CA TechnologiesAffected-21 Mar 2012
EMC CorporationAffected16 Mar 201130 Mar 2012
Hyland SoftwareAffected18 Mar 201118 Mar 2011
Lotus SoftwareAffected07 Feb 201118 Mar 2011
McAfeeAffected08 Mar 201221 Mar 2012
Palisade SystemsAffected-04 Jun 2012
ProofpointAffected-22 May 2012
SymantecAffected07 Feb 201121 Mar 2012
Trend MicroAffected-22 May 2012
VerdasysAffected-04 Jun 2012
WebSenseAffected29 Mar 201218 Apr 2012
AdobeNot Affected16 Mar 201118 Mar 2011
Cisco Systems, Inc.Unknown16 Mar 201130 Mar 2012
CitrixUnknown16 Mar 201116 Mar 2011
If you are a vendor and your product is affected, let us know.View More »

CVSS Metrics (Learn More)

Group Score Vector
Base 9.0 AV:N/AC:M/Au:N/C:C/I:C/A:P
Temporal 7.4 E:F/RL:OF/RC:C
Environmental 7.4 CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND



These vulnerabilities were reported by Will Dormann and Jared Allar of the CERT/CC.

This document was written by Jared Allar.

Other Information

  • CVE IDs: Unknown
  • Date Public: 07 Jun 2011
  • Date First Published: 07 Jun 2011
  • Date Last Updated: 04 Jun 2012
  • Severity Metric: 50.18
  • Document Revision: 80


If you have feedback, comments, or additional information about this vulnerability, please send us email.