CPSA ยท Network device management and Layer 2/3 protocols
SNMP weaknesses
Community strings, v1/v2c vs v3, information enumeration and common attacks on Cisco configurations.
Key points
- SNMP (UDP 161 queries, 162 traps): reads and sets values in a device MIB.
- v1 and 2c: clear-text community string only, often defaults public (read-only) and private (read-write).
- Read community: interfaces, routes, ARP entries, software, sometimes config; write community changes settings.
- SNMPv3: users, authentication, encryption (authNoPriv integrity only, authPriv also encrypts).
- Use ACLs, prefer v3, avoid read-write.
Practice questions
How do SNMPv1 and v2c authenticate a request?
- A per-user certificate
- A community string sent in clear text
- A Kerberos ticket
- An encrypted pre-shared key
Show answer
Answer: B. A community string sent in clear text
They rely on a community string carried in clear text. Per-user keys and encryption arrive only with SNMPv3.
Which weaknesses affect SNMPv1 and v2c deployments?
- Community strings can be sniffed
- Default strings such as public and private are widely tried
- Messages are encrypted per user
- Agents can be queried only from the local console
- Commands are authenticated with a digital certificate
Show answer
Answer: A. Community strings can be sniffed, B. Default strings such as public and private are widely tried
Clear-text community strings and guessable defaults are the issues. Per-user encryption belongs to v3, and UDP transport is not itself a vulnerability here.
A read-only community string cannot expose anything useful to an attacker.
Show answer
Answer: False
False. Read access can reveal interfaces, IP addresses, routes, ARP tables and software versions, which is valuable reconnaissance.
Practice 8 questions on this topic in Bitzu
Short lessons, instant explanations and spaced review of what you get wrong. Free on iOS and Android.
