An update for the package lampod is now available for NetEye 4.
NetEye Product Security has rated this update as having a security impact of Important. Common Vulnerability Scoring System (CVSS) base scores provide additional guidance about a vulnerability and give a detailed severity rating.
Description
lampod is a NetEye package used for searching across the most important entities such as hosts, configurations etc.
An improper input validation causes Cross Site Scripting when the element is displayed in lampo navigation (CWE-79)
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
Update lampod to latest version (1.1.2-1).
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.
Affected Products
All NetEye 4.x versions prior to and including 4.30
Fix upgrade 4.45 migration error We solved an issue that affected the upgrade to NetEye 4.45. The issue occurred during the migration of the monitoring role permissions to Icinga DB, due to the order in which packages were updated. List Read More
Fix NetEye web UI exception We solved an issue that affected the NetEye web UI, when the SLM feature module is not installed, causing an exception to be thrown. List of updated packages To solve the issues mentioned above, the Read More
Fix for memory corruption in icinga2 We solved an issue that affected icinga2. If the cleanup of the http sessions in the execute-script endpoint ran during a request, the re-balance in the internal datastructure would corrupt the requests memory, resulting Read More
Fix El Proxy Kibana plugin activity We solved an issue that affected the El Proxy Kibana plugin which, in case many Fleet agent policies were associated with an integration, caused a large number of index template updates, possibly resulting in Read More
Fix support for Alyvix Nodes with older versions We solved an issue that could cause Test Cases to be not shown in the Alyvix UI if the Alyvix Nodes supported only API version 3 (i.e. Alyvix Service version <= 2.5). Read More