Vulnerabilities > CVE-2015-6497 - Improper Input Validation vulnerability in Magento

047910
CVSS 8.8 - HIGH
Attack vector
NETWORK
Attack complexity
LOW
Privileges required
LOW
Confidentiality impact
HIGH
Integrity impact
HIGH
Availability impact
HIGH
network
low complexity
magento
CWE-20

Summary

The create function in app/code/core/Mage/Catalog/Model/Product/Api/V2.php in Magento Community Edition (CE) before 1.9.2.1 and Enterprise Edition (EE) before 1.14.2.1, when used with PHP before 5.4.24 or 5.5.8, allows remote authenticated users to execute arbitrary PHP code via the productData parameter to index.php/api/v2_soap.

Vulnerable Configurations

Part Description Count
Application
Magento
4
Application
Php
1

Common Weakness Enumeration (CWE)

Common Attack Pattern Enumeration and Classification (CAPEC)

  • Buffer Overflow via Environment Variables
    This attack pattern involves causing a buffer overflow through manipulation of environment variables. Once the attacker finds that they can modify an environment variable, they may try to overflow associated buffers. This attack leverages implicit trust often placed in environment variables.
  • Server Side Include (SSI) Injection
    An attacker can use Server Side Include (SSI) Injection to send code to a web application that then gets executed by the web server. Doing so enables the attacker to achieve similar results to Cross Site Scripting, viz., arbitrary code execution and information disclosure, albeit on a more limited scale, since the SSI directives are nowhere near as powerful as a full-fledged scripting language. Nonetheless, the attacker can conveniently gain access to sensitive files, such as password files, and execute shell commands.
  • Cross Zone Scripting
    An attacker is able to cause a victim to load content into their web-browser that bypasses security zone controls and gain access to increased privileges to execute scripting code or other web objects such as unsigned ActiveX controls or applets. This is a privilege elevation attack targeted at zone-based web-browser security. In a zone-based model, pages belong to one of a set of zones corresponding to the level of privilege assigned to that page. Pages in an untrusted zone would have a lesser level of access to the system and/or be restricted in the types of executable content it was allowed to invoke. In a cross-zone scripting attack, a page that should be assigned to a less privileged zone is granted the privileges of a more trusted zone. This can be accomplished by exploiting bugs in the browser, exploiting incorrect configuration in the zone controls, through a cross-site scripting attack that causes the attackers' content to be treated as coming from a more trusted page, or by leveraging some piece of system functionality that is accessible from both the trusted and less trusted zone. This attack differs from "Restful Privilege Escalation" in that the latter correlates to the inadequate securing of RESTful access methods (such as HTTP DELETE) on the server, while cross-zone scripting attacks the concept of security zones as implemented by a browser.
  • Cross Site Scripting through Log Files
    An attacker may leverage a system weakness where logs are susceptible to log injection to insert scripts into the system's logs. If these logs are later viewed by an administrator through a thin administrative interface and the log data is not properly HTML encoded before being written to the page, the attackers' scripts stored in the log will be executed in the administrative interface with potentially serious consequences. This attack pattern is really a combination of two other attack patterns: log injection and stored cross site scripting.
  • 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.

Packetstorm

data sourcehttps://packetstormsecurity.com/files/download/133544/KIS-2015-04.txt
idPACKETSTORM:133544
last seen2016-12-05
published2015-09-14
reporterEgiX
sourcehttps://packetstormsecurity.com/files/133544/Magento-1.9.2-File-Inclusion.html
titleMagento 1.9.2 File Inclusion

Seebug

bulletinFamilyexploit
description<p><b>[-] Software Link:</b></p><p><a href="http://magento.com/" rel="nofollow">http://magento.com/</a></p><p><br></p><p><b>[-] Affected Versions:</b></p><p>Version 1.9.2 and prior versions.</p><p><br></p><p><b>[-] Vulnerability Description:</b></p><p>The vulnerability is caused by the "catalogProductCreate" SOAP API implementation,</p><p>which is defined into the /app/code/core/Mage/Catalog/Model/Product/Api/V2.php script:</p><p><br></p><pre class="">109. public function create($type, $set, $sku, $productData, $store = null) 110. { 111. if (!$type || !$set || !$sku) { 112. $this-&gt;_fault('data_invalid'); 113. } 114. 115. $this-&gt;_checkProductTypeExists($type); 116. $this-&gt;_checkProductAttributeSet($set); 117. 118. /** @var $product Mage_Catalog_Model_Product */ 119. $product = Mage::getModel('catalog/product'); 120. $product-&gt;setStoreId($this-&gt;_getStoreId($store)) 121. -&gt;setAttributeSetId($set) 122. -&gt;setTypeId($type) 123. -&gt;setSku($sku); 124. 125. if (!property_exists($productData, 'stock_data')) { 126. //Set default stock_data if not exist in product data 127. $_stockData = array('use_config_manage_stock' =&gt; 0); 128. $product-&gt;setStockData($_stockData); 129. }<br></pre><p><br></p><p>User input passed through the "productData" SOAP parameter is not properly validated before being<br></p><p>used in a call to the "property_exists()" function at line 125. This can be exploited by attackers</p><p>with valid API credentials to include and execute arbitrary PHP code (both from local or remote</p><p>resources) leveraging the Varien_Autoload::autoload() autoloading function. Successful exploitation</p><p>of this vulnerability requires the application running on PHP before version 5.4.24 or 5.5.8.</p><p><br></p><p><b>[-] Solution:</b></p><p>Update to version 1.9.2.1 or apply the SUPEE-6482 patch bundle.</p><p><br></p><p><b>[-] Disclosure Timeline:</b></p><p>[27/02/2015] - Vendor notified</p><p>[25/06/2015] - Vendor acknowledgement stating the issue will be fixed in the next release</p><p>[04/08/2015] - Version 1.9.2.1 released along with the patch for this vulnerability</p><p>[13/08/2015] - CVE number requested</p><p>[17/08/2015] - CVE number assigned</p><p>[11/09/2015] - Public disclosure</p><p><br></p><p><b>[-] CVE Reference:</b></p><p>The Common Vulnerabilities and Exposures project (cve.mitre.org)</p><p>has assigned the name CVE-2015-6497 to this vulnerability.</p><p><br></p><p><b>[-] Credits:</b></p><p>Vulnerability discovered by Egidio Romano of Minded Security.</p><p><br></p><p><b>[-] Original Advisory:</b></p><p><a href="http://karmainsecurity.com/KIS-2015-04" rel="nofollow">http://karmainsecurity.com/KIS-2015-04</a></p>
idSSV:89416
last seen2017-11-19
modified2015-09-14
published2015-09-14
reporter00r00
titleMagento <= 1.9.2 (catalogProductCreate) Autoloaded File Inclusion Vulnerability