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

Security Advisories Relating to Symantec Products - Symantec Encryption Desktop DoS

SYM17-008

September 7, 2017

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

 

 

OVERVIEW

Symantec has released an update to address an issue in the Symantec Encryption Desktop product.

 

Highest severity issue: Medium
Number of issues: 1

 

< Back to top

 

 

ISSUES

This update applies to the following issues:

TITLE

CVE

SEVERITY

Symantec Encryption Desktop DoS prior to SED 10.4.1MP2

CVE-2017-6330

Medium

< Back to top

 

 

AFFECTED PRODUCTS

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

 

Enterprise

The following Symantec enterprise products are affected.

PRODUCT

SOLUTION

Symantec Encryption Desktop prior to SED 10.4.1MP2

Upgrade to Symantec Encryption Desktop SED 10.4.1MP2

 

< Back to top

 

 

ISSUE DETAILS

 

Symantec Encryption Desktop Denial of Service

CVE-2017-6330

BID: 100552

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

Impact: Denial of service

Exploitation: None

Date patched: September 6, 2017
 

A Denial of Service (DoS) attack, is a type of attack whereby the perpetrator attempts to make a particular machine or network resource unavailable to its intended users by temporarily or indefinitely disrupting services of a specific host within a network. DoS attacks can occur when a system becomes flooded with specific network requests or subversive operations that can cause the resourced system to become unresponsive.

 

 

< Back to top

 

 

MITIGATION

This issue was validated by the product team engineers. A Symantec Encryption Desktop update, version SED 10.4.1MP2, has been released which addresses the aforementioned vulnerability. Note that the Symantec Encryption Desktop’s latest release and patches are available to customers through normal support channels. At this time, Symantec is not aware of any exploitations or adverse customer impact from these issues.

 

< Back to top

 

 

BEST PRACTICES

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

 

 

ACKNOWLEDGEMENTS

  • Kyriakos Economou (@kyREcon) on behalf of Nettitude: https://www.nettitude.com/ (CVE-2017-6330)

 

< Back to top

 

 

REVISIONS

-          None

 

< Back to top

 

REPORTING VULNERABILITIES TO SYMANTEC

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