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

Security Advisories Relating to Symantec Products - Symantec System Recovery 2011 and Backup Exec System Recovery 2010 DLL Loading


July 20, 2012

Revision History


CVSS2 Base Score



CVSS2 Vector

DLL Loading Remote Code Execution - Medium







Backup Exec System Recovery 2010 and Symantec System Recovery 2011 are susceptible to potential dll loading due to improper path restrictions in system file directories. Successful exploitation could result in an attacker being able to execute arbitrary code with logged-in user permissions.

Affected Products




Backup Exec System Recovery 2010


Upgrade to Backup Exec System Recovery 2010 SP5

Symantec System Recovery 2011


Upgrade to Symantec System Recovery 2011 SP2



Symantec was notified of potential dll loading due to improper path restrictions in file directories installed with Backup Exec System Recovery 2010 and Symantec System Recovery 2011.  The Granular Restore Option directory and the Recovery Point Browser directory do not properly restrict the loading of external libraries.  An unauthorized local user with access to the system could potentially insert a specifically-crafted file in one of the susceptible directory. An attacker with access to the network would then need to entice an authorized user to load a specifically formatted file from an alternate file location or network share.  Successful exploitation could allow unauthorized arbitrary code to be executed with logged-on user permissions.

Symantec Response

Symantec product engineers verified that the vulnerability exists in the versions of Backup Exec System Recovery and Symantec System Recovery indicated above. Additionally, Symantec engineers reviewed related functionality to further enhance overall product security.

Symantec has determined that one of the affected files indentified as a vector for the issue reported in the Granular Restore Library, "imapi.dll" is not a file that Symantec ships and installs with either Backup Exec System Recovery 2010 or Symantec System Recovery 2011.  The Symantec products make use of the imapi.dll version installed with the underlying operating system. 

NOTE:  Symantec research determined that the presence of an older version of the imapi.dll could potentially be leveraged in this type of attack on the Granular Restore Library.  Microsoft upgraded the original imapi.dll to imapiv2 with shipping versions of Windows Vista and Windows 7.  Microsoft released Microsoft Hotfix 932716, http://support.microsoft.com/kb/932716, to upgrade imapi to imapiv2 for Windows XP SP2/SP3 and Windows Server 2003. 

Customers should ensure that they upgrade to the Backup Exec System Recovery 2010 SP5 or Symantec System Recovery 2011 SP2 updates indicated above. Customers should also ensure Microsoft Hotfix 932716 has been successfully applied on their operating system.  

Symantec knows of no exploitation of or adverse customer impact from this issue.

Update Information

Customers may obtain Backup Exec System Recovery 2010 SP5 or Symantec System Recovery 2011 SP2 through their normal support/download locations.

Best Practices

As a part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.
  • Restrict remote access, if required, to trusted/authorized systems only.
  • Run under the principle of least privilege where possible to limit the impact of exploit by threats.
  • 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 credits Nenad Stojanovski, for identifying this and working with us while Symantec resolved the issue.


BID: Security Focus, http://www.securityfocus.com, has assigned a Bugtraq IDs (BIDs) to the

 issue for inclusion in the Security Focus vulnerability database.

CVE: The issue is a candidate for inclusion in the CVE list (http://cve.mitre.org), which standardizes names for security problems. 







BID 54594

dll loading command execution


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: July 20, 2012
Security Response Blog
The State of Spam