We need to create and verify the fix for CVE-2017-16834.
Essentially, npcdmay have some security issues due to root permission usage (ie. its startup file which use root, and then immediately switches to the unprivileged user.
I believe this is a "reaching" issue, as this requires access to the local system (ie. rather than being remotely exploitable), as well as a few other assumptions (ie. users being part of the unprivileged user's group, or have the ability to access that account).
Proper installations should be with root-owned configurations, and lock the user to the unprivileged user. As a workaround, you can run npcd with its own user, only verifying that the webserver has read access to the proper RRD files.
We need to create and verify the fix for CVE-2017-16834.
Essentially,
npcd
may have some security issues due to root permission usage (ie. its startup file which use root, and then immediately switches to the unprivileged user.I believe this is a "reaching" issue, as this requires access to the local system (ie. rather than being remotely exploitable), as well as a few other assumptions (ie. users being part of the unprivileged user's group, or have the ability to access that account).
Proper installations should be with root-owned configurations, and lock the user to the unprivileged user. As a workaround, you can run
npcd
with its own user, only verifying that the webserver has read access to the proper RRD files.