An update for httpd is now available for NetEye 4.17.
NetEye Product Security has rated this update as having a security impact of Important. A Common Vulnerability Scoring System (CVSS) base score, which gives a detailed severity rating.
Description
httpd is the Apache HyperText Transfer Protocol (HTTP) server program used in the NetEye 4 Product to expose the web interface.
A lack of some headers useful to prevent cross-site request forgery and clickjacking attacks was found in the configuration. Attackers were able to induce users to perform actions that they do not intend to perform.
Security Fix(es) for NetEye 4.17:
httpd-neteye-config-1.9.1-1.noarch.rpm
httpd-neteye-config-autosetup-1.9.1-1.noarch.rpm
For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the links listed in the References section.
Solution
For details on how to apply this update, which includes the changes described in this advisory, refer to the NetEye Update Section inside the User Guide.
After installing the updated packages, the httpd daemon will be restarted automatically.
Affected Products
All NetEye 4.x versions prior to and including 4.17.
General Authentication via request-header backend We fixed a bug that did not allow the role to be associated with a user who was part of an LDAP group when the user logged in via the request-header backend. Tornado Tornado Director Read More
We fixed a bug that was preventing the upgrade from 4.29 to 4.30 and removed some concurrency issues occurring in cluster environments. Furthermore we fix a a bug where the neteye_secure_install would overwrite dashboard UIDs in some edge-cases. For NetEye Read More
We updated Icinga Web 2 to the latest bugfix version.All fixes can be found in the official documentation. We also fixed an issue where the modification of the neteye tenant configuration was possible when that would leave orphant generated configurations. Read More
We fixed a bug on the command orchestrator module that prevented the correct command to be displayed on the "Command Execution" tab. Now is possible to see the correct command name and associate correctly the execution tab to the selected Read More
We fixed a bug that was preventing the first secure install of a cluster to success. Now the ClickHouse autosetup, which contained the spotted bug, has been fixed and updated. Moreover we fixed two bugs related to Tenants having a Read More