1. Symantec/
  2. Security Response/
  3. Security Updates Detail

Security Advisories Relating to Symantec Products - Symantec Enterprise Vault Update for Oracle Outside In Module


September 1, 2011

Revision History





CVSS2 Base Score: 8.31

Impact 8.54, Exploitability 8.58

CVSS2 Vector:  AV:N/AC:M/Au:N/C:P/I:P/A:C

Exploit Publicly Available:  No


Symantec is updating the Oracle Outside In module in supported versions of the Symantec Enterprise Vault product suite.  These Oracle Outside In updates address potential denial of service and possible remote code execution susceptibility.


Product(s) Affected




Symantec Enterprise Vault product suite



Apply available hotfix 


Apply available hotfix 

8.0 SP5

Apply available hotfix 

Prior to 8.0 SP5

Upgrade to 8.0 SP5 and apply available hotfix 



CERT notified Symantec of vulnerabilities they had identified in the Oracle Outside In component, used by Symantec Enterprise Vault product suite to convert data for archiving purposes. These issues could potentially result in a denial of service in the application or the possibility of arbitrary code running in the context of the affected application.  In the Symantec Enterprise Vault product suite, attempted exploitation of these issues would require an email with a malicious attachment to be processed for archiving to trigger any type of exploit attempt.   


Symantec Response

Symantec has released updates to Symantec’s Enterprise Vault product suite to address these issues. Symantec recommends all Enterprise Vault product suite customers download and apply the hotfixes identified above as soon as possible to prevent threats of this nature.


Symantec is not aware of any exploitation of, or adverse customer impact from this issue.

Best Practices


As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.
  • Disable remote access or restrict it to trusted/authorized systems only.
  • Keep all operating systems and applications updated with the latest vendor patches.
  • Follow a multi-layered approach to security. Run both firewall and anti-malware applications, at a minimum, to provide multiple points of detection and protection to both inbound and outbound threats.
  • Deploy network and host-based intrusion detection systems to monitor network traffic for signs of anomalous or suspicious activity. This may aid in detection of attacks or malicious activity related to exploitation of latent vulnerabilities


Symantec thanks Will Dormann with CERT/CC for identifying these issues to us.







Symantec takes the security and proper functionality of our products very seriously. As founding members of the Organization for Internet Safety (OISafety), Symantec supports and follows responsible disclosure guidelines.
Symantec has developed a Software Security Vulnerability Management Process document outlining the process we follow in addressing suspected vulnerabilities in our products.
Symantec Corporation firmly believes in a proactive approach to secure software development and implements security review into various stages of the software development process. Additionally, Symantec is committed to the security of its products and services as well as to its customers’ data. Symantec is committed to continually improving its software security process.
This document provides an overview of the current Secure Development Lifecycle (SDLC) practice applicable to Symantec’s product and service teams as well as other software security related activities and policies used by such teams. This document is intended as a summary and does not represent a comprehensive list of security testing and practices conducted by Symantec in the software development process.
Please contact secure@symantec.com if you believe you have discovered a security issue in a Symantec product. A member of the Symantec Software Security team will contact you regarding your submission to coordinate any required response. Symantec strongly recommends using encrypted email for reporting vulnerability information to secure@symantec.com.
The Symantec Software Security PGP key can be found at the following location:
Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Software Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.
Last modified on: September 1, 2011
Security Response Blog
The State of Spam