Date: 24 July 2012
Click here for printable version
Click here for PGP verifiable version
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
===========================================================================
AUSCERT External Security Bulletin Redistribution
ESB-2012.0697
Symantec Web Gateway Multiple Security Issues
24 July 2012
===========================================================================
AusCERT Security Bulletin Summary
---------------------------------
Product: Symantec Web Gateway
Publisher: Symantec
Operating System: Windows
UNIX variants (UNIX, Linux, OSX)
Impact/Access: Execute Arbitrary Code/Commands -- Remote/Unauthenticated
Denial of Service -- Remote/Unauthenticated
Unauthorised Access -- Existing Account
Resolution: Patch/Upgrade
CVE Names: CVE-2012-2977 CVE-2012-2976 CVE-2012-2961
CVE-2012-2957 CVE-2012-2953 CVE-2012-2574
Original Bulletin:
http://www.symantec.com/security_response/securityupdates/detail.jsp?fid=security_advisory&pvid=security_advisory&suid=20120720_00
- --------------------------BEGIN INCLUDED TEXT--------------------
Security Advisories Relating to Symantec Products - Symantec Web Gateway
Security Issues
SYM12-011
July 20, 2012
Revisions
None
Severity
CVSS2 Impact Exploitability CVSS2 Vector
Base Score
Remote command execution - High
8.33 10.0 6.45 AV:A/AC:L/Au:N/C:C/I:C/A:C
SQL Injection - High
8.3 10 6.5 AV:A/AC:L/Au:N/C:C/I:C/A:C
Arbitrary Password Change - High
8.3 10 6.5 AV:A/AC:L/Au:N/C:C/I:C/A:C
Exploit Code Publicly Available: No
Overview
Symantec's Web Gateway management console is susceptible to multiple
security issues that include remote command execution, local file
inclusion, arbitrary password change and SQL injection security
issues. Successful exploitation could result in unauthorized command
execution on or access to the management console and backend database.
Product(s) Affected
Product Version Solution
Symantec Web Gateway 5.0.x.x Symantec Web Gateway 5.0.3.18 or later
apply database update 5.0.0.438 or later
Details
CERT/CC notified Symantec of multiple security issues impacting the
management console of Symantec Web Gateway. The management console does
not properly validate external input. This incomplete input validation
could possibly allow unauthorized remote access with the potential of
arbitrary command execution on the console.
Additionally, an unprivileged user with local access to the management
console could potentially manipulate local files to further leverage an
identified authentication bypass vulnerability possibly resulting in
privileged access on the console.
Arbitrary code could potentially be injected/included in multiple
application scripts used by the Symantec Web Gateway application
possibly resulting in arbitrary command execution with application
privileges. One such script can be manipulated to allow an
unauthorized user to change any authorized user's password, effectively
locking out that user and possibly leveraging unauthorized access in
the context of the affected user.
Multiple SQL injection issues were also identified. The successful
exploitation of these could potentially result in arbitrary SQL command
input to the backend database.
In a normal installation, the Symantec Web Gateway management interface
should not be externally accessible from the network environment.
However, an authorized but unprivileged network user or an external
attacker able to successfully leverage network access could attempt to
exploit these weaknesses.
Symantec Response
Symantec engineers verified these issues and have released an update to
address them. Symantec engineers continue to review related
functionality to further enhance the overall security of Symantec Web
Gateway. Symantec has released Symantec Web Gateway Database Update
5.0.0.438 to address these issues. Customers should ensure they are on
the latest release of Symantec Web Gateway, 5.0.3.18 or later with the
Database Update 5.0.0.438 or later.
Obtaining the Update
The security update addressing these issues has been pushed to
customers as an immediately available update. For customers with
automatic updating enabled the update will automatically be applied.
Customers that do not have automatic updating enabled will need to
manually apply the update by clicking "Check for Updates -> Updates" on
the Administration->Updates page for Web Gateway Database Updates and
Web Gateway Software Updates.
To confirm customers are running the latest updates they should 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.
NOTE: Symantec is currently aware that some of these attack vectors
and methods as well as proof-of-concept examples may be used in Black
Hat 2012 training courses. However, Symantec is not aware of any
malicious activity currently attempting to take advantage of the
disclosed vulnerabilities.
Mitigations
Symantec Security Response has released IPS signatures for web attacks
against Symantec Web Gateway to help detect and block remote exploit
attempts. Signatures are available through normal Symantec security
updates.
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
Offensive Security working through CERT/CC reported local file inclusion,
command execution and SQL injection issues.
Tenable Network Security working through CERT/CC also reported local file
inclusion, command execution, SQL injection and arbitrary password manipulation
issues.
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-2012-2953 BID 54426 command execution
CVE-2012-2957 BID 54429 local file inclusion
CVE-2012-2574 BID 54424 Blind SQL injection
CVE-2012-2961 BID 54425 SQL injection
CVE-2012-2976 BID 54427 shell injection
CVE-2012-2977 BID 54430 unauthorized/unauthenticated password change
__________________________________________________________________
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) 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: July 20, 2012
- --------------------------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
iQIVAwUBUA5Eq+4yVqjM2NGpAQL3Fg//Su1mxaxL7C6wUQYNn/QAHFIB0n0aBImi
SzhAf9j+IHC3LYJXlEDwBHyzJ5K+FDkEZhP08ptCSorVtWJN2zk8MJ/IU9hQ0QqE
gKiw9G3JMZCFJsBEvXyqd2RILc5uFFTeyOjJpvjB1D1aQvUytX4Vw0fYeuWxNLGP
5tMnaRGI+c0VLNTe+j//WukL0YtpZ0sqkS022vfa2k50pTMYDa8XXi2UZ3KQQ/CB
0hMBqWoTl8uAJ0yOOMI+GNpDKJ6N3itBkdVt9Mu4YrmjWTw4Tzms4tJl4K66N/NI
NvgVE+e0ET7uAHRc62YEKXwLH6VpLEu68xRPAStjpVfhKEjtYfdHkUDBBQym2Hur
WbpFnz4wWc3aeXgzu01JGyqQ2ZlqMd/RD6vehdSRgky6qS+DJo2pSygXsSQyEoEk
kfZO6HmB0zWMSNaOshgdf6JOSG+Rpogq5plAujrm94EzXIoEDOPelwtLdfPfRBSJ
8d0PfgldI01eV0ngNhKnLtgiPZZjOjxFnMF9lyuOA3Q4btQaHhTbxVflB1xOvEqU
x1OJ8rYB/GUJj14JgSaxu9vl/0zTRCvgzmXDOpRfTLb5z/eGuyq/ZVR027cfYAve
DepOnqzUDvK6Ip+1jUaq0jo5n/Jjg+mgAtZp5RhGuyGSJql5Ew22WJ8R33NUWyUF
LlFVYv9twfM=
=XMCJ
-----END PGP SIGNATURE-----
|