The ksmbd server through 3.4.2, as used in the Linux kernel through 5.15.8, sometimes communicates in cleartext even though encryption has been enabled. This occurs because it sets the SMB2_GLOBAL_CAP_ENCRYPTION flag when using the SMB 3.1.1 protocol, which is a violation of the SMB protocol specification. When Windows 10 detects this protocol violation, it disables encryption.
The product transmits sensitive or security-critical data in cleartext in a communication channel that can be sniffed by unauthorized actors.
Link | Tags |
---|---|
https://github.com/cifsd-team/ksmbd/issues/550 | third party advisory |
https://github.com/cifsd-team/ksmbd/pull/551 | third party advisory patch |
https://marc.info/?l=linux-kernel&m=163961726017023&w=2 | third party advisory |
https://security.netapp.com/advisory/ntap-20220107-0001/ | third party advisory |