Ravindra BagaleCourses & study guides मराठी Track your progress

37. Enumeration: NetBIOS, SMB, SNMP, LDAP, SMTP, NFS and DNS

37.2 NetBIOS and SMB Enumeration

By Last updated:

Windows / Samba networks var NetBIOS (137/138/139) ani SMB (445) shares, workgroups, usernames leak karu shaktat – jar misconfigured asel.

Name lookup / null session concepts (lab):

# NetBIOS name query (Metasploitable often responds)
nmblookup -A 192.168.56.20

# List shares – try guest / no password carefully (lab only)
smbclient -L //192.168.56.20 -N
smbclient //192.168.56.20/tmp -N

enum4linux – classic one-shot SMB/NetBIOS enum wrapper (users, shares, OS info when allowed):

sudo apt install -y enum4linux
enum4linux -a 192.168.56.20

CrackMapExec / NetExec – modern SMB enum / auth testing framework. Concept: spray credentials, list shares, check signing. Deep AD abuse Chapter 38 madhe; ithe fakt idea:

# NetExec (nxc) – share list against lab host (no spray on real networks)
nxc smb 192.168.56.20 --shares

Null session: unauthenticated IPC$ connection – junya Windows/Samba setups madhe user/share lists yetat. Modern systems var band asayla hava.

Defence: SMBv1 disable kara; guest / anonymous shares band; require authentication (प्रमाणीकरण); firewall madhe 445/139 fakt trusted VLAN; SMB signing enable; patch Samba/Windows. Lakshat theva.

Ravindra Bagale's Tip

When smbclient -L fails, students say "the tool is broken". A failure is often a good sign – guest access is disabled. Enum success = misconfiguration. Defender mindset: if your lab's share list came out, run the same check on production and close it.

Lab

Metasploitable (192.168.56.20) var nmblookup -A, smbclient -L //192.168.56.20 -N ani enum4linux -a chalaa. Konti shares/users distat te note kara. Mag aaplya Amazon Linux Samba (jar asel) var guest share nahi he confirm kara – sudo service smb status (kiwa smbd).

Extended teaching notes

Why this lesson matters

Enumeration maps what a network exposes. Defenders use the same ideas to close shares, fix SNMP community strings, restrict LDAP binds and stop zone transfers.

Hardening related services

[('SSH', 'Key auth, no root login, Fail2ban or equivalent, SG limited to your IP/VPN.', '', ''), ('SMB / NFS / LDAP / SNMP', 'Do not expose to the internet; patch; strong auth; disable unused versions (e.g. SMBv1).', '', ''), ('SMTP', 'Authenticated relay only; SPF/DKIM/DMARC for your domains.', '', ''), ('DNS', 'Restrict zone transfers; monitor for unexpected records (crt.sh for certs).', '', ''), ('Firewalls', 'Host firewall + cloud SG/NSG; default deny; document every allow.', '', '')]

Lab rule

Run enumeration only against host-only lab VMs you own. Then write the defensive fix for each open service you found.

Mini case study

Suppose we are on a purple-team exercise for an Indian mid-size company (sample data). Red notes a technique from this lesson against a lab clone. Blue must show the control that stops it, the log that would have fired, and the ticket that hardens production. That is the standard this course trains you for.

Defender's worksheet (do this today)

  1. Write the lesson title, date and the exact lab target you are allowed to use.
  2. List three owned systems (VMs, apps, or cloud accounts) where this lesson applies.
  3. Run one safe check from the lesson on a lab system only. Paste the command and output.
  4. Write a two-sentence fix you would give a teammate.
  5. Name one related public advisory (CERT-In, CISA, NVD, or a vendor bulletin) with its date.

Indian workplace (sample data)

Suppose we are a junior analyst at Infosys, TCS, Wipro or a fintech SOC in Bengaluru/Pune. Turn this lesson into one checklist item with an owner, a due date and a place to store evidence (ticket + screenshot).

Global practice

Compare your notes with OWASP, CIS Benchmarks, NIST CSF/IR guidance or a cloud Well-Architected security question. Write five lines on what overlaps.

Everyday analogy

Explain the risk and the fix to a family member without jargon. If they can repeat the warning, you understand it well enough to teach juniors.

Key terms

  • Control: a safeguard (patch, config, process, detection).
  • Finding: a weakness backed by evidence.
  • Remediation: the fix plus how you verified it.
  • Scope: systems you have written permission to touch.
  • Least privilege: only the access the task needs.
  • Defence in depth: several layers so one failure does not end the story.

Common mistakes

  • Skipping written permission "just for a quick scan".
  • Practising on hostel, office or public targets without authorisation.
  • Collecting tool output without writing the fix.
  • Copying attack steps onto production to "verify". Defenders verify with versions, configs and patches.
  • Publishing screenshots that contain secrets, cookies or internal hostnames.

Recap

  • Evidence, fix, owner, date.
  • Own lab only.
  • Fix > spectacle.