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

Security Advisories Relating to Symantec Products - Norton Core Command Injection


April 30, 2018

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




Symantec has released an update to address one issue in the Norton Core product.


Highest severity issue: High
Number of issues: 1


< Back to top




This update applies to the following issues:




Norton Core Command Injection



< Back to top




Symantec has verified the issue and addressed it in product update as outlined below.



The following Symantec product(s) are affected. 



Norton Core prior to


Norton Core has been automatically upgraded to v237. No action is required.


< Back to top





Norton Core Command Injection


BID: 103955

Severity: High (CVSSv3: 8.0) (AV:A/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H)

Impact: Command Injection

Exploitation: None

Date patched: April 30, 2018

The Norton Core router may be susceptible to a command injection exploit. This is a type of attack in which the goal is execution of arbitrary commands on the host system via vulnerable software.


< Back to top



The issue was validated by the product team engineers. A Norton Core update, v237, has been released which addresses the aforementioned issue. Note that Norton Core updates are received to devices automatically via firmware updates to the router. 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:

  • To ensure that Norton Core stays up to date, keep it powered on and connected to the internet
  • Maintain an active Norton subscription
  • Enable Multi-Factor Authentication (MFA) on the Norton Account associated with Norton Core
  • Ensure that the Norton Core app on your mobile device is up-to-date
  • Use strong WiFi passwords
  • Use recommended strong encryption options for the WiFi network, such as WPA-2 (AES)
  • Use recommended DNS services, such as those offered by DNSSEC DNS providers
  • Limit or avoid the use of UPnP from Norton Core
  • Limit or avoid the use of Port Forwarding from Norton Core
  • Limit or avoid the use of daisy-chained routers with Norton Core
  • Avoid risky web behavior, such as visiting or downloading software from untrusted websites
  • Use security software such as Norton Security on all devices that support it


< Back to top




  • Alexander Rumyantsev (a.rumyantsev@embedi.com) from Embedi (CVE-2018-5234)


< 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: April 30, 2018
Security Response Blog
The State of Spam