Skip to content
StrikeOps

SNMP Default Community Strings

MediumTypical severity Network and infrastructureCWE-1392

01Description

Devices were found responding to SNMP requests using default or easily guessed community strings such as 'public' or 'private'.

02Impact

SNMP read access discloses detailed information including interfaces, routing tables, running processes, installed software and sometimes usernames, which assists further attacks. Read-write access can allow an attacker to change device configuration or retrieve full configuration files containing credentials.

03Severity

Typically

Medium

Typically Medium. Medium for read-only access, which leaks configuration detail. High if a read-write community string is accepted, as that allows device reconfiguration.

04How to verify

  1. 1Identify hosts listening on UDP 161.
  2. 2Test common community strings with a tool such as onesixtyone or snmpwalk.
  3. 3Record whether each accepted string grants read-only or read-write access.

Testing note: only test systems you are authorized to test, within the agreed scope and rules of engagement. Verification steps are written for professional testers and avoid destructive techniques.

05Remediation

  1. 1Disable SNMP where it is not needed.
  2. 2Migrate to SNMPv3 with authentication and encryption (authPriv).
  3. 3If SNMPv1/v2c must remain, use long random community strings and restrict access by source IP to monitoring servers only.
  4. 4Never enable read-write communities unless strictly required.

06References

Draft findings like this from your own evidence

Book a demo
Book a demo