Insecure permissions nagios service #1028
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This patch changes the permissions of the systemd unit file for Nagios from 755 to 644. The system is vulnerable because there are systemd unit files with insecure permissions. Systemd unit file permission are considered insecure in the following situations:
Making these changes are due to security concerns for Nagios XI which uses Nagios Core. Switching 755 to 644 permissions removes the execution bits from all the groups thus making the systemd unit files secure.
https://www.baeldung.com/linux/systemd-unit-file-permissions
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/using_systemd_unit_files_to_customize_and_optimize_your_system/assembly_working-with-systemd-unit-files_working-with-systemd#proc_creating-custom-unit-files_assembly_working-with-systemd-unit-files