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.
References
| Link | Resource |
|---|---|
| https://github.com/cifsd-team/ksmbd/pull/551 | Patch Third Party Advisory |
| https://github.com/cifsd-team/ksmbd/issues/550 | Third Party Advisory |
| https://marc.info/?l=linux-kernel&m=163961726017023&w=2 | Third Party Advisory |
| https://security.netapp.com/advisory/ntap-20220107-0001/ |
Configurations
Configuration 1 (hide)
| AND |
|
Information
Published : 2021-12-16 05:15
Updated : 2022-01-10 14:10
NVD link : CVE-2021-45100
Mitre link : CVE-2021-45100
JSON object : View
Products Affected
linux
- linux_kernel
ksmbd_project
- ksmbd
CWE
CWE-319
Cleartext Transmission of Sensitive Information
