Facebook Google Plus Twitter LinkedIn YouTube RSS Menu Search Resource - BlogResource - WebinarResource - ReportResource - Eventicons_066 icons_067icons_068icons_069icons_070

[R1] Symantec Web Gateway (SWG) Multiple Vulnerabilities #2

Critical

Synopsis

CVE-2012-2957 - Multiple Script language Parameter Path Traversal Remote File Access

Symantec Web Gateway contains a flaw that allows a local attacker to traverse outside of a restricted path. The issue is due to the spywall/languageTest.php and /spywall/download_file.php scripts not properly sanitizing user input, specifically directory traversal style attacks (e.g., ../../) supplied via the 'language' parameter. This directory traversal attack would allow the attacker to access an arbitrary file. These can be used to include arbitrary PHP files (i.e. Local File Inclusion), but without a way to upload or modify PHP content on the system, they cannot be used for privilege escalation.

CVE-2012-2961 - /spywall/search.php value Parameter SQL Injection

Symantec Web Gateway contains a flaw that may allow an attacker to carry out an SQL injection attack. The issue is due to the /spywall/search.php script not properly sanitizing user-supplied input to the 'value' parameter, before being passed to the includes/dbutils.php script. This may allow an attacker to inject or manipulate SQL queries in the back-end database, allowing for the manipulation or disclosure of arbitrary data.

CVE-2012-2977 - /spywall/temppassword.php Arbitrary User Password Manipulation

Symantec Web Gateway contains a flaw related to the /spywall/temppassword.php script in the management console that is triggered when the program fails to properly sanitize user supplied input. This may allow a remote attacker to change the password of an arbitrary user.

CVE-2012-2976 - Multiple Script Remote Command Execution

#1 Symantec Web Gateway (SWG) contains a flaw in the management console. The issue is triggered when an attacker sends a specially crafted Content-Type header in a POST request to the /spywall/previewBlocked.php or /spywall/previewInfected.php scripts. With a specially crafted request, a remote attacker can execute arbitrary commands with the privileges of the web server.

#2 Symantec Web Gateway contains a flaw that is triggered when input is not properly sanitized before being used by the 'filename' parameter in the management console. This may allow a remote attacker to execute arbitrary shell commands.

#3 Symantec Web Gateway (SWG) contains a flaw that is triggered when input is not properly sanitized before being used by the 'ip' parameter of the fromha.php script in the management console. This may allow a remote authenticated attacker to execute arbitrary shell commands. Note that HTTP Basic Authentication is used to protect this page and the system has no credentials configured by default. However, by chaining this with the associated local file inclusion vulnerability, the authentication check is bypassed and the fromha.php script can be called remotely.

Solution

Upgrade to version 5.0.0.438 or later, as it has been reported by Symantec to address these issues.

Disclosure Timeline

2012-06-25 - Reported to CERT/CC via web submission form
2012-06-25 - CERT/CC confirms receiving the report
2012-07-11 - CERT/CC says Symantec stated a fix is planned for the end of the month
2012-07-20 - Symantec releases a fix and publishes advisory SYM12-011
2012-07-24 - CERT/CC publishes VU#108471

All information within TRA advisories is provided “as is”, without warranty of any kind, including the implied warranties of merchantability and fitness for a particular purpose, and with no guarantee of completeness, accuracy, or timeliness. Individuals and organizations are responsible for assessing the impact of any actual or potential security vulnerability.

Tenable takes product security very seriously. If you believe you have found a vulnerability in one of our products, we ask that you please work with us to quickly resolve it in order to protect customers. Tenable believes in responding quickly to such reports, maintaining communication with researchers, and providing a solution in short order.

For more details on submitting vulnerability information, please see our Vulnerability Reporting Guidelines page.

If you have questions or corrections about this advisory, please email [email protected]