• 3 Posts
  • 29 Comments
Joined 1 year ago
cake
Cake day: June 27th, 2023

help-circle














  • Final update on this issue. I found out about the "rpm -q --whatrequires " command and used that to navigate the dependency chain for the modules in question. I was able to determine that those modules were ultimately not being used for anything. Once I confirmed that, I removed the modules. So far so good. It didn’t cause any issues to the services on that server. I will find out if it resolved the vulnerability that had been flagged by the security scanner next time it runs, probably at the end of the month.




  • I checked, and the versions of those modules that are currently installed are way behind what’s provided in the listed Red Hat patch, so it does seem that the updates for this just haven’t been installed. I will try to double-check with Red Hat support to be sure that enabling the Ceph repository is the correct course of action to take. Thank you once again for your help.




  • You might want to check the errata for the packages your scanning tools complained about. Rhel will keep stable versions at the same release version, but backport security fixes in.

    Thanks. I had verified that there is an errata before posting here. I presume that it hasn’t been installed due to that repository being disabled, but maybe I’m mistaken?

    Many security scanners are stupid about this.

    Indeed. In the process of researching this I found a related KB article from Red Hat that basically said that the security scanner is not supposed to flag this.

    Since it is rhel, you have a support contract, right? What do they say?

    I’m positive we have a support contract, but I’ve never had to use it, so I’m not familiar with the process. I’m not one of the main linux admins here. If I can’t find the answer either here or from my own research, I’ll look into the process to open a case.

    Thanks again.