MobSF / Mobile-Security-Framework-MobSF

Mobile Security Framework (MobSF) is an automated, all-in-one mobile application (Android/iOS/Windows) pen-testing, malware analysis and security assessment framework capable of performing static and dynamic analysis.
https://opensecurity.in
GNU General Public License v3.0
17.4k stars 3.23k forks source link

MobSF dynamic analysis failes No such file or directory: 'capfuzz': 'capfuzz' #653

Closed yasharne closed 6 years ago

yasharne commented 6 years ago

Hi when I open DynamicAnalysis path, the header is Dynamic Analyzer - Failed and when I press create environment button I get this error on console:

[ERROR] Setting up Dynamic Analysis Environment (/home/yashar/Mobile-Security-Framework-MobSF/DynamicAnalyzer/views/android/dynamic.py, LINE 158 "start_proxy(settings.PORT, package)"): [Errno 2] No such file or directory: 'capfuzz': 'capfuzz'

ajinabraham commented 6 years ago

Have you followed the installation documentation? You need to install MobSF inside a python 3 virtualenv.

yasharne commented 6 years ago

Thanks a lot. I forgot about the virtualenv

wg-threatteam-Emil commented 6 years ago

Hello,

I am having this same issue.

Currently I have the MobSF up and running via venv. Static works fine from what I can tell and I did follow the installation documentation. However, I did see this thread:

https://github.com/MobSF/Mobile-Security-Framework-MobSF/issues/92

Does this play an effect at all?

What else can I give you to help troubleshoot? I am running an Ubuntu 18 VM in VMware fusion with 2 core CPU, 8 GB RAM. I set up venv for MobSF.

VBox - is this supposed to be running in a venv as well, was I supposed to install it in that same directory?

Regards.

wg-threatteam-Emil commented 6 years ago

I am running VMware Fusion on a Mac. Within there I have Ubuntu 18.

On the Ubuntu I have venv for MobSF, and VBox installed on Ubuntu. The Android VM is installed on VBox.

Is it possible that there is an issue with the fact of being within Fusion?

wg-threatteam-Emil commented 6 years ago

Just following back up.

I decided to reboot the Ubuntu host VM (again) and I got it going. Just noting this to be sure for possible future reference.

Thanks for an awesome tool.