Save your Magento 2 store from PRODSECBUG-2198


With the increase in the Magento users as well as an increase in the awareness of Magento, the hackers are also increased, they have become more and more experts in their hacking. The number of cyber-attack doubles every time in Magento 2.x.

There is a security bug in the Magento 2.x content system which makes us discover the new and new methods to save the site. That bug is called  PRODSECBUG-2198. This is responsible for the damage to the sites. Every month the number of hacked sites is increasing which is almost near to double. The card details of the customers are stolen from the website. Hackers have become more and more expert with malware nowadays. The bigger and more successful a site, the more bragging rights a hacker gets.

A security engineer at Ambionics discovered and reported the PRODSECBUG-2198, and the security updates and patches were released on March 26.

Hiring the professional Magento certified developers, as well as Magento Experts,  can help your Magento eCommerce store’s successful as well as bug-free development.
With the above method in Magento 2.2 CE version you may face an error as below:
bash PRODSECBUG-2198-2.2-CE.composer-2019-03-27-06-12-19.patch
diff: unrecognized option ‘–git’
diff: Try ‘diff –help’ for more information.
PRODSECBUG-2198-2.2-CE.composer-2019-03-27-06-12-19.patch: line 2: index: command not found
PRODSECBUG-2198-2.2-CE.composer-2019-03-27-06-12-19.patch: line 3: —: command not found
In order to avoid this error, follow the below steps:
● If you use git for your project:
git apply PRODSECBUG-2198-2.2-CE.composer-2019-03-27-06-12-19.patch
● use patch
○ Remove the a/ and b/ before the path name.
○ Move the patch file to your Magento root and execute patch -p0 < PRODSECBUG-2198-2.2-CE.composer-2019-03-27-06-12-19.patch

About PRODSECBUG-2198

Type:
 Injections: SQL
CVSSv3 Severity:
9 (Critical)
Description:
An unauthenticated user can execute arbitrary code through an SQL injection vulnerability, which causes sensitive data leakage.
Product(s) Affected:
Magento Open Source prior to 1.9.4.1, and Magento Commerce prior to 1.14.4.1, Magento 2.1 prior to 2.1.17, Magento 2.2 prior to 2.2.8, Magento 2.3 prior to 2.3.1
Fixed In:
Magento Open Source 1.9.4.1, Magento Commerce 1.14.4.1, SUPEE-11086, Magento 2.1.17, Magento 2.2.8, Magento 2.3.1
Reporter:
cfreal

Steps to install the PRODSECBUG-2198 patch

Backup Your Magento Store
Before applying any new security patch, you will have to first take the back up of your Magento store. Backup is advisable because the store might have some security patches.
Download & Upload the Patch
The next step is to download the Patch PRODSECBUG-2198 from here for your Magento Store Version and then you will have to upload it to your Magento folder.
Apply the Patch
After you log in to your shell server and navigating to your Magento folder, you will have to run the following command:
Bash patch - Name
For e.g. bash PRODSECBUG-2198-2.3-CE.patch
Clear your Magento Cache
Just remove your Magento Cache once you apply the patch. There are two steps to clear the cache
flush the cache from Magento admin
run the following SSH commands:
php bin/magento cache: flush
php bin/magento cache: clean
Confirm the Patch Installation
You will have to confirm whether the patch is being installed successfully or not. For that you can run the following command to check whether the patch has been installed successfully or not
grep '|' app/etc/applied.patches.list
grep '|' app/etc/applied.patches.list
Remove the Patch file
After the successful patch installation, you can remove the .patch file from the root of your Magento.
Run the following command to remove it using SSH:
rm Patch-Name

Make Your Magento Store More Secure

In this time, when security is the topmost priority as well as when the customers become your regular ones on the basis of your security you provide, make sure that you follow all the tips given below
● Regularly update your Magento Installation - every time the update comes with the new regular updates which provide the best protection from the bugs. Update the new version and protect it.

● Follow The Best Magento Development Practices - there are some of the best practices which are framed by the Magento. Whenever you are going to build your site, make sure that you go with the best development practices.


● Magento Store On a Secure Server - Don’t use shared hosting for your Magento store, go with the secure server always.  If you feel the dedicated hostings are costly, you can go with the Best Magento hosting.

● Magento Security Checker - Always get your Magento security scan tool to check the Magento patches.

If you are looking for the help of Certified Magento developers for successful hack removal, click here

Comments

Popular posts from this blog

Preparing your eCommerce business for the Unlock Phase

Helpful Techniques That Can Boost Your Conversion

Ecommerce SEO Guide for Do's & Don'ts of Product Page