74f5fb5ac7
Currently there is just one anti-spoofing firewall rule ensuring packets coming through vif+ interfaces have the right source address. Add another rule ensuring that addresses that belongs to VMs behind those vif+ interface do not appear on other interfaces (specifically eth0, but also physical ones). Normally it wouldn't be an issue because of rp_filter (doing the same based on route table), default DROP in FORWARD chain and also conntrack (the need to guess exact port numbers and sequence numbers). But it appears all three mechanisms are ineffective in some cases: - rp_filter in many distributions (including Fedora and Debian) was switched to Loose Mode, which doesn't verify exact interface - there is a rule in FORWARD table allowing established connections and conntrack does not keep track of input/output interfaces - CVE-2019-14899 allows to guess all the data needed to inject packets Reported-by: Demi M. Obenour <demiobenour@gmail.com> |
||
---|---|---|
.. | ||
30-qubes-external-ip | ||
80-qubes.conf | ||
ip6tables | ||
ip6tables-enabled | ||
iptables | ||
iptables-updates-proxy | ||
Makefile | ||
network-manager-prepare-conf-dir | ||
nm-30-qubes.conf | ||
qubes-fix-nm-conf.sh | ||
qubes-iptables | ||
qubes-nmhook | ||
qubes-setup-dnat-to-ns | ||
qvm-connect-tcp | ||
setup-ip | ||
show-hide-nm-applet.desktop | ||
show-hide-nm-applet.sh | ||
tinyproxy-updates.conf | ||
tinyproxy-wrapper | ||
udev-qubes-network.rules | ||
update-proxy-configs | ||
updates-blacklist | ||
vif-qubes-nat.sh | ||
vif-route-qubes |