Published on November 19, 2019

After announcing v1.1.5 with the new Switch Topology report, quite a few folks wrote in to ask if this feature was available in SNMPv3 environments. As of this evening, the answer is yes. To leverage SNMP v3 credentials in a Rumble scan, set the following options in the Advanced Options section of the Scan Configuration screen.

Rumble SNMP v3 Support

Depending on your environment, these settings may require some tweaking. The standard security levels of NoAuthNoPriv, AuthNoPriv, and AuthPriv map to these options as follows:

NoAuthNoPriv
  • snmp-v3-username set to a valid user
  • snmp-v3-auth-protocol set to “none”
  • snmp-v3-privacy-protocol set to “none”
AuthNoPriv
  • snmp-v3-username set to a valid user
  • snmp-v3-auth-protocol set to “md5” or “sha”
  • snmp-v3-passphrase set to the valid password for the user
  • snmp-v3-privacy-protocol set to “none”
AuthPriv
  • snmp-v3-username set to a valid user
  • snmp-v3-auth-protocol set to “md5” or “sha”
  • snmp-v3-passphrase set to the valid password for the user
  • snmp-v3-privacy-protocol set to “des” or “aes”
  • snmp-v3-privacy-passphrase set to the valid key (often hexadecimal)

The Rumble Scanner also supports SNMPv3 authentication using similar command-line options:

    --snmp-v3-auth-passphrase string      The authentication passphrase
    --snmp-v3-auth-protocol string        The authentication protocol (none, md5, sha) (default "none")
    --snmp-v3-privacy-passphrase string   The privacy passphrase
    --snmp-v3-privacy-protocol string     The privacy protocol (none, des, aes) (default "none")
    --snmp-v3-username string             The username to use for SNMP v3 authentication

These options require version 1.1.7 or newer of the Rumble Agent or Rumble Scanner.

This release also includes a number of small bug fixes for the SNMP probe and better support for CAM/MAC table enumeration of Cisco equipment.

Happy Scanning!

Similar Content

Security Surprises with SNMP v3
Published on January 3, 2020
Earlier this week, Gerry Gosselin and Eric Rioux of VertitechIT were investigating a strange result in the Rumble asset inventory; After scanning an external subnet with Rumble, they noticed that the main internet router was responding to SNMP probes on its normal address and HSRP address. The router in question had a strong SNMP v2 community as well an IP ACL on the SNMP service. Rumble still reported the router vendor, manufacturing date, and MAC address via SNMP, all unauthenticated and from the internet.
Scanning for HTTP/2 with Rumble
Published on August 15, 2019
This Tuesday, Jonathan Looney, a researcher at Netflix, disclosed seven different ways to break common HTTP/2 protocol implementations, while an eighth issue was disclosed by Piotr Sikora of Google. These issues could be used to exhaust the resources of affected HTTP/2 implementations. Shortly after the HTTP/2 issues were disclosed, a Rumble user reached out asking if we could help identify HTTP/2 endpoints on their network. We are happy to announce that as of version 0.
Hunting for Network Bridges with Rumble
Published on August 5, 2019
Thanks to the wonderful user feedback from Beta 5, a handful of bug fixes and improvements have been deployed along with a new feature: Network Bridge Detection! The bridge report shows external networks in red, internal networks in green, and multihomed assets that bridge these networks in orange. Zooming in will show asset and subnet details, while clicking a node will take you to the asset page for bridge nodes and to a CIDR-based inventory search for network nodes.