3CX DLL-Sideloading attack: What you need to know
I've downloaded and imported the appliance into Virtualbox, I checked its network config, the first adapter (LAN) is setup as internal network and the second one (WAN) as NAT. Now if I understand correctly, internal network with VB means its only accessible from another VM attached to the same network so I am struggling to access the interface from my host. Any hints?
==
When in doubt, Script it out.
Have it set up in VirtualBox using host-only as use describe, when using another VM I can't get to the GUI. Can't figure out what I'm doing wrong here. The address is http://172.16.16.16, right?
Definitely, for example right now the VM "client" guest is configured with IP of 172.16.16.32, subnet mask 255.255.255.0, gateway and DNS pointing to 172.16.16.16. Just checked the console of the SFOS VM under Network Administration and it does show the current IP address as the default (16). Can ping the SFOS, but the browser just returns HTTP 404. Do you have to use a custom port, as with UTM, or something else I'm missing? I feel like I'm missing something obvious here.
Yeah, try: Https://172.16.16.16:4444 JUST like the UTM [:)]
In this case, screen shots of your SFOS vbox Network configuration and that of your connecting CLIENT would greatly help.
If I understand you correctly, see attached.