Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

snmpd.conf proc with name containing spaces ignores values for Max and Min #10

Closed
michelhandleitnl opened this issue Sep 17, 2019 · 4 comments
Closed

snmpd.conf proc with name containing spaces ignores values for Max and Min #10

michelhandleitnl opened this issue Sep 17, 2019 · 4 comments

Comments

@michelhandleitnl
Copy link

snmpd.conf proc with name containing spaces ignores values for Max and Min
e.q.

proc "Plex Media Serv" 1 1

triggers an snmp trap with too many "Plex Media Serv" processes. Processes which don't contain a whitespace are not affected
@michelhandleitnl
Copy link
Author

proc "Plex Media Serv" 1 1 in snmpd.conf, this is the trap that is send --> Process should not be running
V2 Trap received: Enterprise value: DISMAN-EVENT-MIB::mteTriggerFired ¶
DISMAN-EVENT-MIB::mteHotTrigger value: process table ¶
DISMAN-EVENT-MIB::mteHotOID value: UCD-SNMP-MIB::prErrorFlag.3 ¶
DISMAN-EVENT-MIB::mteHotValue value: 1 ¶
(Description:The value of the object at mteTriggerValueID when a trigger fired.)
UCD-SNMP-MIB::prNames.3 value: Plex Tuner Serv ¶
UCD-SNMP-MIB::prErrMessage.3 value: Plex Tuner Serv process should not be running. ¶

@bvanassche
Copy link
Contributor

Which Net-SNMP version are you using?

@michelhandleitnl
Copy link
Author

5.7.3

@bvanassche
Copy link
Contributor

The v5.7 branch is no longer supported. A candidate fix has been checked in on the v5.8 and master branches. Please retest.

@AmitSharma1094 AmitSharma1094 mentioned this issue Sep 21, 2019
Closed
@AmitSharma1094 AmitSharma1094 mentioned this issue Sep 26, 2019
Closed
@Ymitrofanov Ymitrofanov mentioned this issue Feb 17, 2020
Open
@Umakumar01 Umakumar01 mentioned this issue May 3, 2020
Closed
@kulhar kulhar mentioned this issue May 12, 2020
Open
@Umakumar01 Umakumar01 mentioned this issue May 17, 2020
Closed
@Umakumar01 Umakumar01 mentioned this issue May 28, 2020
Open
@sureshbalakundi sureshbalakundi mentioned this issue Dec 15, 2020
Open
@suryatsoman suryatsoman mentioned this issue Mar 9, 2021
Closed
@krishnacx krishnacx mentioned this issue May 22, 2021
Open
@dj95035 dj95035 mentioned this issue Aug 31, 2021
Closed
@SHAIK178 SHAIK178 mentioned this issue Jan 31, 2022
Open
@vikneels vikneels mentioned this issue May 31, 2022
Open
bvanassche added a commit that referenced this issue Apr 16, 2023
@bvanassche
libsnmp: Fix a buffer overflow in the MIB parsing code
1d73893 
Fix the following address sanitizer complaint:

ERROR: AddressSanitizer: stack-buffer-overflow on address 0x7f4e612001a0 at pc 0x7f4e63c0a654 bp 0x7ffc98f7bb80 sp 0x7ffc98f7bb78
WRITE of size 1 at 0x7f4e612001a0 thread T0
    #0 0x7f4e63c0a653 in get_token snmplib/parse.c:4835:13
    #1 0x7f4e63c0a4a2 in get_token snmplib/parse.c:4813:20
    #2 0x7f4e63c0a4a2 in get_token snmplib/parse.c:4813:20
    #3 0x7f4e63c0a4a2 in get_token snmplib/parse.c:4813:20
    #4 0x7f4e63c0a4a2 in get_token snmplib/parse.c:4813:20
    #5 0x7f4e63c0a4a2 in get_token snmplib/parse.c:4813:20
    #6 0x7f4e63c0a4a2 in get_token snmplib/parse.c:4813:20
    #7 0x7f4e63c2dbd2 in parse_ranges snmplib/parse.c:2282:20
    #8 0x7f4e63c29ffa in parse_asntype snmplib/parse.c:2462:27
    #9 0x7f4e63c1789f in parse snmplib/parse.c:4598:19
    #10 0x7f4e63c0497b in read_module_internal snmplib/parse.c:3942:18
    #11 0x7f4e63c0407b in netsnmp_read_module snmplib/parse.c:4041:14
    #12 0x7f4e63c0d5e1 in read_mib snmplib/parse.c:5044:12
    #13 0x55ec21ab37b1 in main testing/fulltests/unit-tests/T027read_mib_clib.c:35:1

Fixes: 34058af ("*/*: replace horrible (char *)"string" with const specifiers in relevant 	functions.")
@SunFuchun SunFuchun mentioned this issue Apr 19, 2023
Open
@micron10 micron10 mentioned this issue Jan 29, 2024
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bvanassche @michelhandleitnl