Kibana Upgrades - Vulnerability

[hearnyj]

Hey there,

We've got another Nessus vuln picking up Kibana - https://discuss.elastic.co/t/kibana-8-18-8-8-19-4-9-0-7-9-1-4-security-update-esa-2025-16/382450

Is it a simple case of amending kibana.yml to mitigate this? I appreciate it isn't quite this simple, but will there be functionality to manually upgrade these versions in future? Often Nessus scans are pinged over to the team to remediate, and with LME I've had to wait for this to be bumped in later LME versions.

[aarz-snl]

Yes... ultimately this file: /opt/lme/config/kibana.yml

Is linked to the running instance of kibana. You can add whatever configurations to this as needed and do a sudo systemctl restart lme-kibana to implement. Create a backup of the file to be safe as you make changes

A lot of times nessus scans are overly aggressive and hit vulnerabilities that aren't really vulnerabilities. Because they're often basic checks like 'what version are you using' -- we do not use vega by default in our installation so disabling shouldn't cause any negative impact