Nmap Security Scanner
*Intro
*Ref Guide
*Install Guide
*Download
*Changelog
*Book
*Docs
Security Lists
*Nmap Hackers
*Nmap Dev
*Bugtraq
*Full Disclosure
*Pen Test
*Basics
*More
Security Tools
*Pass crackers
*Sniffers
*Vuln Scanners
*Web scanners
*Wireless
*Exploitation
*Packet crafters
*More
Site News
Site Search:
Exploit World
Advertising
About/Contact
Credits
Sponsors:
edgeos



Bugtraq: Netcache snmp behaviour

Netcache snmp behaviour

From: Marco Davids <mdavids_at_CASEMA.NET>
Date: Wed, 7 Apr 1999 08:43:40 +0200

Hi,

We noticed an unexpected behaviour on our NetApps C630
Netcache's. The problem even seems to exist in the latest software-
release 3.3.1.

The problem concerns the SNMP default community-name setting,
which is set to 'public'.

When changed into something else, using the webinterface, one
might think that de default community-name is disabled. However,
this is not the case. The new community-names are simply added
to the existing default one. In other words; using the webinterface
to enter extra community-names will _not_ disable the default.

SNMP-Information can thereby still be retreived form the 'toaster'.
This enables easy access to information you might not want to
reveal.

The only thing I could come up with to avoid this problem is to
manually telnet into the Netcache, and issue the command: 'snmp
delete ro community public' after every reboot.
(this can only be done in the 'extended' command-mode)

One could also edit /etc/rc and include this command, but please
note that after every change through the web-interface this /etc/rc
file is overwritten.

Off course it is probably wise, although not allways an option, to
restrict snmp-access at all, for instance by using router-
accesslists.

Cheers.

Marco Davids +31(0)15 8881000 fax +31(0)15 8881099
N.V. Casema -- Internet NOC mailto:mdavids_at_casema.net
Systemadministrator http://www.casema.net/~mdavids
Received on Apr 07 1999

[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]
edgeos