Uploaded image for project: 'Observium'
  1. Observium
  2. OBS-3963

Log4j vulnerability

Details

    • Help
    • Resolution: Not A Bug
    • Critical
    • None
    • Professional Edition
    • Security
    • None

    Description

      Hi, 

       

      Is Observium affected by the log4j vulnerability?

      Attachments

        Activity

          [OBS-3963] Log4j vulnerability
          landy Mike Stupalov added a comment -

          Please stop spamming here with not related for Observium questions.

          We have already replied to you in the Discord channel.

          Observium is PHP application (with parts in python).
          We not use Java and any applications written on it.

          landy Mike Stupalov added a comment - Please stop spamming here with not related for Observium questions . We have already replied to you in the Discord channel. Observium is PHP application (with parts in python). We not use Java and any applications written on it.
          bot Observium Bot added a comment -

          General questions and device support can be discussed in our Discord channel, click here to join.

          Please make and attach additional information about the device:

          • full snmp dump from device: 

            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk
            		 
            snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk

            If device not support SNMP version 2c, replace -v2c with -v1.

          • If you have problems with discovery or poller processes, please do and attach these debugs: 

            ./discovery.php -d -h <device>
            		 
            ./poller.php -d -h <device>

          • additionally attach device and/or vendor specific MIB files

          This comment is added automatically.

          bot Observium Bot added a comment - General questions and device support can be discussed in our Discord channel, click here to join . Please make and attach additional information about the device: full snmp dump from device: snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1 > myagent.snmpwalk snmpwalk -v2c -c <community> -t 3 -Cc --hexOutputLength=0 -ObentxU <hostname> .1.3.6.1.4.1 >> myagent.snmpwalk If device not support SNMP version 2c, replace -v2c with -v1. If you have problems with discovery or poller processes, please do and attach these debugs: ./discovery.php -d -h <device> ./poller.php -d -h <device> additionally attach device and/or vendor specific MIB files This comment is added automatically.

          People

            landy Mike Stupalov
            Nirmolak Nirmolak Singh
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: