CVE-2021-45100
published 2021-12-16CVE-2021-45100: 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…
PriorityP338high7.5CVSS 3.1
AVNACLPRNUINSUCHINAN
EPSS
0.91%
56.3th percentile
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.
Affected
5 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | linux | < linux 5.15.15-1 (bookworm) | linux 5.15.15-1 (bookworm) |
| ksmbd_project | ksmbd | <= 3.4.2 | — |
| linux | linux_kernel | >= 0 < 5.15.15-1 | 5.15.15-1 |
| linux | linux_kernel | >= 0 < 5.15.15-1 | 5.15.15-1 |
| linux | linux_kernel | >= 0 < 5.15.15-1 | 5.15.15-1 |
CVSS provenance
nvdv3.17.5HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:P/I:N/A:N
osv7.5HIGH
vendor_debian7.5LOW
vendor_redhat7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Red Hat
kernel: ksmbd server communicates in cleartext even though encryption has been enabled due to a violation of the SMB protocol specification
vendor_redhat·2021-12-14·CVSS 7.5
CVE-2021-45100 [HIGH] CWE-319 kernel: ksmbd server communicates in cleartext even though encryption has been enabled due to a violation of the SMB protocol specification
kernel: ksmbd server communicates in cleartext even though encryption has been enabled due to a violation of the SMB protocol specification
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.
An unexpected, non-encrypted communication flaw in the Linux kernel's ksmbd (Samba 3 protocol implementation) subsystem was found in the way when user set flag SMB2_GLOBAL_CAP_ENCRYPTION using the SMB 3.1.1 protocol. If during connection flag SMB2_GLOBAL_CAP_ENCRYPTION being u
Debian
CVE-2021-45100: linux - The ksmbd server through 3.4.2, as used in the Linux kernel through 5.15.8, some...
vendor_debian·2021·CVSS 7.5
CVE-2021-45100 [HIGH] CVE-2021-45100: linux - The ksmbd server through 3.4.2, as used in the Linux kernel through 5.15.8, some...
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.
Scope: local
bookworm: resolved (fixed in 5.15.15-1)
bullseye: resolved
forky: resolved (fixed in 5.15.15-1)
sid: resolved (fixed in 5.15.15-1)
trixie: resolved (fixed in 5.15.15-1)
GHSA
GHSA-2872-89wh-3frc: The ksmbd server through 3
ghsa_unreviewed·2021-12-17
CVE-2021-45100 [HIGH] CWE-319 GHSA-2872-89wh-3frc: The ksmbd server through 3
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.
OSV
CVE-2021-45100: The ksmbd server through 3
osv·2021-12-16·CVSS 7.5
CVE-2021-45100 [HIGH] CVE-2021-45100: The ksmbd server through 3
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.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/cifsd-team/ksmbd/issues/550https://github.com/cifsd-team/ksmbd/pull/551https://marc.info/?l=linux-kernel&m=163961726017023&w=2https://security.netapp.com/advisory/ntap-20220107-0001/https://github.com/cifsd-team/ksmbd/issues/550https://github.com/cifsd-team/ksmbd/pull/551https://marc.info/?l=linux-kernel&m=163961726017023&w=2https://security.netapp.com/advisory/ntap-20220107-0001/
2021-12-16
Published