We’ve written many times about the recently found DNS vulnerability, but it’s clear that many people don’t understand the ins and outs of this kind of flaw. Unlike problems on a client computer, which are generally easy to explain (though, to be honest, “buffer overflow” isn’t plain English), this one’s much more complex. Glenn Fleishman and Rich Mogull, writing at Macworld, have a clear and thorough exposé of the issue, its effects, and how it can be fixed. (Or how it has been, sort of, fixed.) They point out that, even if Mac OS X clients have not been fixed, the risk is minimal.
So, for now, if you are running a Mac OS X server, make sure you apple the recent security update. I’m sure that more info will be coming soon regarding this vulnerability.
