IntroductionPeople consider Linux the most secure operating system, as it is open-source. Even with all its might, vulnerabilities creep in the shadow, ready to strike. In this blog, we'll be taking a look at an infamous heap overflow vulnerability discovered in 2022. The growth of the Kubernetes and containers increased
Authors choice of title - Protect from CVE-2022-0185 - I say it is a permanent fix, so my title is more accurate. The CVE itself is part of Linux Kernel to some kernels and therefore the title is correct.
Does it fix anything for Linux users who don’t use kubernetes? The vast majority don’t. The obvious way everyone should fix CVE-2022-0185 today is by upgrading their kernel. If your distro hasn’t shipped an update with the fix yet, you should find a new distro.
I was hoping that this link would tell me about the process of writing the Linux kernel patch (which I of course upgraded to already) which fixed the bug.
Instead I found an advertisement for a kubernetes-related product. I have no idea if “AccuKnox” is any good, but I do know that at this point in time nobody should be “fixing” CVE-2022-0185 by installing it - the correct fix is to upgrade Linux.
Perhaps this product is a good idea for kubernetes users to mitigate the next unprivileged user namespace related vulnerability; I stopped reading when I realized it was all about kubernetes.
Another good mitigation for Linux users in general is to simply disable unprivileged user namespaces altogether :)
You can apply the method to other solutions too, it is mentioned at the bottom. Other product work similar, they usually apply a template.
What you hope and what it says can differ.
I doubt you even read it because you answered after 2-3 minutes of posting this guidance.
It is not an advertisement for Kubernetes. It is an example how to deal with the CVE using AccuKnox. If you want to complain about something then maybe that the Templates that they offer do not work on every Kernel, configuration, cluster etc.
The example is a fix to avoid getting compromised for that specific CVE. Whenever you like it or not it is a fix.
CVE-2022-0185, was discovered and patched before malicious attackers released an exploit publically. If this would be a guidance for home users I would have written something like - the Linux Kernel got an update to address CVE-2022-0185.
Authors choice of title - Protect from CVE-2022-0185 - I say it is a permanent fix, so my title is more accurate. The CVE itself is part of Linux Kernel to some kernels and therefore the title is correct.
Does it fix anything for Linux users who don’t use kubernetes? The vast majority don’t. The obvious way everyone should fix CVE-2022-0185 today is by upgrading their kernel. If your distro hasn’t shipped an update with the fix yet, you should find a new distro.
I was hoping that this link would tell me about the process of writing the Linux kernel patch (which I of course upgraded to already) which fixed the bug.
Instead I found an advertisement for a kubernetes-related product. I have no idea if “AccuKnox” is any good, but I do know that at this point in time nobody should be “fixing” CVE-2022-0185 by installing it - the correct fix is to upgrade Linux.
Perhaps this product is a good idea for kubernetes users to mitigate the next unprivileged user namespace related vulnerability; I stopped reading when I realized it was all about kubernetes.
Another good mitigation for Linux users in general is to simply disable unprivileged user namespaces altogether :)