If you have HTTPs everywhere on, how much harm can a malicious wifi network do?
-
This is resolved in TLS 1.3 with ECH. Adoption is still not wide though, so you're concern is valid.
-
Was not aware ECH was actually in TLS 1.3 thanks for that. But yes it will take a long time for widespread adoption.
-
Https only encrypts the packet content.
What can happen:
TL;DR:
Evesdropping, spoofing, device vulnerabilities (e.g. using exposed ports).- Attackers can listen and log to which servers you're talking to. This can be combined with the attack explained in the following.
- The can do spoofing attacks by replying to your DNS request with their own IP. For example: you open domain.com and the attacker will not forward domain.com to the trusted DNS server but will instead send you their own IP and website that looks exactly like the website you intent to visit. Since they control this spoofed website they can also intercept all the credentials you enter. If you don't enter credentials or upload or download stuff, nothing can happen. However you'll be safe from spoofing attacks in most cases as popular websites use HSTS which hardcodes the IP addresses corresponding to domains result into your browser, bypassing DNS.
- An attacker could exploit device vulnerabilities that are unrelated to https web traffic. So make sure your OS and software are up to date and you don't have applications running with exposed ports!