On 6/22/25 11:44 AM, JustCoding247 wrote:
I am writing to inquire about the proper procedure for reporting a
potential security vulnerability I have discovered in Net-SNMP.
While analyzing the Net-SNMP source code, I have identified what appears
to be a buffer overflow vulnerability in the
Dear Net-SNMP Developers,
I hope this email finds you well.
I am writing to inquire about the proper procedure for reporting a
potential security vulnerability I have discovered in Net-SNMP.
While analyzing the Net-SNMP source code, I have identified what appears to
be a buffer overflow
SM> How many devices are monitored?
Thousands.
SM> Generally this kind of behavior observed in our network monitoring tool,
SM> because of devices are having same engine ID.
We know with 100% certainty that there are no *current* devices with
the same engine ID. I am not asking for how to troub
: [email protected] [mailto:[email protected]]
Sent: Thursday, June 23, 2011 1:01 PM
To: [email protected]
Subject: Agent Reporting usmStatsNotInTimeWindows
Hi,
We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
Our manager was working
On Thu, 28 Jul 2011 15:30:03 -0400 Doug wrote:
DM> WH> The SNMPv3 specifications say that a running manager should allow its
DM> WH> notion of an agents clock values to go forward, but not backward. Thus,
DM> WH> we're doing what we're supposed to do: we won't accept *older* values
DM> WH> than wh
WH> The SNMPv3 specifications say that a running manager should allow its
WH> notion of an agents clock values to go forward, but not backward. Thus,
WH> we're doing what we're supposed to do: we won't accept *older* values
WH> than what we have cached (but would accept newer values). So, we're
W
> On Thu, 23 Jun 2011 05:26:04 -0400, said:
> We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
5.2.6 is rather old at this point, you might consider upgrading to a
newer release.
> Our manager was working fine for some time without any issues. after
> some days t
Hi,
We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
Our manager was working fine for some time without any issues. after some days
the agent starts giving report " usmStatsNotInTimeWindows" to all GETNEXT
queries. we noticed that the enginetime supplied by manager
Hi,
We are using net-snmp5.2.6 library to communicate with switches SNMP agent.
Our manager was working fine for some time without any issues. after some days
the agent starts giving report " usmStatsNotInTimeWindows" to all GETNEXT
queries. we noticed that the enginetime supplied by manager
hrStorageUsed (1.3.6.1.2.1.25.2.3.1.6)
> and hrStorageAllocationUnits (1.3.6.1.2.1.25.2.3.1.4) .
Eh?
This rather relies on the hrStorageTable *only* reporting memory usage.
That is a somewhat dangerous (read broken/wrong) assumption.
This particular table is designed for reporting a range of storage type
, 2010 8:48 AM
To: '[email protected]'
Subject: Memory reporting issues
Hi. I am using a monitoring product, Orion, from Solar Winds. We have been
experiencing reporting issues for a few months now. Per Solar Winds, I moved
away from the default SUN Solaris snmp and ins
Hi. I am using a monitoring product, Orion, from Solar Winds. We have been
experiencing reporting issues for a few months now. Per Solar Winds, I moved
away from the default SUN Solaris snmp and installed net-snmp. I tried to
compile 5.5, 5.4.3 and 5.3.3 on several servers and failed every time
Thomas Anders wrote:
> Chris Black wrote:
>
>> Thomas Anders wrote:
>>
>>> Chris Black wrote:
>>>
I am compiling net-snmp on OpenBSD-4.0 on an amd64 arch (running in
64-bit mode) from ports with the openbsd MIBs patch
(http://www.packetmischief.ca/openbsd/snmp/) applie
Chris Black wrote:
> Thomas Anders wrote:
>> Chris Black wrote:
>>> I am compiling net-snmp on OpenBSD-4.0 on an amd64 arch (running in
>>> 64-bit mode) from ports with the openbsd MIBs patch
>>> (http://www.packetmischief.ca/openbsd/snmp/) applied. During autoconf I
>>> got the following warning t
Thomas Anders wrote:
> Chris Black wrote:
>
>> I am compiling net-snmp on OpenBSD-4.0 on an amd64 arch (running in
>> 64-bit mode) from ports with the openbsd MIBs patch
>> (http://www.packetmischief.ca/openbsd/snmp/) applied. During autoconf I
>> got the following warning that seemed to indicat
Chris Black wrote:
> I am compiling net-snmp on OpenBSD-4.0 on an amd64 arch (running in
> 64-bit mode) from ports with the openbsd MIBs patch
> (http://www.packetmischief.ca/openbsd/snmp/) applied. During autoconf I
> got the following warning that seemed to indicate I should notify this
> list, s
I am compiling net-snmp on OpenBSD-4.0 on an amd64 arch (running in
64-bit mode) from ports with the openbsd MIBs patch
(http://www.packetmischief.ca/openbsd/snmp/) applied. During autoconf I
got the following warning that seemed to indicate I should notify this
list, so I am doing so. I am not loo
Alexander Czigler wrote:
> uname: FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7 04:32:43
> UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GENERIC i386
>
> checking sys/conf.h presence... yes
> configure: WARNING: sys/conf.h: present but cannot be compiled
Whci hnet-snmp version? Sh
Just picked this up in the terminal..
uname: FreeBSD 6.1-RELEASE FreeBSD 6.1-RELEASE #0: Sun May 7
04:32:43 UTC 2006 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/
GENERIC i386
checking sys/conf.h presence... yes
configure: WARNING: sys/conf.h: present but cannot be compiled
configure: WARNIN
>>>>> On Mon, 20 Mar 2006 16:00:05 -0700, "Kane Estess" <[EMAIL PROTECTED]>
>>>>> said:
Kane> Don't know exactly what this means, but the directions were
Kane> clear, so here it is... Compiled on a late version of Cygwin on
Kane> XP
Don't know exactly what this means, but the directions were clear, so
here it is...
Compiled on a late version of Cygwin on XP Pro.
Anything else I should do?
checking winsock.h presence... yes
configure: WARNING: winsock.h: present but cannot be compiled
configure: WARNING: winsock.h: check f
I'm sending this to the
coders list because of the configure output request but I tried the suggestions
of Thomas Anders when I contacted the users list.
I'm running on IRIX6.5.
I've tried using a
recent tarball (net-snmp-cvs-V5-3-patches_20060306_0306.tar.gz) and untarred it
using the gnu
22 matches
Mail list logo
