Onesixtyone

onesixtyone

Purpose

Use this skill for fast, bounded SNMP validation when the engagement needs to know whether approved devices expose SNMP with known or approved community strings.

Phase Fit

• Primary: Discovery and Reconnaissance, Vulnerability Analysis
• Secondary: Retest and Closure

Use When

• Need a quick view of SNMP exposure across approved devices.
• Need to validate whether a bounded community-string hypothesis is true.
• Need a retest path after SNMP hardening.

Avoid When

• Community-string testing is not explicitly approved.
• Range scope or rate limits are unclear.

Inputs

• Approved host range
• Narrow community-string list
• Rate and segmentation constraints

Procedure

1. Keep the community set tightly bounded.
2. Start with the smallest target range needed.
3. Hand confirmed SNMP responders to snmpwalk for focused follow-up.
4. Record the exact range and candidate set used.
5. Preserve the same bounded test for retest.

Command Syntax

Replace sample ranges and community files with approved in-scope values.

# Scan a single host with a community strings file
onesixtyone -c /usr/share/seclists/Discovery/SNMP/common-snmp-community-strings.txt 10.10.10.100

# Scan a subnet
onesixtyone -c communities.txt 10.10.10.0/24

# Scan from a hosts file with community strings file
onesixtyone -c communities.txt -i contoso-hosts.txt

# Adjust timeout (milliseconds)
onesixtyone -t 200 10.10.10.0/24 public

# Save output to file
onesixtyone -c communities.txt 10.10.10.0/24 > contoso-snmp.txt

Evidence to Capture

• Hosts that accepted the approved community set
• Exact range and candidate set used
• Minimal proof needed for remediation

Safety Boundaries

• Use only approved community candidates and ranges.
• Keep the candidate set narrow and rate aware.