Bug discovered on NetEye module logmanagement and SIEM
A bug has been discovered on NetEye modules logmanagement and SIEM. If affected, rsyslog directories on system might be created with wrong permissions causing Logstash to be unable to load log lines of some hosts inside Elasticsearch. Users might also receive an error message trying to check signatures for some hosts inside Logmanager Log Check. All NetEye systems with neteye-logmanagement or netey-siem modules installed might be affected .
To check your system run following command:
find /neteye/shared/rsyslog/data/ -not -perm 770 -type d -exec ls -lad {} \; | grep "dr-------T."
If the provided command returns some results your system is affected. Please apply the following workaround to fix it until an official bug-fix is provided:
Run command: crontab –e
Add following line: 30 00 * * * /usr/bin/find /neteye/shared/rsyslog/data/ -not -perm 770 -a -not -perm 750 -type d -exec /usr/bin/chmod 770 {} \; > /dev/null
Save the file
Previous steps must be executed on every NetEye node.
If
you need further information, or experience some problem applying the fix, feel
free to contact our support team using one of the following options:
Scenario GLPI is integrated into NetEye and provides powerful asset management solutions. Usually GLPI agents are deployed on servers and clients: this way an up-to-date asset inventory is kept within NetEye. The GLPI package also provides a tool able to Read More
We fixed a bug that caused the neteye install command to not wait for resources to restart after the procedure completed. We updated the following packages: neteye-setup and neteye-setup-configurator to version 1.127.4-1
We released an update for GLPI that fixes several vulnerabilities. We updated the following packages: glpi, glpi-autosetup and glpi-neteye-config to version 10.0.16_neteye1.15.3-2
In order to be able to carry out detailed network monitoring, an IT administrator naturally wants to know what is happening in his or her network. To obtain this information, the network flows must of course be analyzed. Many network Read More
We fixed a bug in Icingaweb2 module Tornado UI which prevented the UI from refreshing after a draft configuration was deleted. We updated the following packages: icingaweb2-module-tornado, icingaweb2-module-tornado-autosetup and icingaweb2-module-tornado-configurator to version 2.13.6-1