5 ms·
As this is a protocol level vulnerability, older versions of Samba were also affected. Security release announcement is here: https://www.samba.org/samba/secu
by jra_samba 6y ago
As this is a protocol level vulnerability, older versions of Samba were also affected.
Security release announcement is here:
https://www.samba.org/samba/security/CVE-2020-1472.html https://www.samba.org/samba/security/CVE-2020-1472.html
After a previous vulnerability we changed our defaults to require schannel for release 4.8, which protects against the CVE-2020-1472 problem, but admins could turn off this protection to work with older/less secure products.
Further hardening of Samba is currently taking place to protect our users from the bug.
- deleted 6y ago[deleted]
- malwarebytess 6y agoDoes this mean that any server that uses Samba, windows or not, is vulnerable?
- tcmb 6y agoLooks like it, there is also a security issue released for Ubuntu: https://usn.ubuntu.com/4510-1/ https://usn.ubuntu.com/4510-1/
- secabeen 6y agoOnly if you are running the Samba DC functionality, which is non-default. Also, you would have needed to specifically disable the protection that was added by Samba in 2018.
- deleted 6y ago[deleted]
- tialaramex 6y agoIf the server provides Domain Controller capability then yes, it implements NetLogon, Microsoft's NetLogon protocol is vulnerable to this attack by design and so Samba in that scenario is potentially vulnerable and has the same mitigation strategy that Microsoft applied. If it's not a Domain Controller then this is irrelevant.