Closed wilsonator closed 2 months ago
👋 @wilsonator Issues is only for reporting a bug/feature request. For limited support, questions, and discussions, please join MobSF Slack channel Please include all the requested and relevant information when opening a bug report. Improper reports will be closed without any response.
Port seems open inside the docker
docker exec -it mobsf /usr/bin/bash
(replace the name by yours if different
So the problem is that the port is not exposed from external
docker run -it --rm -p 8000:8000 -p 1338:1338 -e MOBSF_ANALYZER_IDENTIFIER=emulator-5554 opensecurity/mobile-security-framework-mobsf:latest
Your command is not good, left side is for port externally exposed that point to right side internal port. So in your case it's 1338:1337
The good one is :
docker run -it --rm -p 8000:8000 -p 1338:1337 -e MOBSF_ANALYZER_IDENTIFIER=emulator-5554 opensecurity/mobile-security-framework-mobsf:latest
Thank you, this seems to have fixed my issues!
ENVIRONMENT
EXPLANATION OF THE ISSUE
In MobSF Docker container, the port 1337 is used for HTTPTools. This port seems to be blocked by windows by default.
I started MobSF for Dynamic Analysis with the command:
docker run -it --rm -p 8000:8000 -p 1338:1338 -e MOBSF_ANALYZER_IDENTIFIER=emulator-5554 opensecurity/mobile-security-framework-mobsf:latest
However this does not change the listening port of HTTPTools.
I attempted to unblock port 1337 in Windows firewall inbound and outbound and this change had no effect.
I further tested the issue with httptools installed manually. On port 1338 the web UI is accessible:
However port 1337 is not accessible:
I think it would be best to configure a command line option that will change the port of httptools to whatever port the user desires.
STEPS TO REPRODUCE THE ISSUE
LOG FILE