Being robust, functional and highly customizable, Magento deserves its leading position amongst the most powerful eCommerce platforms. According to BuiltWith over 20% of TOP 10K eCommerce stores are running on Magento(Community and Enterprise Editions). But same as any other platform it has to be frequently scanned for vulnerability issues. Your store can suffer heavy security attacks any moment, so you have to be on the watch and protect your customers from sensitive data loss.
1 Uninstalled Security Patches
Magento team is constantly discovering all possible security issues and launches security patches that prevent Magento store owners from the unnecessary stress. To be alerted about the latest patches, sign up to a newsletter at the Magento security center. Magento Enterprise Edition has a higher priority, so patches for it are updated in the first place and some time later patches for Community Edition appear. New Magento versions generally contain all prior patches as well.
- Security patch 5994 (admin disclosure)
- Security patch 5344 (Shoplift)
- Security patch 6285 (XSS, RSS)
- Security patch 6482 (XSS)
- Security patch 6788 (secrets leak)
- Security patch 7405 (admin takeover)
All you need to do is just download Release for your version in time and install it in 6 steps:
- Make a backup
- Log on to SSH (shell)
- Download the patch
- Apply the patch
- Clear your cache
- Check your shop
Or contact Magento developers to help you with installation to make sure you wonât miss a thing. To detect vulnerabilities you can run a free MageReport.com tool.
2 Unprotected Magmi
Magmi is a Magento mass importer. It is used to empower the performance of importing products, which is quite low in Magento by default. But this effective tool has one major weakness - it doesnât have authentication of its own, so it opens access to your Magento web store database. Malefactors can add Admin users and change products, as well as upload insecure files or steal credit card data from your store, so you need to make 100% sure that this module is secured against hacker attacks. You can fix this problem via SSH, but if you donât know how to use it, contact us.
3 Unprotected development files
In Magento versions 1.9.2.0 till 1.9.2.2 several development files were included in the standard installation package. It was later discovered that these files may reveal your passwords and other sensitive data. To secure your Magento development files configure your webserver to block requests to â/devâ folder, but please note that it doesnât mean simply to delete the â/devâ directory because this brutal method will just break future patches. You need to block these files at the web server level. Note that it works differently for Apache and Nginx.
4 Exposed Magento 2 API
The API in Magento 2 can be accessed without providing credentials. Such information as storefront and (hidden) products (including prices) is exposed through API.
5 Admin/downloader unprotected
By default, back-end or Admin pane are placed at â/adminâ and â/downloaderâ. It is a well known fact, so hackers can easily take advantage of this vulnerability by launching a brute-force attack, which generates random passwords until the suitable one is found. That should stop you from using simple passwords like â123456789â, since they are crushed within a minute or less.
If it will make you happy, itâs a quite common mistake of careless Magento users. Hypernode team detects around 1M of such vulnerabilities weekly!
This is not the whole story though! Unfortunately, simply using a strong password with capital letters, numbers and signs wonât protect your store. Hackers can continue crushing your password and this additive load can waste valuable capacity of your server, so keep the name of the admin panel in a secret as well.
Of course, there are some other ways you can secure admin/downloader:
First of all, change the name of the back-end panel at app/etc/local.xml under admin -> routers -> adminhml -> args -> frontName. It has to be something easy to remember for you but not clear or easy-to-guess for others.
Flush your cache in the back end at System â Cache Management or run in SSH: magerun cache:flush.
In Magento 2 a secret back-end name is created during installation.
Secure/downloader. /downloader is a standard link to install programs via the Magento Connect Manager. As you may have noticed, all standard ways are easy preys for intruders. But in this case renaming wonât be enough, so it is better to install IP access control (an âIP whitelistâ).
Install adaptive filtering or Intrusion Prevention System (IPS). Itâd better to prevent attacks by blocking hacker sources.
6 Unprotected version control
Magento version control systems/platforms such as Git and Subversion store their metadata in hidden folders. But they could reveal sensitive information such as passwords if they are left open via the web. If the database passwords are also present somewhere in this repository, this may lead to hackers using their own username and password combination to add admin users to your Magento webshop.
7 Credit Card Hijack
In November 2015 the whole Magento world has been stirred up by the Credit Card Hijacking. This malicious javascript code is injected into Magento stores and allows hackers to intercept credit card data. For 6 months intruders wielded with harvest of unprotected data of credit cards from 3,500 web shops. Credit card numbers are captured as soon as an unsuspecting shopper types them in their browser, so they are captured right before they can be encrypted.
And itâs not the Magento weakness only, since the hijacking Javascript code could run on any site that handles sensitive information.
The fraud was detected on May 12th, so the malpractice was unnoticed for months and is still active, so if you still havenât scanned your Magento store for vulnerabilities you have to make this ASAP!!!
If Credit Card Hijack is detected, contact a Magento developer or Magento security expert, because trust us that fixing this crack isnât easy cheese.
