Vulnerabilities > CVE-2013-7092 - SQL Injection vulnerability in Mcafee Email Gateway 7.6
Attack vector
NETWORK Attack complexity
LOW Privileges required
SINGLE Confidentiality impact
PARTIAL Integrity impact
PARTIAL Availability impact
PARTIAL Summary
Multiple SQL injection vulnerabilities in /admin/cgi-bin/rpc/doReport/18 in McAfee Email Gateway 7.6 allow remote authenticated users to execute arbitrary SQL commands via the (1) events_col, (2) event_id, (3) reason, (4) events_order, (5) emailstatus_order, or (6) emailstatus_col JSON keys.
Vulnerable Configurations
| Part | Description | Count |
|---|---|---|
| Application | 1 |
Common Weakness Enumeration (CWE)
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:
Nessus
| NASL family | CGI abuses |
| NASL id | MCAFEE_EMAIL_GATEWAY_SB10064.NASL |
| description | The remote host is running a version of McAfee Email Gateway (MEG) that is affected by multiple SQL injection and command execution vulnerabilities: - Multiple SQL injections vulnerabilities exist in the administrative web interface. A remote, authenticated attacker could potentially exploit these vulnerabilities to run arbitrary SQL commands. (CVE-2013-7092) - A command execution vulnerability exists in the administrative web interface due to a failure to sanitize user input to the |
| last seen | 2020-06-01 |
| modified | 2020-06-02 |
| plugin id | 73225 |
| published | 2014-03-27 |
| reporter | This script is Copyright (C) 2014-2018 and is owned by Tenable, Inc. or an Affiliate thereof. |
| source | https://www.tenable.com/plugins/nessus/73225 |
| title | McAfee Email Gateway Multiple Vulnerabilities (SB10064) |
| code | |
Seebug
bulletinFamily exploit description CVE ID:CVE-2013-7092 McAfee Email Gateway是一款电子邮件解决方案。McAfee Email and Web Security Appliance用于智能化的垃圾邮件和恶意软件防护。 通过"events_col", "event_id", "reason", "events_order", "emailstatus_order"和"emailstatus_col" JSON键值提交给/admin/cgi-bin/rpc/doReport/18的输入在用于SQL查询之前缺少过滤，允许远程攻击者利用漏洞提交特制的SQL查询，操作或获取数据库数据。 0 McAfee Email and Web Security Appliance 5.x McAfee Email Gateway 7.x 用户可参考如下厂商提供的安全公告获取补丁以修复该漏洞： https://kc.mcafee.com/corporate/index?page=content&id=SB10064 id SSV:61831 last seen 2017-11-19 modified 2014-03-18 published 2014-03-18 reporter Root title McAfee Email Gateway/McAfee Email和Web Security Appliance多个SQL注入漏洞 bulletinFamily exploit description CVE ID：CVE-2013-7092 McAfee Email Gateway之前名为IronMail，是企业级的硬件邮件网关和管理平台。 由于通过"events_col", "event_id", "reason", "events_order", "emailstatus_order"和"emailstatus_col" JSON keys传递到/admin/cgi-bin/rpc/doReport/18的输入在被用于SQL查询前没有正确过滤，攻击者可以利用漏洞通过注入任意SQL代码操纵SQL查询。 0 McAfee Email and Web Security Appliance 5.x McAfee Email Gateway 7.x 目前厂商已经发布了升级补丁以修复这个安全问题，请到厂商的主页下载： https://kc.mcafee.com/corporate/index?page=content&id=SB10064 id SSV:61792 last seen 2017-11-19 modified 2014-03-14 published 2014-03-14 reporter Root title McAfee Email Gateway/McAfee Email and Web Security Appliance SQL注入漏洞