Issue with veeamservice PID being world writable

[daniel.welsh]

On our system, after running SCAP scans, V-38643 got flagged. After remediation, and changing permissions, the veeamservice PID is the only file on our system that reverts back to world writable. Is there a way to fix this?

[Gostev]

Can you clarify what specific service are you talking about?

[anish.varghese]

Hi, we're running Veeam-6.2.0.101 and we're seeing the same behaviour. The issue is that the pid file /run/veeamservice.pid is created with permissions 666 each time the service is started up. The other pid files such as veeamtransport.pid, veeamdeployment.pid etc have 644 permissions and so look ok. We're seeing the same behaviour on a Rocky 9 and an Ubuntu client.

[Gostev]

5 years later I'm still confused what service or even product are you talking about guys (6.2.0.101 does not sound like a Veeam Backup & Replication version or anything around object storage).

[rovshan.pashayev]

Hi All,

If I understood correctly, we are talking about Veeam Agent for Linux 6.2 (build 6.2.0.101), and issue with /run/veeamservice.pid file's permission will be fixed in a future release.

[anish.varghese]

Hi Rovshan,
That's right. Apologies that I didn't make this clear before. I was referring to "Veeam Agent for Linux". Thanks for confirming that this will be fixed in a future release.