5 ms·
But if you need to have the malicious DNS server connected as a requirement, aren't you already owned? The DNS server can tell you the bank's hostname is a mali
by chii 8y ago
But if you need to have the malicious DNS server connected as a requirement, aren't you already owned? The DNS server can tell you the bank's hostname is a malicious IP, and then you can both steal credentials, or MITM.
- AstralStorm 8y agoAnd the prevention is the same, verify DNSSEC, at least for a set of critical domains - starting with anything TLS related perhaps.
- tptacek 8y agoDNSSEC does nothing to prevent DNS rebinding attacks.
- tptacek 8y agoNo, the malicious DNS server is the one for the domain the attacker controls, not the target.
- chii 8y agoBut if you use a DNS server that's not trustworthy, how can you be sure that the site you're seeing is indeed the correct one?
- tptacek 8y agoI think you're confusing authority servers, which control the content for domains, and query resolvers. This attack works because it only requires an attacker to control an authority server, any authority, on the whole Internet. They can just register a domain to do this with.
- netheril96 8y ago> But if you need to have the malicious DNS server connected as a requirement, aren't you already owned? DNS replies can be modified by anyone in the network path, so it is far more than just compromised DNS server. > The DNS server can tell you the bank's hostname is a malicious IP, and then you can both steal credentials, or MITM. All banks use HTTPS for their websites. A malicious IP is no t enough, unless it also has a forged certificate for the domain.