3 ms·
It may be of interest for attackers that have no visibility into your network and make cross site attacks against you easier. For example, if I know that your r
by Xylakant 6y ago
It may be of interest for attackers that have no visibility into your network and make cross site attacks against you easier. For example, if I know that your router is available at router.network.internal, I might just try and see if your browser is logged in and send you a link to a page that starts making requests against that interface. Enumerating network resources can certainly be done via other ways, but DNS is a particularly easy one.
- cassianoleal 6y agoInteresting but 192.168.0.1 or 192.168.1.1 would probably cover 80% of that use case. This is just security by obscurity. It doesn't add much if you already implement actual security in the form of firewalls, network segregation, etc.
- Xylakant 6y agoI agree that it's certainly not a substitute for a proper security setup, but it definitely makes an attackers life easier - up to the point where it may get interesting to automate this. So as always, it's a tradeoff. Both options may be acceptable (and I've run a setup where I'd have internal names exposed on public DNS for years), but you need to be aware of the tradeoff to make that judgement.