>why would you make this information available at all? Why not? I know "why make it available at all?" is the proper question from a security standpoint. I'm just wondering what it opens you up to.
Suppose a vendor has a bug in their software that creates a read-only
community string with no access list protecting it. How much of an issue
would that be and why?
Regards,
Lee
|---------+-------------------------------------->
| | peter moody |
| | <[EMAIL PROTECTED]> |
| | Sent by: |
| | [EMAIL PROTECTED]|
| | .netsys.com |
| | |
| | |
| | 06/04/03 03:10 PM |
| | |
|---------+-------------------------------------->
>------------------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc: [EMAIL PROTECTED]
|
| Subject: Re: [Full-Disclosure] SNMP read-only opens up... what?
|
>------------------------------------------------------------------------------------------------------------------------------|
you could get the product type, version information etc from certain
mibs. you could tell how busy the site is, and from that infer how big
a pipe you've got.
There's a lot more. I would snmp-walk the device and find out what it
tells you.
but I've got to ask, why would you make this information available at
all?
On Wed, 2003-06-04 at 10:44, [EMAIL PROTECTED] wrote:
> Say I configure a router with a read-only SNMP community of "public" and
> make it Internet accessible. What vulnerabilities or information
> disclosure does that open up that would be better left closed? A switch?
>
> Thanks,
> Lee
--
Peter Moody <[EMAIL PROTECTED]>
InfoSec Administrator 831/459.5409
Communications and Technology Services. http://mustard.ucsc.edu/pubkey
UC, Santa Cruz.
:wq
(See attached file: signature.asc)
signature.asc
Description: Binary data
