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

Security Advisories Relating to Symantec Products - Symantec Enterprise Vault Updates Oracle Outside-In Libraries


September 28, 2012

Revision History






Base Score



CVSS2 Vectors







Symantec updated the Oracle Outside-In module in the Symantec Enterprise Vault product suite.  The Oracle Outside-In updates address potential denial of service and possible remote code execution susceptibility.


Product(s) Affected




Symantec Enterprise Vault product suite


10.x and prior

Update to 10.0.2



CERT notified Symantec of vulnerabilities identified in the Oracle Outside-In component.  Symantec was already aware of security issues being reported in this module and implemented the updates as soon as it was made available by the vendor.


Oracle’s Outside-In module is used by Symantec Enterprise Vault product suite to convert data for indexing purposes. These reported issues in Oracle’s Outside-In libraries, if successfully exploited, may potentially result in a denial of service in the application or allow 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 downloaded and stored in a user’s mail box until processed for archiving in order to present any potential for malicious activity attempts.   


Symantec Response

Symantec has released an update to Symantec’s Enterprise Vault product suite to address these issues. Symantec recommends all Symantec Enterprise Vault product suite customers upgrade to Symantec Enterprise Vault 10.0.2 to address any possibility of threats of this nature. 


Symantec Enterprise Vault 10.0.2 is currently available through normal update channels.




Symantec Enterprise Vault product suite enables Data Execution Prevention (DEP) as well as Address Space Layout Randomization (ASLR) in supported versions of Windows to further mitigate successful attempts against these types of issues.


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


Will Dormann with CERT.org initially identified 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.
Please contact secure@symantec.com if you feel you have discovered a security issue in a Symantec product. A member of the Symantec Product 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 Product Security PGP key can be found at the location below.
Symantec has developed a Product Vulnerability Response document outlining the process we follow in addressing suspected vulnerabilities in our products. This document is available below.

Copyright (c) by Symantec Corp.

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Product Security. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.
Symantec, Symantec products, Symantec Product Security, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.
* Signature names may have been updated to comply with an updated IPS Signature naming convention. See http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST for more information.
Last modified on: September 28, 2012
Security Response Blog
The State of Spam