Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Application Security

// // //
9/3/2019
10:35 AM
Larry Loeb
Larry Loeb
Larry Loeb

Making Code Harder to Read by Attackers Can Make Injections Less Likely

It's one of way of stopping formjackers making off with customers' credit card details.

In Plain Sight II: On the Trail of Magecartwas a white paper commissioned by Arxan Technologies and produced by Aite Group. It says that its purpose is to demonstrate the massive attack surface created by electronic commerce (e-commerce) web applications that aren't being properly secured.

This lack in in-app security makes web apps vulnerable to a type of cyber attack called formjacking. Formjacking is a type of breach, where attackers inject the e-commerce checkout form with malicious code that sends buyers' credit card information to an offsite server under the hackers' control.

Eighty compromised servers were analyzed as part of this research. The companies were located in the US, Canada, Europe, Latin America and Asia.

Formjacking code is employed on the server side and executed as JavaScript in the victim's web browsers on the client side. On the web server running the e-commerce website itself is where the malicious code is inserted and renders/executes in the web browser of the victim.The credit card details are then sent from the victim's computer to the staging server owned by the attacker.

The white paper recommends some overall solutions. First is a well-documented and regularly updated vulnerability and patch management process that includes regular patching of, updates to, and penetration testing of the company's e-commerce site(s).

Second is in-app protection which implements code obfuscation and white-box cryptography to make the web forms unreadable to the adversary. This stops the adversary from injecting their field-stealing JavaScript code by making the resident code unreadable to the attacker.

Because obfuscated code can be de-obfuscated, it's also wise to adopt solutions that implement multiple layers of security, such as detection of code tampering and analysis, an active response that shuts a browser down upon detection of formjacking, and threat detection along with real-time alerting and response -- not just obfuscation.

E-commerce sites can also monitor traffic to ensure the web server is not initiating outbound connections. This should never happen under normal operating conditions, except for legitimate program updates. Deepak Patel, vice president and security evangelist with PerimeterX, commented on the situation to Security Now.

"The modern web application stack relies on third-party scripts obtained from a variety of providers, not all of whom have strong security practices," he said. "Website owners lack visibility into the third-party scripts running on the users' browsers within the context of their site. Many website owners are also unaware of all the first-party scripts running on their site. In addition to staying up to date with the latest versions of your critical platform components, website owners need to take another step: get visibility and control of all the scripts running on your website, whether first- or third-party or another part of the supply chain."

— Larry Loeb has written for many of the last century's major "dead tree" computer magazines, having been, among other things, a consulting editor for BYTE magazine and senior editor for the launch of WebWeek.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Edge-DRsplash-10-edge-articles
I Smell a RAT! New Cybersecurity Threats for the Crypto Industry
David Trepp, Partner, IT Assurance with accounting and advisory firm BPM LLP,  7/9/2021
News
Attacks on Kaseya Servers Led to Ransomware in Less Than 2 Hours
Robert Lemos, Contributing Writer,  7/7/2021
Commentary
It's in the Game (but It Shouldn't Be)
Tal Memran, Cybersecurity Expert, CYE,  7/9/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon
Current Issue
Incorporating a Prevention Mindset into Threat Detection and Response
Threat detection and response systems, by definition, are reactive because they have to wait for damage to be done before finding the attack. With a prevention-mindset, security teams can proactively anticipate the attacker's next move, rather than reacting to specific threats or trying to detect the latest techniques in real-time. The report covers areas enterprises should focus on: What positive response looks like. Improving security hygiene. Combining preventive actions with red team efforts.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2022-1898
PUBLISHED: 2022-05-27
Use After Free in GitHub repository vim/vim prior to 8.2.
CVE-2022-1907
PUBLISHED: 2022-05-27
Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to 0.11.
CVE-2022-1908
PUBLISHED: 2022-05-27
Buffer Over-read in GitHub repository bfabiszewski/libmobi prior to 0.11.
CVE-2022-1909
PUBLISHED: 2022-05-27
Cross-site Scripting (XSS) - Stored in GitHub repository causefx/organizr prior to 2.1.2200.
CVE-2022-28394
PUBLISHED: 2022-05-27
EOL Product CVE - Installer of Trend Micro Password Manager (Consumer) versions 3.7.0.1223 and below provided by Trend Micro Incorporated contains an issue with the DLL search path, which may lead to insecurely loading Dynamic Link Libraries (CWE-427). Please note that this was reported on an EOL...