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

Security Advisories Relating to Symantec Products - Norton Remove and Reinstall DLL Preloading


September 26, 2017

Overview | Issues | Affected Products | Mitigation | Best Practices | Acknowledgements | Revisions




Symantec has released an update to address an issue in the Norton Remove and Reinstall product.


Highest severity issue: Medium
Number of issues: 1


< Back to top




This update applies to the following issues:




Norton Remove & Reinstall DLL Preloading prior to version



< Back to top




Symantec has verified the issues and addressed them in product updates as outlined below.



The following Symantec enterprise products are affected.



Norton Remove & Reinstall prior to version

Upgrade to Norton Remove & Reinstall version


< Back to top





Norton Remove & Reinstall DLL Preloading


BID: 100939

Severity: Medium (CVSSv3: 6.7) AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Impact: Privilege escalation

Exploitation: None

Date patched: September 22, 2017

Norton Remove & Reinstall can be susceptible to a DLL preloading vulnerability. These types of issues occur when an application looks to call a DLL for execution and an attacker provides a malicious DLL to use instead. Depending on how the application is configured, it will generally follow a specific search path to locate the DLL. The vulnerability can be exploited by a simple file write (or potentially an over-write) which results in a foreign DLL running under the context of the application.


< Back to top



This issue was validated by the product team engineers. A Norton Remove & Reinstall update, version, has been released which addresses the aforementioned vulnerability. Note that Norton Remove & Reinstall’s latest release and patches are available to customers through normal support channels or can be downloaded directly from the following URL:


To determine if your version of Norton Remove & Reinstall is susceptible to this vulnerability, please perform the following actions:

  • Open the File properties for NRnR.exe, click on the ‘Details’ tab
  • View the ‘File Version’ entry
  • Upgrade to the patched version as needed depending on existing file version (note that file versions older than are susceptible to this vulnerability)

At this time, Symantec is not aware of any exploitations or adverse customer impact from these issues.


< Back to top



Symantec recommends the following measures to reduce risk of attack:

  • Restrict access to administrative or management systems to authorized privileged users.
  • Restrict remote access to trusted/authorized systems only.
  • Run under the principle of least privilege, where possible, to limit the impact of potential exploit.
  • Keep all operating systems and applications current with vendor patches.
  • Follow a multi-layered approach to security. At a minimum, run both firewall and anti-malware applications to provide multiple points of detection and protection for 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 the detection of attacks or malicious activity related to the exploitation of latent vulnerabilities.


< Back to top



  • Kushal Arvind Shah of Fortinet's FortiGuard Labs: kshah@fortinet.com (CVE-2017-13676)


< Back to top



-          None


< Back to top


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 26, 2017
Security Response Blog
The State of Spam