skip to content

SMB

SMB 2 and 3 share files, printers and named pipes over port 445, negotiate a dialect, then sign or encrypt the session. Interviewers ask which settings an administrator sets and what to audit.

on this pageshow

explore

questions

18

Why do security baselines say SMBv1 must go, and what was Microsoft's March 2017 MS17-010 bulletin about?

level: juniorimportance: must knowfreq 66%

answer

  1. oldest dialect, replaced from 2007
  2. publicly deprecated in 2014
  3. no longer installed by default
  4. March 2017, rated Critical, SMBv1 server
  5. a patched server can still run it

basics

~10 s

SMBv1 is the original SMB dialect, superseded by SMB 2 from 2007 and publicly deprecated by Microsoft in 2014. MS17-010 (14 March 2017, Critical) corrected how the SMBv1 server handles specially crafted requests.

solid answer

~50 s

SMBv1 is the CIFS-era dialect. SMB 2 replaced it starting in 2007 (Windows Vista, Windows Server 2008), Microsoft publicly deprecated it in 2014, and from Windows 10 version 1709 and Windows Server version 1709 it is no longer installed by default on a clean installation (Windows 10 Home and Pro kept the client for a time); a clean Windows 11 or Windows Server 2019 and later has neither the SMBv1 client nor server. It also falls outside what SMB 3.1.1 adds to protect negotiation. MS17-010 is a dated bulletin: published 14 March 2017, rated Critical, titled "Security Update for Microsoft Windows SMB Server", covering CVE-2017-0143 to CVE-2017-0148, fixed by correcting how the SMBv1 server handles specially crafted requests. Microsoft listed no mitigating factors and one workaround, disabling SMBv1. For a review: the update tells you a release carries the correction, not that SMBv1 is off.

go deeper

for a junior

Recall that SMBv1 is the old dialect, deprecated in 2014, absent by default from current Windows, and that MS17-010 was a March 2017 critical fix for the SMBv1 server.

for a middle

Explain what SMB 2 added, which releases stopped installing SMBv1, and why Microsoft's workaround for the bulletin was to disable the protocol.

for a senior

Separate three evidence items an auditor needs: the fix is installed, the server setting is off, and the audit trail shows no SMBv1 attempts.

for a principal

Frame SMBv1 as a dated hazard with a dated fix: argue for removing the dependency rather than relying on a patch level that says nothing about exposure.

## What SMBv1 is and where it sits in history **SMBv1** (also called **CIFS** in older documents) is the first generation of the Server Message Block protocol, Windows's file-sharing protocol. Microsoft's page on SMBv1 defaults says SMB 2 and later superseded it "starting in 2007", and that Microsoft publicly deprecated SMBv1 in 2014. Every Windows release since Windows Vista and Windows Server 2008 speaks SMB 2 as well, so SMBv1 is only needed to talk to a device that knows nothing newer. Microsoft's "detect, enable and disable" page lists what SMB 2 added over SMBv1: - request compounding and larger reads and writes - durable handles that reconnect after a short disconnection - message signing with HMAC SHA-256 instead of MD5 - better scalability in shares, users and open files, and symbolic links Microsoft says the devices that still need SMBv1 are not likely running Windows but older or third-party file-sharing software, often itself out of support. ## Why a baseline treats it as a liability 1. **It is the one dialect the modern protections do not reach.** SMB 3.1.1 hashes its NEGOTIATE and SESSION_SETUP exchange into key derivation (pre-authentication integrity), but Microsoft's SMB security page says that feature does not prevent a downgrade to SMB 1.0. That is why the same page tells administrators to disable the SMB 1.0 server. 2. **Its signing is the old MD5 kind**, not the HMAC-SHA256, AES-CMAC or AES-GMAC family of SMB 2 and 3. 3. **A critical flaw was found in its server code.** That is MS17-010 below. Microsoft's own page says SMBv1 "has known security issues regarding ransomware and other malware" and strongly recommends not reinstalling it. 4. **Switching it off costs little on a current estate, with one visible side effect.** The Computer Browser service relies on SMBv1 and is uninstalled with it, so Explorer's Network view stops listing Windows computers through legacy NetBIOS datagram browsing; Microsoft recommends mapped drives and printers instead. ## MS17-010 as dated history | Item | What the bulletin says | |---|---| | Published | 14 March 2017, version 1.0 | | Title | Security Update for Microsoft Windows SMB Server (4013389) | | Rating | Critical for all supported releases at the time | | Component | the Microsoft SMBv1 server | | Fix | corrects how SMBv1 handles specially crafted requests | | CVEs | CVE-2017-0143 through CVE-2017-0148 (one of the six is rated Important, an information disclosure) | | Mitigating factors | none identified | | Workaround | disable SMBv1 (clear the SMB1.0/CIFS File Sharing Support feature) | The bulletin lists Windows Vista, 7, 8.1, RT 8.1 and 10 (the original release, 1511 and 1607), and Windows Server 2008, 2008 R2, 2012, 2012 R2 and 2016, Server Core installations included, each with its own update number (for example 4013429 for Windows 10 version 1607 and Windows Server 2016). Releases not listed are, in the bulletin's words, "either past their support life cycle or are not affected". This question stops at what the bulletin was and which releases carry the fix. ## Defaults by release | Release | SMBv1 after a clean installation | |---|---| | Windows 10 version 1709, Windows Server version 1709 | no longer installed by default (Windows 10 Home and Pro 1709 kept the client; Windows 10 Pro 1809 and later does not) | | Windows Server 2019 and later | neither client nor server | | Windows 11 | neither client nor server | | Windows Server 2016 and Windows 10 | SMBv1 can still be reinstalled | In-place upgrades of Enterprise, Education and Pro for Workstations editions do not remove it automatically; an administrator has to decide. Cite the Microsoft page last updated 2025-06-18 and say so. ## What an auditor should take from the bulletin 1. The update for the server's release is installed, which shows the correction is present. 2. `Get-SmbServerConfiguration | Format-List EnableSMB1Protocol` shows whether the SMBv1 server is still enabled. Microsoft notes this works without elevation. 3. Auditing with `AuditSmb1Access` shows whether anything still asks for SMBv1; that is the next question's subject. A patched but enabled SMBv1 server passes the first check and fails the other two. The bulletin never claimed otherwise: its only workaround was to switch the protocol off.

  • Does installing the MS17-010 update on a Windows server mean SMBv1 is turned off there?
    No. The update corrects how the SMBv1 server handles specially crafted requests; it does not change whether SMBv1 is enabled. A server that had SMBv1 on before the update has it on after. Check `Get-SmbServerConfiguration | Format-List EnableSMB1Protocol`, and turn on auditing to see whether anything uses it.
  • A reviewer asks for the Windows 10 Home and Pro position on SMBv1. What does Microsoft's page say?
    On the page last updated 2025-06-18: Windows 10 Home and Pro version 1709 still contained the SMBv1 client by default after a clean installation, and uninstalled it automatically after 15 days without use. Windows 10 Pro from version 1809 no longer contains the client. The 15-day removal is a one-time operation.
  • After SMBv1 is gone, why does Explorer's Network view stop listing Windows computers?
    The Computer Browser service depends on SMBv1 and is uninstalled with it, so legacy NetBIOS datagram browsing no longer works. Microsoft suggests mapping drives and printers, or in small workgroups starting the Function Discovery Provider Host and Function Discovery Resource Publication services.

  • A patched SMBv1 server is fine to leave enabled
  • Installing the MS17-010 update switches SMBv1 off
  • Windows 11 still installs the SMBv1 server by default
  • SMB 3.1.1 pre-authentication integrity makes SMBv1 safe to keep
  • Disabling SMBv1 also breaks SMB 2 and SMB 3 clients
open as a page

In SMB on Windows, what are the default administrative shares C$, ADMIN$ and IPC$, and how do you turn the automatic ones off?

level: juniorimportance: must knowfreq 62%

basics

~20 s

C$ and its siblings expose local disks, ADMIN$ is reserved for remote administration, and IPC$ is the pipe share that carries named-pipe RPC. Set-SmbServerConfiguration -AutoShareServer $false -AutoShareWorkstation $false turns off the default server and workstation shares.

open as a page

On a Windows file server, how does SMB signing differ from SMB 3 encryption, and which settings turn each one on?

level: juniorimportance: must knowfreq 62%

basics

~20 s

SMB signing adds a signature to every message so tampering is detected, but the data stays readable on the wire. SMB 3 encryption hides the data and also protects its integrity, at a higher CPU cost.

open as a page

How do you find out whether any client still uses SMBv1 on a Windows file server before switching it off?

level: middleimportance: must knowfreq 54%

basics

~10 s

On Windows, read EnableSMB1Protocol with Get-SmbServerConfiguration, turn on Set-SmbServerConfiguration -AuditSmb1Access $true, and watch event 3000 in the SMBServer\Audit log. Clients log events 32002 or 32000.

open as a page

On a Windows SMB file server, how do share-level and file-system permissions differ, and what does a denial of each look like in the audit log?

level: middleimportance: must knowfreq 48%

basics

~20 s

A share has its own access list (Read, Change or Full), checked separately from the ACL on the files. Microsoft's event 5145 page says a failure is logged only for a share-level denial, never for a file-system one.

open as a page

Why does a Windows 11, version 24H2 client refuse a third-party NAS share that cannot sign, and how should you fix it?

level: middleimportance: must knowfreq 54%

basics

~20 s

Windows 11, version 24H2 requires signing on outbound connections, so a device that cannot sign fails with STATUS_INVALID_SIGNATURE (0xc000a000). Enable signing on the device or replace it; turning signing off on clients is the discouraged workaround.

open as a page

Which ports and transports does SMB use, and what should an edge firewall do with TCP 445, 139 and UDP 443?

level: middleimportance: should knowfreq 48%

basics

~20 s

SMB uses direct TCP 445; NetBIOS over TCP 139 is the legacy transport; SMB over QUIC uses UDP 443. Block TCP 445 at the internet edge both inbound and outbound, and offer remote access with SMB over QUIC if needed.

open as a page

In a packet capture of one SMB 2 or 3 connection, why do two negotiate exchanges appear, and what does 0x02FF mean?

level: middleimportance: should knowfreq 24%

basics

~20 s

A client that is not sure the server speaks SMB 2 sends an SMB1-framed NEGOTIATE listing the strings "SMB 2.002" and "SMB 2.???". The server replies with an SMB2 NEGOTIATE response; 0x02FF tells the client to send the real SMB2 NEGOTIATE.

open as a page

In SMB on Windows, what does access-based enumeration do for a share, and how does Samba's access based share enum differ?

level: middleimportance: should knowfreq 26%

basics

~20 s

Access-based enumeration (Set-SmbShare -FolderEnumerationMode AccessBased) stops SMB listing files and folders a user has no rights to; the default is Unrestricted. Samba's access based share enum instead hides the share itself from users without share access, using share permissions only.

open as a page

In SMB, how does DCE/RPC use the ncacn_np protocol sequence, and what do the IPC$ share and a pipe such as srvsvc contribute?

level: middleimportance: should knowfreq 24%

basics

~20 s

With ncacn_np, RPC runs directly over SMB: the endpoint is a named pipe opened on the IPC$ pipe share, and each RPC message is a pipe write or read. A pipe such as srvsvc is one interface's endpoint, used for share administration.

open as a page

Where can Windows require SMB encryption, and what does an encrypted share do to a client that cannot do SMB 3?

level: middleimportance: should knowfreq 34%

basics

~20 s

Windows requires encryption per share, for the whole server, per mapped drive, or for all outbound connections of a 24H2 client. With RejectUnencryptedAccess at its default of true, a client without SMB 3 is refused and the server logs event 1003.

open as a page

Which algorithm signs an SMB session on each dialect, and why do Kerberos and connecting by name matter to its strength?

level: middleimportance: should knowfreq 26%

basics

~10 s

SMB 2.0.2 and 2.1 sign with HMAC-SHA256, 3.0 and 3.0.2 with AES-128-CMAC, and 3.1.1 with a negotiated algorithm, AES-128-GMAC on Windows 11 and Server 2022 and later. All keys derive from the session key.

open as a page

Can a Windows Server 2025 file server raise its SMB dialect floor to 3.1.1, and what would that cut off?

level: seniorimportance: should knowfreq 17%

basics

~20 s

Yes: on Windows Server 2025 or Windows 11 24H2, Set-SmbServerConfiguration -Smb2DialectMin SMB311 refuses older dialects. Clients whose highest dialect is 3.0.2 or lower, such as Windows 8.1, can no longer connect, so inventory dialects first.

open as a page

To show an auditor who opened a Windows file share last week, how do events 5140 and 5145 differ and which audit subcategories must be on?

level: seniorimportance: should knowfreq 34%

basics

~20 s

Event 5140, from Audit File Share, is written once per session at the first access to a share. Event 5145, from Audit Detailed File Share, is written per file or folder and adds the Relative Target Name.

open as a page

Before requiring SMB signing or encryption across a mixed estate, how do you find which clients and servers would break?

level: seniorimportance: should knowfreq 22%

basics

~10 s

Enable the SMB audit parameters first: AuditClientDoesNotSupportSigning and AuditClientDoesNotSupportEncryption on servers, AuditServerDoesNotSupportSigning and AuditServerDoesNotSupportEncryption on clients. They only log, so read the events, fix or replace what shows up, then require.

open as a page

What does SMB 3.1.1 pre-authentication integrity protect, and which downgrade does it still leave open?

level: seniorimportance: nice to knowfreq 12%

basics

~20 s

SMB 3.1.1 hashes the NEGOTIATE and SESSION_SETUP exchange with SHA-512 and feeds the result into key derivation, so tampering breaks the keys and the connection drops. It does not prevent a downgrade to SMB 1.0.

open as a page

Which Windows policies and registry values decide what an anonymous null-session SMB client can reach on a file server, and what are their defaults?

level: seniorimportance: nice to knowfreq 14%

basics

~20 s

The policy "Restrict anonymous access to Named Pipes and Shares" sets RestrictNullSessAccess (Enabled by default), limiting null sessions to the pipes and shares listed in NullSessionPipes and NullSessionShares. "Let Everyone permissions apply to anonymous users" is Disabled by default.

open as a page

What does the SMB client's BlockNTLM setting do on Windows 11, version 24H2, and what must be true of the servers it connects to?

level: seniorimportance: nice to knowfreq 10%

basics

~20 s

On Windows 11, version 24H2 and Windows Server 2025, Set-SmbClientConfiguration -BlockNTLM $true makes the SMB client refuse NTLM on its outbound connections. The server must allow Kerberos (or PKU2U), so connect by name, not IP address, or list an exception.

open as a page