this post was submitted on 08 Aug 2023
15 points (89.5% liked)
Linux
47955 readers
1153 users here now
From Wikipedia, the free encyclopedia
Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).
Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.
Rules
- Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
- No misinformation
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon by Alpár-Etele Méder, licensed under CC BY 3.0
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Here's my question, if anyone reading this post knows the answer: the simple version is... is it safe to enable the rhel-7-server-rhceph-4-tools-rpms repository?
To give a little more detail: old versions of modules that come from the Ceph package got flagged by our security scan. It appears that Ceph is installed by default on RHEL 7, but the repository above which I believe will update these modules, is not enabled by default. This seems odd to me, and the documentation for Ceph mentions that the EPEL repository should be disabled. It doesn't appear that this repository is enabled, but this still made me concerned about why the Ceph repository isn't enabled by default, hence my question.
Edit: I will try to contact Red Hat support to confirm the best course of action, like some have suggested on this thread. Thank you everyone for your help.
Edit 2: I figured out a course of action to take. The vulnerabilities were flagged for the librados2 and librbd1 packages. I used the command "rpm -q --whatrequires " to navigate the dependencies of these two packages to end at libvirt. Using the same command with libvirt, I was able to determine that no other package is dependent on it. Thus, it appears to me that I can address the issue by uninstalling all 3 packages. This seems safer and more secure than addressing the issue by enabling a new repository on the server. To be safe, I will take a snapshot of the VM before making the changes. I'll post another update afterward.
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.
Many security scanners are stupid about this.
Since it is rhel, you have a support contract, right? What do they say?
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?
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.
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.
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.