Mobile & Wireless

iOS App Patching Tool “Rollout” Prone to Abuse

Researchers at security firm FireEye have analyzed another hot-patching solution for iOS applications that could be abused by malicious actors to turn harmless apps into malware.

<p><strong><span><span>Researchers at security firm FireEye have analyzed another hot-patching solution for iOS applications that could be abused by malicious actors to turn harmless apps into malware.</span></span></strong></p>

Researchers at security firm FireEye have analyzed another hot-patching solution for iOS applications that could be abused by malicious actors to turn harmless apps into malware.

Updates and hotfixes created by iOS application developers for software available in the Apple App Store have to go through a strict security and integrity verification process. Since this can be problematic, especially when fixes need to be pushed out quickly, some companies and independent developers have created tools that make it possible to release updates directly to users.

While these solutions can be useful as they allow developers to easily roll out fixes by adding a few lines of code to their applications, FireEye has warned that they can also be abused by threat actors to push malicious code to apps after they pass Apple’s inspection.

In January, the security firm analyzed JSPatch, an open source hot-patching tool built on top of Apple’s JavaScriptCore framework. JSPatch has been found in more than 1,200 apps available in the App Store.

FireEye on Monday published the results of research targeting a similar solution, namely Rollout.io.

Rollout is a commercial tool that allows developers to easily debug and hot-patch their products by giving them remote code-level access to the live app. Using technologies and techniques such as debug symbol (dSYM) files, the JavaScriptCore framework, and method swizzling, Rollout enables developers to carry out a wide range of modifications.

Researchers reported identifying the use of Rollout in 245 apps found in the App Store (as of January 19), and the developer says its solution is currently running on 35 million devices. Unlike JSPatch, which is mainly used by Chinese developers, Rollout’s customer base is international and predominantly English-speaking.

FireEye has published a blog post detailing how attackers can use Rollout and Apple’s private APIs to access a device’s camera and microphone, scan a phone to determine if a certain application is installed, make calls to premium numbers, and take screenshots. There are two scenarios for an attack involving Rollout: the app developer is malicious, or an unwitting developer integrates a malicious third-party ad SDK into a legitimate app.

Advertisement. Scroll to continue reading.

Experts have described a theoretical attack scenario in which an apparently harmless iOS app is utilized to conduct malicious activities, but noted that such attacks have not been spotted in the wild.

FireEye informed Rollout of its findings and the vendor is preparing a new version of its product that will prevent developers from accessing private iOS APIs and frameworks. Since the attack examples described by researchers involve these types of components, restricting their use can prevent abuse.

“Rollout’s solution allows mobile companies to mitigate production quality and performance issues, Rollout.io is already running on 35 million devices and has proven invaluable for preventing app downtime, increasing app rating and improving user experience,” Erez Rusovsky, CEO & co-founder of Rollout, told SecurityWeek.

“As written in FireEye report, there are many ways developers can exploit Objective-C Runtime and bypass App Store review process with the intent of using Apple’s private APIs (w/o Rollout.io). Nonetheless Rollout is fully committed to preventing abuse of our technology and we are currently updating our systems to reject usage of Apple’s private APIs,” Rusovsky added. “We thank Jing Xie and the rest of the FireEye team for their help in this matter.”

RelatedEstablishing Correspondence Between an Application and its Source Code

Related Content

Copyright © 2024 SecurityWeek ®, a Wired Business Media Publication. All Rights Reserved.

Exit mobile version