Redis port vulnerability in subprocess qemu-system-aarch64 #157
-
qemu-system-aarch64 creates a port 6379 that is bound to all interfaces, among other ports. The port 6379 for REDIS which is accessible without authentication. https://support.genymotion.com/hc/en-us/articles/360002732118-Genymotion-Desktop-and-firewalls For running Genymotion, can you please bind the ports to the local interface only? Command for reference: This is a blocker for running Genymotion using my corporate network. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
Hi @genman, Thanks for your valuable feedback, we will fix it in the next Genymotion Desktop version. As it is a blocker for you, I'm sharing with you an undocumented workaround that you can try with no guarantee of success. TLDR; Try to set the env var
👇 Explanation In the process command you see two
Using a sed command to add
The result is:
The value of the env var
ℹ️ |
Beta Was this translation helpful? Give feedback.
-
@genman Genymotion Desktop 3.8 has just been released! This new version includes a security patch which addresses the vulnerability you reported. For more details, please refer to the release notes: https://www.genymotion.com/blog/release-note/genymotion-desktop-3-8-0/ |
Beta Was this translation helpful? Give feedback.
Hi @genman,
Thanks for your valuable feedback, we will fix it in the next Genymotion Desktop version.
As it is a blocker for you, I'm sharing with you an undocumented workaround that you can try with no guarantee of success.
TLDR;
Try to set the env var
GM_QEMU_START_ARGS
with the following value, then if you start Genymotion, the QEMU argument should be partly overriden: