Vulnerability Note VU#103425

Oracle Outside In CorelDRAW file parser stack buffer overflow

Original Release date: 19 Jul 2011 | Last revised: 28 Apr 2014

Overview

Oracle Outside In contains a stack buffer overflow in the CorelDRAW parser, which can allow a remote, unauthenticated attacker to execute arbitrary code on a vulnerable system.

Description

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 versions 8.3.5.5927 and 8.3.2.5927 and earlier fail to properly handle CorelDRAW data, which is handled by the imcdr2.flt library.

Impact

By causing an application to process a specially-crafted .CDR 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.

Solution

Apply an update

These vulnerabilites are addressed in the Oracle Fusion Middleware Critical Patch Update July 2011. Please see Oracle Support Note 1323616.1 (valid Oracle CSI# required) for more details. If you are using an application that uses Outside In, please check with that application's vendor for updates. If updates for your application are not yet available, or if you wish to mitigate other vulnerabilities in Outside In, 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
AccessDataAffected30 Mar 201103 Aug 2011
ACD Systems InternationalAffected-06 Jul 2012
AvantstarAffected-19 Apr 2011
Cisco Systems, Inc.Affected18 Apr 201127 Oct 2011
GoogleAffected-01 Apr 2014
Guidance Software, Inc.Affected18 Apr 201125 Jul 2011
Hewlett-Packard CompanyAffected19 Apr 201110 May 2011
IBM CorporationAffected18 Apr 201129 Jan 2014
Kamel SoftwareAffected18 Apr 201108 Aug 2011
kcuraAffected-08 Aug 2011
Kroll Ontrack IncAffected21 Apr 201110 May 2011
LucionAffected22 Jul 201126 Aug 2011
MarkLogic CorporationAffected08 Aug 201126 Aug 2011
McAfeeAffected21 Apr 201104 May 2011
NewSoft America IncAffected21 Apr 201110 May 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.0 E:POC/RL:OF/RC:C
Environmental 7.1 CDP:ND/TD:ND/CR:ND/IR:ND/AR:ND

References

Credit

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

This document was written by Will Dormann.

Other Information

  • CVE IDs: CVE-2011-2264
  • Date Public: 19 Jul 2011
  • Date First Published: 19 Jul 2011
  • Date Last Updated: 28 Apr 2014
  • Severity Metric: 17.71
  • Document Revision: 97

Feedback

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