5 ms·

These exploits rely upon the ports being exposed on localhost. Even if you are not (as you should) using ssh tunneling to the VM, any exposed ports are on a sep

by teilo 10y ago

These exploits rely upon the ports being exposed on localhost. Even if you are not (as you should) using ssh tunneling to the VM, any exposed ports are on a separate IP address, not localhost. However, if one is forwarding ports to the host machine, that's obviously a problem.

Dylan16807 10y ago
These exploits rely upon the ports being exposed on a predictable IP. A lot of setups are going to give you very predictable IPs for the virtual machines.
- lima 10y ago
  Thanks to WebRTC, it's even easier - you can enumerate all local IP addresses and then you only have to scan one or two subnets. Local VMs are definitely vulnerable to this as well.
  - uniclaude 10y ago
    Not if you actually work in the VM, and do not expose database ports to the host (why in hell would you do this anyway). No amount of ip scanning is going to open ports.
    - estefan 10y ago
      > why in hell would you do this anyway Integration with IDEs.
      - uniclaude 10y ago
        > Integration with IDEs. That's a fair point, but Rsync or shared folders should have you covered for this.
        estefan 10y ago
        Actually I meant something like how Intellij has DB integration, so you could put in your host & port and connect to the DB to help you write queries etc.
  - deleted 10y ago
    [deleted]
- manarth 10y ago
  192.168.33.10
AgentME 10y ago
If the user isn't using ssh tunneling into the vagrant vm, then this attack still works if the attacker uses the correct IP address instead of localhost.