Open In App

SNMP Enumeration

Last Updated : 28 Jul, 2025
Comments
Improve
Suggest changes
Like Article
Like
Report

Simple Network Management Protocol (SNMP) is an application-layer protocol that operates over UDP to manage and monitor network devices, such as routers, hubs, and switches.

  • SNMP is widely used across various operating systems such as Windows Server and Linux.
  • It is also implemented on network devices like routers, switches, and hubs.
  • SNMP agents are deployed on these devices to enable network management.
  • It helps facilitate tasks such as monitoring performance, configuring settings, and troubleshooting issues in IP-based networks.

On a target system, SNMP enumeration is used to list user accounts, passwords, groups, system names, and devices.

Working of SNMP Enumeration

There are some steps that define the workflow of SNMP Enumeration.

  • Step 1: The attacker or administrator identifies the IP address of a device that has an SNMP service running.
  • Step 2: Discover the String Community.
  • Step 3: Initiate SNMP Requests.
  • Step 4: Extract OID Values.
  • Step 5: Analyze and Document Findings.

Tools Used in SNMP

Kali Linux includes several powerful SNMP (Simple Network Management Protocol) tools used for network enumeration, device information gathering, and vulnerability assessment.

Here’s a list of essential SNMP tools in Kali Linux along with their use cases:

1 . "snmpwalk"

It is a command line utility used to recursively query SNMP enabled devices for a hierarchy of information, beginning from a specified OID (Object Identifier). It communicates using the Simple Network Management Protocol (SNMP) to retrieve structured data such as system details, network interface statistics, running services, and other management information. This tool is especially useful for network enumeration, device monitoring, and auditing SNMP configurations.

Syntax:

snmpwalk -v [version]1 -c [community] [target IP]
here,
        v- version (1.9,2.0,2.1)
       c- communtity ( public or private )  

Some Common Options:

Here are some common options in 'snmpwalk'

OptionDescription
-tTimeout (in seconds).
-rNumber of retries.
-OsDisplay only last symbolic name part (short output).
-OnDisplay numeric OIDs (useful for scripting).
-OePrint enums numerically.
-OqQuick print (value only).
-CcDo not check whether the returned OIDs are increasing (faster for some agents).
-mMIB module to load. Use ALL to load all MIBs.
-MPath to search for MIB files.

Example:

snmpwalk -v1.9 -public 192.168.2.4
snmp

Use Case:

  • To find active network interfaces.
  • Show the inventory SNMP enabled devices.
  • It used to assist in vulnerability assessments.

2. "snmpget"

It is a command line utility to retrieve a specific SNMP object identifier (OID) from a target device, you can use the snmpget command. This command queries a specific OID and returns its value.

Syntax:

snmpget -v[version] -c[community] <target_ip> <OID>
here,
        v- version (1.9,2.0,2.1)
       c- communtity ( public or private )  
       OID- Object Identifier

Example:

snmpget -v1.9 -public 192.168.1.1 1.3.6.1.2.0.1.1.1.1
image

Use Case:

  • Used to fetch a specific SNMP Object Identifier (OID) from a device without querying the entire SNMP tree.
  • Ideal for environments where minimal network traffic is preferred, since it retrieves only one value per request.
  • Helps network administrators verify the current state of specific components quickly.

3. "snmpbulkwalk"

snmpbulkwalk is similar to snmpwalk, but it is optimized for retrieving large sets of SNMP data by reducing the number of packets exchanged, making it ideal for traversing extensive SNMP trees using SNMPv2c or SNMPv3.

Syntax:

snmpwalk -v [version]1 -c [community] [target IP]  
here,
       v- version (1.9,2.0,2.1)
      c- communtity ( public or private )  

Exmaple:

snmpbulkwalk -1.9 -public 192.168.1.1
snmmm

Use Case:

  • Perfect for extracting complete branches like interface lists, routing tables, or system statistics.
  • Fewer packets are sent between client and target device, making it faster and more efficient on congested networks.
  • Commonly integrated into NMS (Network Management Systems) for regular polling of metrics.

4. "nmap"

Nmap includes NSE (Nmap Scripting Engine) scripts that facilitate SNMP enumeration. Nmap allowing users to collect detailed information from SNMP enabled devices such as system descriptions, network interfaces, and active processes.

Syntax:

nmap -sU -p 161 --script=snmp* [target IP]

Example:

nmap -sU -p 161 --script=snmp* 192.168.1.7
nmap

Use Case:

  • Identify whether SNMP service (UDP port 161) is running on a target device.
  • Detect SNMP misconfiguration
  • Identify SNMP-related vulnerabilities or software versions that may be outdated.

Component of SNMP Enumeration:

SNMP Enumeration is made up of three major parts:

  1. Managed Device: A managed device is a device or a host (technically referred to as a node) that has the SNMP service enabled. These devices include routers, switches, hubs, bridges, computers, and so on.
  2. Agents: An agent is a software component that runs on a managed device. Its primary function is to convert data into an SNMP-compatible format for network management via the SNMP protocol.
  3. Network Management System (NMS) : NMS are software systems that are employed to monitor network devices.

SNMP Architecture

The architecture of SNMP Enumeration:

SNMP Enumeration
  1. Management Agent: An application that resides in managed devices such as hosts, bridges, routers, and so on. The agent responds to the operative's requests for data and actions and may send asynchronous messages to the operative in the event of a critical event.
  2. Management Station: It serves as the human network manager's interface to the network management station (or network operation center NOC), from which he monitors and manages the network and assists in fault recovery.
  3. Network Management Protocol: The network management protocol (SNMP) is used to transfer data and commands between agents and managing entities. For communication between managers and agents, SNMP employs the User Datagram Protocol (UDP) as the transport protocol. The reasons for exploitation of UDP for SNMP area unit are as follows:
    1. First, it has low overheads in comparison to the protocol, which uses a 3-way handshake for the association. 
    2. Second, in large networks, SNMP over protocol may be a risky strategy because the protocol to ensure dependability can flood the network with retransmissions. SNMP sends and receives requests on UDP port 161, and receives traps from managed devices on UDP port 162.
  4. Management database (MIB) : A management database is represented as a collection of managed objects. These objects together form the MIB virtual database. Although an agent may implement multiple MIBs, all agents must implement a single MIB, known as MIB-II. This standard defines variables for things like interface statistics (interface speeds, MTU, octets sent, octets received, and so on) as well as various other things related to the system itself (system location, system contact, etc.). MIB-primary II's goal is to generate general TCP/IP management data.

Protective Measure from SNMP Enumeration

To prevent unauthorized access and data leakage through SNMP enumeration, it's essential to implement good security practices across your network infrastructure.

  1. SNMP agents on hosts should be removed or disabled.
  2. All perimeter network access devices should block port 161.
  3. Access should be limited to specific IP addresses.
  4. Make use of SNMPv3 (more secure)
  5. Add the Group Policy security option “Additional restrictions for anonymous connections" to your configuration.
  6. Null session pipes, null session shares, and IPsec filtering should all be restricted as well.

Conclusion

SNMP security is critical in protecting network devices, routers, switches, and IT infrastructure from SNMP enumeration attacks and unauthorized access. As SNMP agents store system information, user accounts, and network configurations, attackers exploit default community strings to gain information.

Organizations must implement the following to prevent SNMP enumeration and cyber attacks:

  • Disable SNMP agents for unused hosts.
  • Restrict SNMP access to specified IP addresses.
  • Block UDP port 161 on perimeter network devices.
  • Transition to SNMPv3 for encrypted authentication and secure communication.
  • Implement security policies like Group Policy limitations and IPsec filtering.

Similar Reads