Protect yourself against future threats.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2014.0190
Symantec Web Gateway Security Management Console Multiple Security Issues
12 February 2014
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Symantec Web Gateway Appliance
Publisher: Symantec
Operating System: Network Appliance
Impact/Access: Cross-site Scripting -- Remote with User Interaction
Modify Arbitrary Files -- Existing Account
Resolution: Patch/Upgrade
CVE Names: CVE-2013-5013 CVE-2013-5012
Original Bulletin:
http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&year=&suid=20140210_00
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Advisories Relating to Symantec Products - Symantec Web Gateway
Security Management Console Multiple Security Issues
SYM14-003
February 10, 2014
Revisions
None
Severity
CVSS2 Base Score Impact Exploitability CVSS2 Vector
Unauthenticated XSS in .php scripts - High
7.5 6.4 10 AV:N/AC:L/Au:N/C:P/I:P/A:P
Authenticated Access XSS - Medium
4.0 6.4 2.5 AV:L/AC:L/Au:M/C:P/I:P/A:P
Authenticated Access SQL Injections Medium
6.5 10 2.5 AV:L/AC:L/Au:M/C:C/I:C/A:C
Overview
Symantec Web Gateway (SWG) Appliance management console is susceptible to both
local and remote access cross-site scripting (XSS) and local access SQL
injection (sqli) vulnerabilities. Successful exploitation may result in an
authorized user gaining unauthorized access to files on the management console
or possibility being able to manipulate the backend data base. There is also
potential for remote hijacking of an authorized user session with associated
privileges.
Product(s) Affected
Product Version Solution
Symantec Web Gateway Appliance 5.1.1 and prior Symantec Web Gateway 5.2
NOTE: Customers should always ensure they are running the latest data base
updates available
Details
Symantec was notified of security issues impacting the Symantec Web Gateway
management console. The results of successful exploitation could potentially
range from a user with authorized access to the management console gaining
unauthorized access to sensitive data or another users account to unauthorized
manipulation of the backend application database.
Local access SQL injection issues were identified allowing an authenticated
Symantec Web Gateway user to make unauthorized database queries. Successful
targeting could potentially result in unauthorized disclosure of privileged
information and/or possible unauthorized manipulation of the backend database.
Symantec Web Gateway in certain cases does not properly validate/sanitize
external input allowing the potential of cross-site scripting attempts by both
authorized but non-privileged and in some instances unauthorized individuals.
Successful targeting of these issues could result in unauthorized access by an
authorized but unprivileged user or potentially allowing an unauthorized
individual to hijack an authorized Symantec Web Gateway user session with
associated privileges.
Symantec Response
Symantec engineers validated these submissions, having also identified these
types of issues during internal testing. An updated Symantec Web Gateway
version, 5.2, has been released to address them. Symantec Web Gateway 5.2 is
currently available to customers through normal support locations. Symantec is
not aware of exploitation of or adverse customer impact from this issue.
Customers should ensure they are on the latest release of Symantec Web Gateway
5.2 and running the latest data base update. To confirm customers are running
the latest updates check the Current Software Version -> Current Version on
the Administration->Updates page. Alternatively, customers can click the Check
for Updates button on the Administration->Updates page to verify that they are
running the latest software version.
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.
* The Symantec Web Gateway software and any applications that are installed on
the Symantec Web Gateway can ONLY be updated with authorized and tested
versions distributed by Symantec.
* 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 thanks Shaun Bertrand, Creative Breakthroughs Inc, for reporting the
local access XSS and SQLi issues; Comrade Polar Bear for reporting an
unauthenticated XSS issue; and William Costa, william.costa@gmail.com, for
reporting an unauthenticated XSS issue. Symantec thanks all of them for
working with us as we resolved their findings.
References
BID: Security Focus, http://www.securityfocus.com, has assigned Bugtraq IDs
(BIDs) 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-2013-5012 BID 65404 SQL Injection
CVE-2013-5013 BID 65405 Cross-Site Scripting
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.
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 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: February 10, 2014
- --------------------------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
iQIVAwUBUvsGlhLndAQH1ShLAQKwDA//Uo+q3ruUvKKGSwHmD3Krs9Phllchhj8A
IkW282ECNSVjz1leIMwniKRF6pCyZAULDqPLffBUfeOYGfhHVdR6QjEeR1jahvcI
eZOkzkGHrNtSFHR+Vm9U2hjg1nLUhuKHmNc6Jo+9zRB0h52rWn5sLxPBQaUrAAXC
nkdCMkKwadI9tWH2oZ/vV7Tgf4EvcB0Ax6Xyu50cqNnYnwV4DoLXXow+cuUx7wQv
yJ6Jf2rjOmRZvPZVaOK4em9JPjqeFufF85uSwfolKzrSacuzfEl1u29vSSBTSZTx
hEq1YEtgOqFUhfq7+x6ZvC5jlAja+AVBNAp8fKrl4M5b/ggi8tnxU7XHXCL2Z+q1
8mZ+WsTQAR9KUNrMYJ9nFpWkshn+6CL+fUXlQmn3TTrDiE7/L1NGPGeWm+SAHZl5
FY9qt8fb9ZO3j5lbBnhYZ5+Usvq4AznN/XsQJdn6mRvBM0IGmt6PLKil0mTDVTRv
9rS627zl2zDZrYdFmHLVoUzjRsbutPruxFpwduAAr4rGOGr0nfHGOAfjdRlJpFr2
3iXD4YW+tguZ0CLQMzWR37FlMOVB66O5YBBZInobm8CJzE0ggi+gDITtDKr19LRo
Xys2PAUtQ8bj/uGojjNSdZrL6bqhuOxlRzzb02xCJdn+0SXJnS3raDqtFqLXgrSE
sTAF3dabydE=
=fWjf
-----END PGP SIGNATURE-----