Since DirectAdmin maintains its own CSF ‘fork’ and quite a lot of DirectAdmin servers are still running CSF, is DA aware of these vulnerabilities and are there plans to release fixes for the DirectAdmin version?
Why? That is good for admins with a more dynamic ip, right?I would go ahead and remove the DynDNS feature as well.
Well...Why? That is good for admins with a more dynamic ip, right?
Sorry, could be me but I don't get it. I don't see the fun about the dyndns option related to that.*nudge* *nudge* *wink* *wink*
Well, the one who controles the dns, controls your firewall. Or threat actors using cachepoisoning can get themselves fully whitelisted and disable any FW blocks completely for that ip. Every dns change is like russian roulette, at least for a while. And those are just a few issues...Sorry, could be me but I don't get it. I don't see the fun about the dyndns option related to that.
Sorry, could be me but I don't get it. I don't see the fun about the dyndns option related to that.
This is only a part of it. URLGet has a serious flaw in it too, allowing infection if an attacker can control that URL. But there is more..I think that it was already discussed:
@DanielP, the default DA installation is not affected. There is a vulnerability in the CSF captcha/messenger feature. Users who manually enabled it are effected. We are planing to release new CSF build with captcha/messenger feature completely removed.