Skip to content
AdminKit

Is port 161 (SNMP) exposed to the internet with a default community string?

Port 161 is the default port for SNMP, the protocol network gear uses for monitoring and remote configuration. SNMPv1 and v2c authenticate with a plaintext "community string," and many devices still ship with the default read string "public" unchanged. AdminKit's port-check tool automates nine exposure checks; 161 isn't on that list, so here's how to check it yourself.

By AdminKit team, Netbase JSC · Updated

Key takeaways

  • UDP port 161 is where SNMP agents on routers, switches, firewalls, printers and UPS units take queries. SNMPv1 and v2c protect it with a shared “community string” sent in plaintext.
  • A reachable agent that accepts “public” gives away its configuration, interfaces and software version. CISA’s joint advisory says weak strings, “including the default ‘public’”, let APT28 into routers.
  • The read-only string is also the key to some remote code execution flaws, two of which are in CISA’s Known Exploited Vulnerabilities catalog.
  • AdminKit’s port check does not test 161. Test it from outside with an SNMP client, then turn off v1/v2c, use SNMPv3 with authPriv, and keep 161 on a management network.

Why does SNMP still lean on a shared “community string”?

IANA registers port 161 for SNMP, the Simple Network Management Protocol used across routers, switches, UPS units, printers and countless other network-attached devices to report status and accept configuration changes remotely. SNMPv1 and v2c, still the most widely deployed versions, authenticate with a community string rather than a username and password — a design that made sense when network management traffic was assumed to never leave a trusted internal segment. In practice, many deployed devices still ship with, or get configured with, the default read string “public” and the default write string “private,” and on v1/v2c that string travels in plaintext with no encryption at all.

Software agents are often no stricter. The Net-SNMP snmpd.conf manual notes that its agent’s “default behaviour is to listen on UDP port 161 on all IPv4 interfaces”. On a server with a public address, or behind a forward, that means the internet unless a firewall says otherwise.

Which SNMP versions will you find on port 161?

All three versions use the same port, and one device often answers more than one. What protects the agent depends on which versions are turned on, not which ones the firmware supports:

VersionHow a request is authorizedWhat crosses the networkExposed on the internet
SNMPv1Community stringEverything in plaintext, string includedAnyone who guesses or captures the string can read, and with a write string, change settings
SNMPv2cCommunity stringEverything in plaintext; adds the GetBulk requestSame as v1, plus a better amplifier for DDoS
SNMPv3, noAuthNoPrivUsername onlyPlaintextClose to v1/v2c in practice
SNMPv3, authNoPrivUsername plus authenticationAuthenticated, not encryptedProtected against forged or changed messages; contents readable
SNMPv3, authPrivUsername plus authentication and privacyAuthenticated and encryptedThe level CISA recommends

SNMPv3’s User-based Security Model, RFC 3414, was designed against exactly the threats a public port invites: “modification of information”, “masquerade” (attempting operations “by assuming the identity of another user”), and disclosure by eavesdropping. CISA’s alert TA17-156A puts it plainly: “Configure SNMPv3 to use the highest level of security available on the device; this would be authPriv on most devices.”

How have attackers used exposed SNMP?

This isn’t hypothetical. A joint advisory from CISA, the NSA, the FBI and the UK’s NCSC detailed how the Russian state-linked group APT28 abused SNMP access to Cisco routers — including devices belonging to European and U.S. government institutions and roughly 250 Ukrainian targets. The full advisory, AA23-108, states that “weak SNMP community strings, including the default ‘public,’ allowed APT28 to gain access to router information”, and that APT28 “sent additional SNMP commands to enumerate router interfaces”. A more recent CISA advisory on router hygiene describes Russian FSB-linked actors who “scan for Internet IP ranges with active Simple Network Management Protocol (SNMP) agents that accept common or default community strings” — the same exposure pattern, used as a routine reconnaissance technique rather than a one-off incident.

What does an exposed, default-credentialed SNMP agent give away?

A reachable port 161 with the default read string active typically lets anyone pull the device’s full configuration, interface list, routing information, installed software versions and other operational details with no credential of their own. If the default write string is also active, that same unauthenticated access can be used to change configuration — the exact escalation path documented in the advisories above.

Even the first query is revealing. The documentation for Nmap’s snmp-sysdescr script shows the kind of answer a printer gives to a single request for its system description:

| snmp-sysdescr: HP ETHERNET MULTI-ENVIRONMENT,ROM A.25.80,JETDIRECT,JD117,EEPROM V.28.22,CIDATE 08/09/2006
|_  System uptime: 28 days, 17:18:59 (248153900 timeticks)

That is the make, firmware versions and uptime, enough to look up which advisories apply. A read string is also more than a key to information. Some SNMP flaws are exploitable by anyone holding it:

VulnerabilityWhat NVD and CISA recordWhat the attacker needs
CVE-2017-6742, Cisco IOS and IOS XEBuffer overflow allowing remote code execution or reload; added to CISA’s Known Exploited Vulnerabilities catalog on 19 April 2023; used by APT28“The SNMP read only community string (SNMP version 2c or earlier) or the user credentials (SNMPv3)”
CVE-2025-20352, Cisco IOS and IOS XEStack overflow allowing denial of service or code execution as root; added to the catalog on 29 September 2025The SNMPv2c or earlier read-only community string or valid SNMPv3 credentials, plus higher privileges for code execution

Patching fixes each flaw. Keeping 161 off the internet removes the whole class.

Does SNMPv3 leak anything before login?

A little, by design. RFC 3414 describes a discovery step: a manager sends a request with no username, “and the response to this message will be a Report message containing the snmpEngineID”. RFC 3411’s recommended format for that ID starts with the vendor’s IANA enterprise number and can include an interface’s MAC address. Nmap’s snmp-info script documents output such as enterprise: ciscoSystems and engineIDFormat: mac. So a v3-only agent on the internet still tells a stranger the vendor, sometimes a MAC address, and how long it has been up. That’s far less than v2c gives away, but it is another reason to keep the port on a management network.

Can an exposed SNMP agent be used against others?

Yes. SNMP runs over UDP, so a spoofed request makes your device send its reply to someone else. CISA’s alert on UDP-based amplification attacks (TA14-017A) lists SNMPv2 with a bandwidth amplification factor of 6.3, using the GetBulk request. A device that answers “public” to the internet can be drafted into floods it has nothing to do with.

How do you check your own exposure?

AdminKit’s open ports check checks a fixed nine-port TCP list on your own IP, and port 161 isn’t on it; nothing in that result covers SNMP. Confirm your current public IP first with what is my IP, then test manually from a machine outside your network. SNMP runs over UDP, so a plain nc -u test can’t tell an open agent from a filtered port. Ask a real SNMP question instead. With the Net-SNMP tools, request the system description using the default string, against your own address only (a documentation address is shown):

snmpget -v2c -c public -t 3 -r 1 203.0.113.5 1.3.6.1.2.1.1.1.0
snmpget -v3 -l noAuthNoPriv -u nosuchuser -t 3 -r 1 203.0.113.5 1.3.6.1.2.1.1.1.0
What comes backWhat it meansWhat to do
A STRING: system description to the v2c requestThe agent is reachable and accepts the default string “public”Treat as urgent: block 161 at the edge and change or remove the string today
“Timeout: No Response” to v2c, but an “Unknown user name” error to v3An SNMPv3 agent is reachable; “public” was refused or v2c is offKeep v3 at authPriv and move 161 off the internet
“Timeout: No Response” to bothNo SNMP reply reached youLikely not exposed; repeat once, and test any other management IPs you own

A v1/v2c agent normally ignores a wrong community string rather than refusing it, so a timeout on v2c alone does not prove the port is closed. Since a device can have SNMPv3 support available but still be running v1/v2c for backward compatibility, confirming what’s actually enabled and reachable is more reliable than trusting a spec sheet. On a Linux host you manage, ss -ulnp | grep ':161' shows whether snmpd is bound to all interfaces.

How do you fix it?

  • Change any default community string immediately — “public” and “private” should never remain in production on an internet-reachable device.
  • Disable SNMPv1 and v2c in favor of SNMPv3, which adds real per-user authentication and, optionally, payload encryption, closing the plaintext-shared-secret gap the advisories above describe. AA23-108 advises: “Do not use SNMP if you are not required to configure or manage devices remotely.”
  • Use SNMPv3 at authPriv, and limit what each user can read with SNMP views, as TA17-156A recommends.
  • Restrict port 161 to a management VLAN or specific trusted management IPs with a firewall rule, rather than leaving it reachable from any network the device happens to sit on. On Net-SNMP, the agentaddress setting binds the agent to a chosen address instead of every interface.
  • Disable SNMP entirely on devices that don’t actually need remote monitoring, and patch network devices for SNMP advisories.

BACnet on building networks has the same root problem, a protocol that trusts whoever can reach it; see is port 47808 (BACnet/IP) exposed. For another directory-style service that should stay internal, see is port 389 (LDAP) exposed.

Which devices may you test?

Every check this page links to is for assets you own or are explicitly authorized to test. Never scan, probe, or attempt to connect to a network or device you don’t control — AdminKit’s active checks only ever run against the IP making the request or an asset you’ve verified ownership of. See our Disclaimer and Acceptable Use Policy for the full terms.

This guide is general information, not a security audit of your specific network — see our disclaimer for what AdminKit's guidance does and does not commit to.

Frequently asked questions

Does AdminKit's port-check tool scan port 161?

No. The tool checks a fixed list of nine specific TCP ports (23, 554, 1883, 8883, 502, 7547, 80, 443, 8080) chosen for how often they turn up misconfigured on home and small-office devices — see the port-check tool page for the current list. 161 isn't on that list, and SNMP itself runs over UDP rather than TCP, so confirm your own exposure with the manual check below.

Why does SNMP use a community string instead of a username and password?

SNMPv1 and v2c, the versions still most widely deployed, were designed in an era when network management traffic was assumed to stay on a trusted internal segment. The community string acts as a shared secret rather than a per-user credential, and on v1/v2c it travels unencrypted, so anyone who can observe the traffic — or simply guess the near-universal default — can read it.

Is this still actively exploited, or just a theoretical risk?

Actively exploited. A joint CISA, NSA, FBI and UK NCSC advisory detailed how the Russian state-linked group APT28 used weak and default SNMP community strings, including "public," to access Cisco routers and carry out reconnaissance, and a later CISA advisory describes Russian FSB-linked actors scanning the internet specifically for devices that still accept default or common community strings.

Doesn't upgrading to SNMPv3 fix this automatically?

SNMPv3 adds real per-user authentication and optional payload encryption, which fixes the plaintext-shared-secret problem — but only if it's actually configured and enabled. A device running SNMPv3-capable firmware with v1/v2c still turned on for compatibility is just as exposed as one that never supported v3 at all.

What's the fastest fix if I find my own device's port 161 open?

Change any default community string immediately, disable SNMPv1/v2c in favor of SNMPv3 with real authentication if your device supports it, and restrict access to port 161 with a firewall rule or management VLAN so it's never reachable from the public internet at all.

Is a read-only community string harmless?

No. Besides leaking the device's configuration details, some SNMP vulnerabilities need only the read-only string to exploit. NVD's entry for CVE-2017-6742, the Cisco flaw APT28 used, says the attacker must know the SNMP read-only community string for v2c or earlier, and the flaw can lead to arbitrary code execution.

Want AdminKit to watch this for you?

Free checks tell you the state today. Protective DNS and monitoring tell you when it changes.

Huy Nguyen (David), Founder and CEO of Netbase JSC

Talk to an expert

Huy Nguyen (David), Founder & CEO, Netbase JSC

Ask whether this fix applies to your setup, or get a second pair of eyes on your DNS and mail records.