[PATCH 0/1] Patch for snmp_agent.c

2025-02-28 Thread Michael Schmidt via Net-snmp-coders
e value of the command-pointer at the start of the if-case and later reused to compare if the issued command was a set or get request. This prevents modifications of the command-pointer (snmp_agent.c, line 2017) impacting the proper incrementation of the statistic. Kind regards, Michael Schmid

Re: Memory leak in snmp_agent.c

2010-03-12 Thread lanas
Le Vendredi, 12 Mars 2010 17:38:37 -0800, Wes Hardaker a écrit : > You're right it's not. Generally there are a number of places in the > code (many many actually) where single-instance calls to memory > allocation are taken and never cleaned up like they should be at > shut-down time because we

Re: Memory leak in snmp_agent.c

2010-03-12 Thread Wes Hardaker
>>>>> On Sat, 6 Mar 2010 15:18:32 -0500, "Szudy Brett-CBS035" >>>>> said: SB> I have version 5.5 of netsnmp. I am looking at snmp_agent.c, function SB> init_master_agent and see a memory leak here. strdup mallocs and SB> duplicates the string

Memory leak in snmp_agent.c

2010-03-06 Thread Szudy Brett-CBS035
Hi all I have version 5.5 of netsnmp. I am looking at snmp_agent.c, function init_master_agent and see a memory leak here. strdup mallocs and duplicates the string into buf, but then buf is never released. It is a local which is also never stored or returned, so it is lost forever and not

snmp_agent.c

2009-10-27 Thread Karthikeyan N
Hello, I have a doubt regarding the below piece of code in snmp_agent.c file. I am using net-snmp5.0.9. if (access_ret == VACM_NOSUCHCONTEXT) { /* * rfc2573 section 3.2, step 5 says that we increment the * counter but don't return a response of any

RE: Possible memory corruption and double free in snmp_agent.c - netsnmp_wrap_up_request()

2009-10-04 Thread Gaash Hazan (gahazan)
snmp_agent.c - netsnmp_wrap_up_request() Gaash Hazan (gahazan) wrote: >Hi codes, > >I am new to net-snmp. Please understand if I do thing not in the right >way. > >I believe there is an issue at netsnmp_wrap_up_request)). An issue that >causes memory corruption and double free.

Re: Possible memory corruption and double free in snmp_agent.c - netsnmp_wrap_up_request()

2009-09-25 Thread Daniel Chuang
ct is created and processed. >3. netsnmp_wrap_up_request() at snmp_agent.c is called with an 'asp' >object. >4. The 'asp' object points to 'pdu' and 'requests' objects. Both 'pdu' >and 'requests' point to the *same* varbind objects. &g

Possible memory corruption and double free in snmp_agent.c - netsnmp_wrap_up_request()

2009-09-02 Thread Gaash Hazan (gahazan)
-a output is: Linux SCE8000 2.6.26.2 #32 SMP Sun Apr 26 15:55:49 IDT 2009 ppc GNU/Linux It goes like that: 1. SNMP get sys up time request is received and processed. 2. An 'asp' object is created and processed. 3. netsnmp_wrap_up_request() at snmp_agent.c is called with an 'asp&

Possible memory corruption and double free in snmp_agent.c - netsnmp_wrap_up_request()

2009-09-02 Thread Gaash Hazan (gahazan)
-a output is: Linux SCE8000 2.6.26.2 #32 SMP Sun Apr 26 15:55:49 IDT 2009 ppc GNU/Linux It goes like that: 1. SNMP get sys up time request is received and processed. 2. An 'asp' object is created and processed. 3. netsnmp_wrap_up_request() at snmp_agent.c is called with an 'asp&