Custom Query (16363 matches)
Results (1321 - 1323 of 16363)
| Ticket | Resolution | Summary | Owner | Reporter |
|---|---|---|---|---|
| #17914 | wontfix | [security] NAT VM bypasses host firewall | ||
| Description |
a NAT VM is able to completely bypass the host firewall and access services on blocked ports. for example, the guest can ping the host (even if host firewall blocks pings) and can access host web server (even if host firewall blocks access to web server). there may be a zillion other non-public host services which are accessible to the guest. affects linux hosts running iptables-based firewall. |
|||
| #17913 | duplicate | documentation indicates (incorrectly) that NAT VM can't communicate with host over network -> duplicate of #16912 | ||
| Description |
https://www.virtualbox.org/manual/ch06.html#networkingmodes Table 6.1 "VM ↔ Host" column has a "–" symbol for NAT, which is misleading, as the guest VM is able to communicate over the network with the host, in fact bypassing the host's firewall (which, btw, seems like a security issue which should also be noted in the documentation, particular since NAT is the default); the guest VM, for example, can ping the host's IP. The host, however, can't ping the guest VM's IP. |
|||
| #17910 | invalid | after windows 10 upgrade no longer able to start my VMs | ||
| Description |
I have a windows 10 machine with several VMs (Ubuntu) installed which were running fine. After Win10 upgrade to 1709 OS Build 16299.551 i cannot access my VMs. Error i get is VT-x is not available (VERR_VMX_NO_VMX). Result Code: E_FAIL (0x80004005) Component: ConsoleWrap Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed} My Machine is a Lenovo ThinkPad T470, I checked the BIOS and virtualization is enabled (never made a change to this setting in BIOS) I tried all the suggestion in this forum https://forums.virtualbox.org/viewtopic.php?f=6&t=84618 but no luck. I reinstalled VB and I tried any other suggestion by googling on this error and still no luck. |
|||

