Symantec Endpoint Encryption Client Memory Dump Information Disclosure

Endpoint Encryption

0 more products

1339

05 March 2020

14 December 2015

CLOSED

LOW

3.8

SUMMARY

 

Symantec’s Endpoint Encryption (SEE) Client is susceptible to information disclosure if a user with access to a system hosting a client is able to force a client memory dump and access the content of the memory dump. This could result in unauthorized exposure of such things as stored credentials used by the client in communicating with components of the SEE management server (SEEMS).

AFFECTED PRODUCTS

 

Symantec Endpoint Encryption

CVE

Affected Version(s)

Remediation

CVE-2015-6556

Prior to 11.0

Upgrade to 11.0

 

ISSUES

 

CVE-2015-6556

Severity/CVSSv3:

Low / 3.8 AV:A/AC:M/Au:S/C:P/I:P/A:N

References:

Impact:

Securityfocus: BID 78803  / NVD: CVE-2015-6556

Memory dump information disclosure

Description:

Symantec was notified of an information disclosure isse in SEE clients. An authorized but unprivileged client user with SEE installed on their system who can force and access a memory dump of the SEE Framework Service, EACommunicatorSrv.exe, may have unauthorized access to credentials stored on the client such as the Domain user credentials protecting the SEEMS web service. This could potentially allow an unprivileged user to attempt unauthorized access to additional systems hosting other clients through web services. This access is dependent on the privileges afforded to the Domain user credentials.

 

MITIGATION

 

Symantec Response

Symantec product engineers fully addressed these issues in SEE 11.1.0. Recommend customer upgrade to the latest release of SEE to prevent any potential impact from this issue.

NOTE: SEEMS installation/security configuration documentation has always recommended Domain user credentials NOT have logon privileges.

Symantec is not aware of exploitation of or adverse customer impact from this issue.

 

Update information

Symantec Endpoint Encryption 11.1.0 is available through Symantec File Connect.

 

Best Practices

As part of normal best practices, Symantec strongly recommends:

  • Restrict access to administration or management systems to privileged users.

  • Disable remote access if not required or restrict it to trusted/authorized systems only.

  • Where possible, limit exposure of application and web interfaces to trusted/internal networks 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

ACKNOWLEDGEMENTS

 

Symantec thanks Julio Auto, Principal Information Security Engineer at Mayo Clinic, for reporting this and working with us as we addressed it.