Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | Re: [Snort-sigs] SNMP Missing Community String Signature FP |
|---|---|
| Date: | Mon, 10 Jul 2006 19:23:53 -0500 |
On 0, Eric Hines <eric.hines@appliedwatch.com> wrote:
Nigel, Packet pasted below starting from UDP Header. You are correct, as Jon pointed out, the 5 byte offset was starting from the UDP header instead of the Payload. But it still begs to ask as to why the rule is firing when the payload does in fact contain the public community string. Why search for |04 00| ? What would the |04 00| be indicative of if the payload does contain the community string? 0fdd 00a1 0033 d483 3029 0201 0004 0670 .......3..0).....p 7562 6c69 63a0 1c02 0400 a063 f602 0100 0201 ublic......c...... 0030 0e30 0c06 082b 0601 0201 0103 0005 00 .0.0...+.........
Well, the community string should be followed by an SNMP PDU which
contains the type of pdu, request-id, some error stuff and other things.
In versions of NT 4 it was possible to use the public community string,
(or any known community, but public was default) to connect and access
functions. Up to a service pack release that fixed the issue, it was not
possible to make the community read only, it was always read/write and
thus, if accessible, it was possible to do whatever you wanted using
SNMP.
I think the "04 00" indicates the termination of data. There is a "a0 1c"
right after the "public" in this case, which IIRC means "get". So the
"termination" (for want of a better word) bytes seem to be in the ID
field in this case.
(I could be wrong about the get thing, but right after the request type
should be a request-id)
+--------------------------------------------------------------------+
Nigel Houghton Research Engineer Sourcefire Inc.
Vulnerability Research Team
There is no theory of evolution, just a list
of creatures Vin Diesel allows to live.
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
Snort-sigs mailing list
Snort-sigs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/snort-sigs
| Previous by Date: | Re: [Snort-sigs] SNMP Missing Community String Signature FP, Eric Hines |
|---|---|
| Next by Date: | Re: [Snort-sigs] SNMP Missing Community String Signature FP, Nigel Houghton |
| Previous by Thread: | Re: [Snort-sigs] SNMP Missing Community String Signature FP, Nigel Houghton |
| Next by Thread: | Re: [Snort-sigs] SNMP Missing Community String Signature FP, Matthew Watchinski |
| Indexes: | [Date] [Thread] [Top] [All Lists] |