Vulnerability Note VU#738961

Oracle Outside In contains an exploitable vulnerability in Lotus 123 v4 parser

Original Release date: 18 Jan 2012 | Last revised: 28 Apr 2014


Oracle Outside In contains an exploitable vulnerability in the Lotus 123 version 4 file parser, which can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system.


Oracle Outside In is a set of libraries that can decode over 500 different file formats. Originally written by Stellent, Outside In is now part of Oracle. The Oracle Outside In libraries are used by a variety of applications, including Oracle Fusion Middleware, Google Search Appliance, Guidance Encase Forensics, AccessData FTK, and Novell Groupwise.

Outside In fails to properly handle Lotus 123 version 4 file data, which is handled on the Windows platform by the vswk4.dll library. The Linux version of Outside In uses Other supported platforms may use different file names.

Limited testing has shown that the Lotus 123 version 4 parser in Outside in versions prior to and are vulnerable.


By causing an application to process a specially-crafted file with the Oracle Outside In library, a remote, unauthenticated attacker may be able to execute arbitrary code with the privileges of the vulnerable application. Depending on what application is using Outside In, this 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

These vulnerabilites are addressed in the Oracle Fusion Middleware Critical Patch Update January 2012. This update provides the Outside In Lotus 123 version 4 parser versions, and, which address this vulnerability. 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.

Vendor Information (Learn More)

VendorStatusDate NotifiedDate Updated
AccessDataAffected16 Jan 201202 Mar 2012
ACD Systems InternationalAffected-06 Jul 2012
AvantstarAffected-16 Jan 2012
Cisco Systems, Inc.Affected16 Jan 201216 Jan 2012
GoogleAffected-01 Apr 2014
Guidance Software, Inc.Affected16 Jan 201210 May 2012
Hewlett-Packard CompanyAffected16 Jan 201216 Jan 2012
IBM CorporationAffected16 Jan 201229 Jan 2014
Kamel SoftwareAffected16 Jan 201216 Jan 2012
kcuraAffected16 Jan 201216 Jan 2012
Kroll Ontrack IncAffected16 Jan 201216 Jan 2012
LucionAffected16 Jan 201216 Jan 2012
MarkLogic CorporationAffected16 Jan 201231 Jan 2012
McAfeeAffected16 Jan 201216 Jan 2012
NewSoft America IncAffected16 Jan 201216 Jan 2012
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.0 E:POC/RL:OF/RC:C
Environmental 7.1 CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND



This vulnerability was reported by Will Dormann of the CERT/CC.

This document was written by Will Dormann.

Other Information

  • CVE IDs: CVE-2012-0110
  • Date Public: 17 Jan 2012
  • Date First Published: 18 Jan 2012
  • Date Last Updated: 28 Apr 2014
  • Severity Metric: 26.24
  • Document Revision: 27


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