[Pkg-net-snmp-devel] Bug#565635: Bug#565635: Crashes when queried

[Simon Richter]

severity 565635 important
thanks

Hi,

On Mon, Feb 01, 2010 at 06:22:34PM +0100, Jochen Friedrich wrote:

> >since the last upgrade, about any GETNEXT request makes snmpd crash,
> >first logging an assertion failure, then stumbling over what looks like
> >a null pointer dereference (address 0x20c).
> >
> >ii  libsnmp15                 5.4.2.1~dfsg-4 SNMP (Simple Network Management Pr

> Does this still happen with libsnmp15 5.4.2.1~dfsg-5?

Yes.

I've narrowed it down a bit hence the severity adjustment.

First of all, my example is not quite correct. While 1.3.6.1.2.1.4.34.1
does give me the first row, first column of the ipAddressTable,
1.3.6.1.2.1.4.34.2 does not refer to the second column; rather, I should
be using .1.3.6.1.2.1.4.34.1.1 and .1.3.6.1.2.1.4.34.1.2; snmpd does not
crash then (these columns appear to be entirely virtual, and snmpd
returns the first element of the third row for both; the results for
the first two rows can be deduced from the OID returned for the third
row however, so this is not a problem).

The issue of the crash still remains, however: asking for both
1.3.6.1.2.1.4.34.1 and 1.3.6.1.2.1.4.34.2 in the same request leads to a
crash, while individually, they are handled fine (the first returning
the third column, first row of ipAddressTable, the second returning
what is apparently fourth column, first row of ipNetToPhysicalTable).

So it is the combination of the requests that is problematic.

   Simon