-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

===========================================================================
             AUSCERT External Security Bulletin Redistribution

                               ESB-2015.1724
  Security Advisories Relating to Symantec Products - Symantec Data Loss
        Prevention Enforce Server Administration Console Cross-site
               Scripting, Cross-site Request Forgery Issues
                               30 June 2015

===========================================================================

        AusCERT Security Bulletin Summary
        ---------------------------------

Product:           Symantec Data Loss Prevention Enforce Server
Publisher:         Symantec
Operating System:  Red Hat
                   Windows
Impact/Access:     Cross-site Scripting       -- Remote with User Interaction
                   Cross-site Request Forgery -- Remote with User Interaction
Resolution:        Patch/Upgrade
CVE Names:         CVE-2015-1485 CVE-2014-9230 

Original Bulletin: 
   https://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=&suid=20150622_00

- --------------------------BEGIN INCLUDED TEXT--------------------

Security Advisories Relating to Symantec Products - Symantec Data Loss 
Prevention Enforce Server Administration Console Cross-site Scripting, 
Cross-site Request Forgery Issues

SYM15-006

June 22, 2015

Revisions

None

Severity

CVSS2		Impact		Exploitability		CVSS2 Vector
Base Score	

Symantec Data Loss Prevention Enforce Server administration console XSS - Medium

5.1		6.4		4.9			AV:N/AC:H/Au:N/C:P/I:P/A:P

Symantec Data Loss Prevention Enforce Server administration console CSRF - Medium

5.1		6.4		4.9			AV:N/AC:M/Au:N/C:P/I:P/A:P

Overview

Symantec's Data Loss Prevention (DLP) Management Console is potentially 
susceptible to persistent cross-site scripting (XSS) issues and a possible 
cross-site request forgery (CSRF) in the Enforce Server administration 
console. Successful exploitation could result in potential unauthorized 
actions directed against the console potentially with elevated privileges.

Affected Products

Product					Version			Solution(s)

Symantec Data Loss Prevention		12.5.1 and prior	Migrate to Symantec Data 
								Loss Prevention 12.5.2 or 
								later release

Details

Symantec was notified of XSS issues as well as possible CSRF issues within the
Symantec Data Loss Prevention Enforce Server administration console. 
Additionally, Symantec DLP engineers have been doing extensive internal 
reviews that identified and addressed other areas susceptible to similar 
issues.

Both XSS and CSRF issues are the result of insufficient validation/sanitation
of user input and server output. A successful exploitation of these issues in
Enforce Server administration console pages used to manage DLP is possible 
should a properly authenticated user click on a maliciously-crafted link. 
Depending on the nature of the link it is possible for execution of arbitrary
html requests and scripts in the context of the targeted user. The 
administration console normally allows access to only specified 
users/administrators with varying levels of access depending on their 
requirements.

Cross-site scripting and cross-site request forgery are trust exploitations 
requiring enticing a previously authenticated user to click on a link in a 
context such as a website URL or an HTML email. To be exposed to other than 
another authorized network user, an external attacker would need to 
successfully entice an authorized, privileged or limited-access Enforce Server
console user to visit a malicious web site or click on a malicious HTML link 
in an email in any attempts to take advantage of this issue.

In a typical installation the Symantec Data Loss Prevention Enforce Server 
administration console should not be accessible external to the network 
environment and access should be restricted to specified users/administrators.
Web browsers used by authorized users to manage Symantec Data Loss Prevention
Enforce Server should never be used for casual browsing of external web sites
during an active administrative session. These restrictions greatly reduce 
exposure to external attempts of this type.

Symantec Response

Symantec engineers have verified and addressed these external submissions as 
well as those identified through internal reviews. Symantec strongly 
recommends Symantec Data Loss Prevention customers update to the latest 
release of Symantec Data Loss Prevention as indicated in the above product 
table. Symantec knows of no exploitation of or adverse customer impact from 
these issues.

Symantec Data Loss Prevention 12.5.2 and 14.0 are currently available through
customer normal download channels.

Mitigation/Workaround

Since exploitation depends on user interaction (phishing, clicking on 
untrusted html link), customers are strongly encouraged to follow security 
best practices.

Specifically, during an active DLP administration session:

Avoid casual surfing in different tabs of the browser session

Avoid clicking html links in emails or any other electronic document that may
launch an additional browser instance

Best Practices

Symantec strongly recommends as part of normal best practices:

Restrict access to administration or management systems to privileged users.

Avoid casual surfing in different tabs when using the browser to administer 
systems.

Do not click on html links in emails.

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.

Credit

Symantec would like to thank Mike Czumak (@SecuritySift) for reporting XSS and
CSRF issues; Pieter Hiele for reporting XSS issues and both for coordinating 
with us as we resolved them.

References

BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq ID 
(BID) to these issues for inclusion in the Security Focus vulnerability 
database.

CVE: These issues are candidates for inclusion in the CVE list 
(http://cve.mitre.org), which standardizes names for security problems.

CVE		BID	Description

CVE-2014-9230	75288	Symantec Data Loss Prevention Enforce Server administration console XSS

CVE-2015-1485	75289	Symantec Data Loss Prevention Enforce Server administration console CSRF

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.

Please contact secure@symantec.com if you feel you have discovered a security
issue in a Symantec product. A member of the Symantec Product 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 Product 
Security PGP key can be found at the location below.

Symantec has developed a Product Vulnerability Response document outlining the
process we follow in addressing suspected vulnerabilities in our products. 
This document is available below.

Symantec Vulnerability Response Policy

 Symantec Product Vulnerability Management PGP Key Symantec Product 
Vulnerability Management PGP Key

Copyright (c) 2015 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 Product Security. 
Reprinting the whole or part of this alert in any medium other than 
electronically requires permission from secure@symantec.com

Disclaimer

The information in the advisory is believed to be accurate at the time of 
publishing based on currently available information. Use of the information 
constitutes acceptance for use in an AS IS condition. There are no warranties
with regard to this information. Neither the author nor the publisher accepts
any liability for any direct, indirect, or consequential loss or damage 
arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Product Security, and 
secure@symantec.com are registered trademarks of Symantec Corp. and/or 
affiliated companies in the United States and other countries. All other 
registered and unregistered trademarks represented in this document are the 
sole property of their respective companies/owners.

* Signature names may have been updated to comply with an updated IPS 
Signature naming convention. See 
http://www.symantec.com/business/support/index?page=content&id=TECH152794&key=54619&actp=LIST
for more information.

Last modified on: June 22, 2015

- --------------------------END INCLUDED TEXT--------------------

You have received this e-mail bulletin as a result of your organisation's
registration with AusCERT. The mailing list you are subscribed to is
maintained within your organisation, so if you do not wish to continue
receiving these bulletins you should contact your local IT manager. If
you do not know who that is, please send an email to auscert@auscert.org.au
and we will forward your request to the appropriate person.

NOTE: Third Party Rights
This security bulletin is provided as a service to AusCERT's members.  As
AusCERT did not write the document quoted above, AusCERT has had no control
over its content. The decision to follow or act on information or advice
contained in this security bulletin is the responsibility of each user or
organisation, and should be considered in accordance with your organisation's
site policies and procedures. AusCERT takes no responsibility for consequences
which may arise from following or acting on information or advice contained in
this security bulletin.

NOTE: This is only the original release of the security bulletin.  It may
not be updated when updates to the original are made.  If downloading at
a later date, it is recommended that the bulletin is retrieved directly
from the author's website to ensure that the information is still current.

Contact information for the authors of the original document is included
in the Security Bulletin above.  If you have any questions or need further
information, please contact them directly.

Previous advisories and external security bulletins can be retrieved from:

        http://www.auscert.org.au/render.html?cid=1980

===========================================================================
Australian Computer Emergency Response Team
The University of Queensland
Brisbane
Qld 4072

Internet Email: auscert@auscert.org.au
Facsimile:      (07) 3365 7031
Telephone:      (07) 3365 4417 (International: +61 7 3365 4417)
                AusCERT personnel answer during Queensland business hours
                which are GMT+10:00 (AEST).
                On call after hours for member emergencies only.
===========================================================================
-----BEGIN PGP SIGNATURE-----
Comment: http://www.auscert.org.au/render.html?it=1967

iQIVAwUBVZInSn6ZAP0PgtI9AQLHOg//boad/x31kBDJQ2FywClXA1Qlo8+BStJ4
Zp2DvPOfMvbQWiY7r1JDKSOeq50AWE7R3x4bufXBtGYxM8L+13EPGreOEUPllhnM
He5efkmDCzSjv2BZ5NWt7+REzGh37BoCw1xyEp4KZ/Kk5lN3vi9Pz4VhDY2TZW9m
q6LEMV1kA0Ml9BkAl/yJ0J9pmntD4XCrMz5FOVEJY74yzVd2b2mLgGCw3hwogAdk
C1rWMPNROiN/Kso7K9CSiuDwM6UtZeDPSn46oCAJPlLsTBbnNlI2FcqZEyqfURVt
L81t9T38Nis17a13diYfC6DEgQ527a8WsAmWKQhnH6tVoEI7wZBgq97QhOefZ+qJ
oDWXFyBWWKSa2sZaFAFVcIvsE+jQLriuNjY21oyL5Pn/Ldj2aPhC7rXJz1aWJYXA
GVbFceagtweIbzHSSkfe5VV4wHY1TDbC/jItyvxbdct/tn+oeg7zV7YvVvBOYpYC
V1zmv5ZGdYgFz+AM2fvbbnGuhhv6Ly6FEzo71yw96smmFc+VTaA/KDNZVV0ZrjDe
FNC3TMbOoPFHwhdOcmsV/kg2SWZwXDrFt4vJwe3jhA+y2gYVsDyMf8Kd7Q6ITdw6
+CykVaVMLFSSTDzJskqxQuymVJf1yvUcmHXXAqNcLYYDCxNyd2a6hjyN1fHP86XV
KFaYvxHC2qY=
=gJ/G
-----END PGP SIGNATURE-----