North American Network Operators Group|
Date Prev | Date Next |
Date Index |
Thread Index |
Author Index |
RE: Warning: Cisco RW community backdoor.
- From: Chris Hallman
- Date: Tue Feb 27 01:36:28 2001
Yes, the info is due to be made public today. We have been making personal
calls to numerous ISPs as early of 2/20.
NSE NSP North Florida
3660 Maguire Blvd., Suite 200
Orlando, Fl. 32803
407-903-7591 off-site office
From: email@example.com [mailto:firstname.lastname@example.org]On Behalf Of
Sent: Monday, February 26, 2001 11:07 PM
To: Sean Donelan
Subject: Re: Warning: Cisco RW community backdoor.
On 26 Feb 2001, Sean Donelan wrote:
> It appears more than one vendor shared the same SNMP library (or
> SNMP programmer). Folks have sent me evidence at least two other
> vendor's equipment has similar responses to the same SNMP community
> string ILMI.
> However, there are other non-related SNMP issues. Many SNMP
> implementations included the default community strings "public"
> and "private". If the operator doesn't change them, the defaults
> may still work. The other common SNMP implementation issue is if
> no community string is specified, the SNMP agent accepts any
> community string.
> If you are checking your network, I'd suggest checking for all
> three possibilities.
IMHO, if no communities are supplied, the SNMP daemon should not respond
While I agree that "public" and "private" are "wellknowns," in most
implementations, they at least show up in the code. Cisco chose to hide
this one where it would not show up in the code. That IMHO is a very bad
thing and does bad things to my confidence level in Cisco.