SMB Version 1 Enabled
The host supports SMB version 1, an obsolete file sharing protocol that lacks the protections of SMB 2 and 3 and has been the target of wormable exploits.
| Severity | Medium |
| CVSS 3.1 | 4.8 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N Open in the calculator |
| CVSS 4.0 | 6.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-327: Use of a Broken or Risky Cryptographic Algorithm |
| OWASP Top 10 | A04:2025 Cryptographic Failures |
| MITRE ATT&CK | T1210 Exploitation of Remote Services, T1557 Adversary-in-the-Middle |
| Category | Security Misconfiguration |
Description
The host accepts connections using version 1 of the Server Message Block protocol (SMBv1, sometimes called CIFS). SMBv1 was superseded by SMB 2 with Windows Vista and Windows Server 2008, and lacks protections that later versions provide, including pre-authentication integrity, which stops an attacker downgrading a connection, encryption, stronger signing, and the blocking of insecure guest logons. Where both the client and the server support SMBv1, an attacker able to intercept traffic may be able to force a connection down to it and so remove those protections.
SMBv1 does not by itself give an attacker access, but it exposes the host to a class of serious vulnerabilities in the protocol's implementations, such as those fixed by MS17-010 and exploited in the WannaCry and NotPetya outbreaks, whenever updates are missed. It also tends to give unauthenticated users the host's name, domain and operating system version, which helps an attacker choose targets. Microsoft has deprecated it and no longer installs it by default in current Windows releases, but it remains enabled on older systems, on some systems upgraded from older releases, and on appliances, printers and storage devices that only support it, so the practical risk depends on patch levels and on how many systems on the network still use the protocol.
The dialects a host accepts can be checked without credentials, for example with the Nmap smb-protocols script, which lists the NT LM 0.12 (SMBv1) dialect when it is supported, or with NetExec, which reports SMBv1 support for each host. Scanners report it as the SMB version 1 protocol detected or enabled.
Remediation
Remove SMBv1 from servers and clients once nothing depends on it:
- Find remaining SMBv1 users first.
Set-SmbServerConfiguration -AuditSmb1Access $truerecords each SMBv1 connection attempt as event ID 3000 in theMicrosoft-Windows-SMBServer\Auditevent log. - On Windows, remove the feature with
Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol, which restarts the computer. To disable only the server side without a restart, useSet-SmbServerConfiguration -EnableSMB1Protocol $false. - On older Windows releases, set the
SMB1DWORD value to 0 underHKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters, and disable the SMBv1 client withsc.exe config lanmanworkstation depend= bowser/mrxsmb20/nsiandsc.exe config mrxsmb10 start= disabled. - On Samba, set
server min protocol = SMB2_02or higher insmb.conf. - Upgrade or replace appliances, printers and scanners that only support SMBv1, or move them to an isolated network segment until they can be replaced.
Confirm the fix with the Nmap smb-protocols script, which should no longer list the NT LM 0.12 dialect.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.