CVE-2024-3400: PAN-OS Command Injection Vulnerability in GlobalProtect Gateway. Learn More

CVE-2024-3400: PAN-OS Command Injection Vulnerability in GlobalProtect Gateway. Learn More

Services
Capture
Managed Detection & Response

Eliminate active threats with 24/7 threat detection, investigation, and response.

twi-managed-portal-color
Co-Managed SOC (SIEM)

Maximize your SIEM investment, stop alert fatigue, and enhance your team with hybrid security operations support.

twi-briefcase-color-svg
Advisory & Diagnostics

Advance your cybersecurity program and get expert guidance where you need it most.

tw-laptop-data
Penetration Testing

Test your physical locations and IT infrastructure to shore up weaknesses before exploitation.

twi-database-color-svg
Database Security

Prevent unauthorized access and exceed compliance requirements.

twi-email-color-svg
Email Security

Stop email threats others miss and secure your organization against the #1 ransomware attack vector.

tw-officer
Digital Forensics & Incident Response

Prepare for the inevitable with 24/7 global breach response in-region and available on-site.

tw-network
Firewall & Technology Management

Mitigate risk of a cyberattack with 24/7 incident and health monitoring and the latest threat intelligence.

Solutions
BY TOPIC
Offensive Security
Solutions to maximize your security ROI
Microsoft Exchange Server Attacks
Stay protected against emerging threats
Rapidly Secure New Environments
Security for rapid response situations
Securing the Cloud
Safely navigate and stay protected
Securing the IoT Landscape
Test, monitor and secure network objects
Why Trustwave
About Us
Awards and Accolades
Trustwave SpiderLabs Team
Trustwave Fusion Security Operations Platform
Trustwave Security Colony
Partners
Technology Alliance Partners
Key alliances who align and support our ecosystem of security offerings
Trustwave PartnerOne Program
Join forces with Trustwave to protect against the most advance cybersecurity threats
SpiderLabs Blog

Executing Apps on Jailbroken Devices

This post is part two of a three-part series about mobile security. Today's post will discuss the execution of apps on jailbroken devices. Yesterday, we described some vulnerabilities in iOS web browsers. Tomorrow, we'll explore detecting jailbroken devices.

  • "App cannot run on jailbroken devices"
  • "This version of [app name] only runs on unmodified OS versions"
  • "This app cannot run on a jailbroken device"

Three different messages but they say the same thing: the app will not execute on a jailbroken device. The question is though, is it a good idea for developers to block execution on jailbroken or rooted devices?

There is of course not a good answer to the question, and it depends on the app's purpose and the information it handles.

However, the decision to block execution on rooted or jailbroken devices should not be taken lightly. By blocking execution, you've got your work cut out for you. Jailbreak and root detection is not easy. If you decide to block execution on modified devices, you need to invest the time and get the necessary skills to implement detection that cannot be bypassed. I would argue that a root detection or jailbreak detection that can be bypassed is worse than not detecting root or jailbreak at all. Apps that try to block execution on modified devices can flag themselves as all the more interesting to a malicious individual.

Here are some of the tools you are up against (this is not a comprehensive list, it merely provides a few examples):

In our testing, we found that 14 percent of apps that attempted to block execution on rooted or jailbroken devices did so ineffectively. We were able to bypass the checks in hours and sometimes even in minutes.

Our research also points out the difficulty in detecting and blocking execution on a jailbroken device. Of apps that attempted to block execution on jailbroken or rooted devices, we managed to bypass the checks and execute the app on a modified device in every case.. Granted, some of the bypasses required heavy modifications of the operating system, and sometimes the app itself, but we were successful in the end.

In summary, you should not block execution of apps on rooted or jailbroken devices unless it is absolutely necessary for the security and/or integrity of the app. If you do decide to do so, make sure to understand the time and effort it will require and have the necessary resources available.

Latest SpiderLabs Blogs

EDR – The Multi-Tool of Security Defenses

This is Part 8 in my ongoing project to cover 30 cybersecurity topics in 30 weekly blog posts. The full series can be found here.

Read More

The Invisible Battleground: Essentials of EASM

Know your enemy – inside and out. External Attack Surface Management tools are an effective way to understand externally facing threats and help plan cyber defenses accordingly. Let’s discuss what...

Read More

Fake Dialog Boxes to Make Malware More Convincing

Let’s explore how SpiderLabs created and incorporated user prompts, specifically Windows dialog boxes into its malware loader to make it more convincing to phishing targets during a Red Team...

Read More