Description
Nagios Core before 4.3.3 creates a nagios.lock PID file after dropping privileges to a non-root account, which might allow local users to kill arbitrary processes by leveraging access to this non-root account for nagios.lock modification before a root script executes a "kill `cat /pathname/nagios.lock`" command.
Fixed in Linux distributions
Distributions backport fixes, so the version that fixes this vulnerability differs per release — upgrade to at least the version shown. From the distributions' security trackers and advisories.
Ubuntu
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| Ubuntu 18.04 LTS | nagios3 | No fix yet | — |
| Ubuntu 16.04 LTS | nagios3 | No fix yet | — |
openSUSE
Security tracker ↗| Release | Package | Fixed in | Advisory |
|---|---|---|---|
| openSUSE Tumbleweed | nagios | 4.4.6-2.5 | openSUSE-SU-2024:11073-1 |
Advisories 1
- openSUSE-SU-2024:11073-1 nagios-4.4.6-2.5 on GA media SUSE / openSUSE Security Updates · May 7, 2025
References
- GLSA-201710-20 vendor-advisory
- https://github.com/NagiosEnterprises/nagioscore/commit/3baffa78bafebbbdf9f448890ba5a952ea2d73cb
- https://github.com/NagiosEnterprises/nagioscore/commit/1b197346d490df2e2d3b1dcce5ac6134ad0c8752
- https://github.com/NagiosEnterprises/nagioscore/blob/master/Changelog
- 100403 vdb-entry
- https://github.com/NagiosEnterprises/nagioscore/issues/404