Bug Fix for NetEye 4.49: Blocked GLPI Agent Inventories
When the GLPI inventory plugin is used to collect agent inventories, assets may fail to appear in GLPI even though the agents reach the server. The cause was a bug in the Icinga Web 2 SSO plugin: GLPI 11 marks the inventory plugin’s endpoints as “stateless,” and the SSO plugin wrongly treated them like static resources, skipping their authentication. Inventory submissions from the GLPI Agent were therefore blocked before they could be processed.
The fix makes the plugin recognize these endpoints and handle them correctly: agent inventories are again authenticated against Icinga Web 2 and ingested as expected, while the behavior of all other resources remains unchanged.
List of updated packages
The following packages have been updated for NetEye 4.49:
glpi-plugin-icingaweb2sso, glpi-plugin-icingaweb2sso-autosetup, and glpi-plugin-icingaweb2sso-configurator, all to version 1.20.3-1
Disclaimer: Three of the security issues referenced below do not yet have public CVE identifiers, so they are referenced by their GHSA ID. This post will be updated as soon as CVEs become available. Important: Icinga Web 2 security update Read More
Disclaimer: Some of the CVEs referenced below have not yet been publicly disclosed, so details regarding their severity, impact, and potential attack vectors are not fully available at this time. This post will be updated as soon as additional information Read More
Important: Elastic Stack security update Type/Severity NetEye Product Security has rated this update as having a High security impact. Topic Updates for the Elastic Stack packages are now available for NetEye 4. Security Fix for NetEye 4.50 9.5.6_neteye3.105.5-1 CVEs Elasticsearch Read More
Update: Elastic Stack v9.5.6 also includes important security fixes. You can find more details here. Update of Elastic Stack to Version 9.5.6 Elastic Stack 9.5.6 is a maintenance release that brings a large set of stability, correctness and hardening fixes Read More
Disclaimer: The security issues below do not yet have publicly disclosed CVE identifiers, so details regarding their severity, impact, and potential attack vectors are not fully available at this time. This post will be updated as soon as additional information Read More
