I tried e2guardian in a virtual machine today, running it as a standalone transparent proxy with SSL MITM, with the following iptables rules that redirect traffic to it (where 974 is the uid of the user that e2guardian runs as):
I found that e2guardian enables browser connections to sites that it should not allow. One example is https://wrong.host.badssl.com/
This is very serious, because anyone on the path, who can intercept the connection or poison the DNS cache and thus redirect e2guardian's outgoing connection to a host under his control, now can perform a successful MITM attack. All he needs is any valid certificate - e2guardian will accept it for any host.
The text was updated successfully, but these errors were encountered:
I tried e2guardian in a virtual machine today, running it as a standalone transparent proxy with SSL MITM, with the following iptables rules that redirect traffic to it (where 974 is the uid of the user that e2guardian runs as):
I found that e2guardian enables browser connections to sites that it should not allow. One example is https://wrong.host.badssl.com/
This is very serious, because anyone on the path, who can intercept the connection or poison the DNS cache and thus redirect e2guardian's outgoing connection to a host under his control, now can perform a successful MITM attack. All he needs is any valid certificate - e2guardian will accept it for any host.
The text was updated successfully, but these errors were encountered: