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:
Removed input in Elastic Agent Fleet System integration With the release of Elastic Agent Fleet version 2.0.0, the "System" integration has been updated and now removes support for a deprecated log collection input method that relied on httpjson. This input Read More
Important: Grafana security update Type/Severity NetEye Product Security has rated this update as having a security impact of High Topic An update for the package grafana is now available for NetEye 4. Security Fix for NetEye 4.41 11.6.1_neteye3.27.1-1 For details on how Read More
Fix rpmnew handling in Keycloak upgrade procedure We fixed an issue in Keycloak's update procedure to improve the handling of an rpnew generated during the update. First installation for SIEM clusters without voting-only node We fixed an issue related with Read More
Fix Tornado filter WHERE condition We fixed an issue in Tornado UI in which the WHERE condition of a filter were not being displayed correctly for some conditions not created through the API. List of updated packages To solve the Read More
Fix Tornado filter WHERE condition We fixed an issue in Tornado UI that did not allow deleting the WHERE condition of a filter in some conditions. List of updated packages To solve the issue, the following packages have been updated Read More