Zero day vulnerability in Magento e-commerce platform exploited by hackers to steal credit card information
Researchers have discovered that cyber criminals are exploiting the zero day vulnerability in Magento’s e-commerce platform to steal credit card details. The zero day vulnerability which was discovered by Check Point, can allow an attacker to gain complete control over a store with administrator access, potentially allowing credit card theft, wrote Netanel Rubin of Check Point’s Malware and Vulnerability Research Group.
As many as 200,000 websites use Magento e-commerce platform, which is owned by eBay.
The security companies have warned the owners and webmasters using Magento’s e-commerce platform to ensure they’re using its latest software. Check Point, which found the flaw, reported it to Magento, which issued a patch (SUPEE-5344) on Feb. 9. Since Check Point revealed the flaw earlier this week, it appears attackers have picked up on it and are trying to find unpatched applications.
Analysts with Sucuri Security wrote on Thursday they’ve seen indications that attackers using two Russia-based IP addresses are trying to exploit unpatched Magento applications.
As per Sucuri, the attacks so far appeared aimed at just first creating a fake administrator user in a Magento database. However, David Cid, CTO and founder of Sucuri feels that cyber criminals will use that foothold to take over a site later.
The exploit code Sucuri analyzed is a SQL injection attack, which inserts a new “admin_user” into a database. Cid wrote the exploit uses the usernames “vpwq” and “defaultmanager.” The presence of those names on a system could indicate a successful attack.
Check Point posted a video on its blog that showed how the flaw could be used to reduce the price of a US$100,000 watch on an e-commerce site they created for demonstration purposes.
Rubin wrote the vulnerability in Magento is composed of several flaws which allow an unauthenticated hacker to run PHP code on a web server. The flaws are within Magento’s core code and affects default installations of Magento’s Community 184.108.40.206 and Enterprise 220.127.116.11 editions, he wrote.
“The sad part is that you will not know it’s affecting you until it’s too late, Gramantik wrote in a blog post, “in the worst cases it will not become apparent until they appear on your bank statements.”