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

MAGMI Multiple Vulnerabilities

Medium

Synopsis

CVE-2020-5777 - Remote Authentication Bypass

Here, in MAGMI v0.7.23 source code https://github.com/dweeves/magmi-git/blob/18bd9ec905c90bfc9eaed0c2bf2d3525002e33b9/magmi/inc/magmi_auth.php#L35, it allows default magmi:magmi credentials to be used in the event a database connection fails. A remote attacker can trigger this connection failure if the Mysql setting max_connections (default 151) is lower than Apache (or another web server) setting MaxRequestWorkers (formerly MaxClients) (default 256). This can be done by sending at least 151 simultaneous requests to the Magento website to trigger a "Too many connections" error, then use default magmi:magmi basic authentication to remotely bypass authentication. To recreate the triggering of max connections error, performing a large number of  requests to following URIs worked.

POST /index.php/newsletter/subscriber/new/

or

GET /index.php/catalogsearch/advanced/result/?name=xxx

Once db connection is maxed out, an attacker can authenticate with default credentials and execute arbitrary commands on the server by uploading a php webshell. This issue has been patched in v0.7.24.

CVE-2020-5776 - Cross Site Request Forgery (CSRF)

Due to the lack of CSRF tokens, RCE (via phpcli command) is possible in the event that a CSRF is leveraged against an existing admin session for MAGMI. At the time of this advisory, no patch exists for this issue.

Solution

The fix for CVE-2020-5777 is in MAGMI version 0.7.24 and it is recommended to update to that version, however, there is no known solution for CVE-2020-5776 at this time.

Proof of Concept

https://github.com/tenable/poc/tree/master/MAGMI

Disclosure Timeline

06-03-2020 - Initial Disclosure to developer of MAGMI.
06-17-2020 - Tenable follows up with MAGMI developer.
07-06-2020 - Tenable informs that we will be disclosing to CERT if acknowledgement of disclosure isn't received.
07-06-2020 - MAGMI developer acknowledges disclosure and is in process of fixing issues.
07-09-2020 - Tenable thanks for response asks for updates on expected patch dates.
07-22-2020 - Tenable asks for patch updates.
08-05-2020 - Tenable hasn't received updates, follows up again asking for updates.
08-24-2020 - Tenable explains this is last follow up before disclosure, asks for any new information on patch updates.

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]

Risk Information

Tenable Advisory ID: TRA-2020-51
Credit:
Enguerran Gillier
CVSSv2 Base / Temporal Score:
6.8
6.8
CVSSv2 Vector:
AV:N/AC:M/Au:N/C:P/I:P/A:P
AV:N/AC:M/Au:N/C:P/I:P/A:P
Affected Products:
CVE-2020-5777 - MAGMI v0.7.23 and below
CVE-2020-5776 - All MAGMI versions
Risk Factor:
Medium

Advisory Timeline

09-01-2020 - Advisory published.
09-01-2020 - Added PoC
09-24-2020 - Fixed Typo