New Linux glibc flaw lets attackers get root on major distros
New Linux glibc flaw lets attackers get root on major distros
www.bleepingcomputer.com
New Linux glibc flaw lets attackers get root on major distros
11 comments
-
-
they didnt explain how the exploit work or howto know if your system is vulnerable
-
Easiest answer:
sudo apt udpate sudo apt upgradeIf it upgrades some stuff, you were vulnerable, but you no longer are. If nothing upgrades, then you were already all good.
If you're doing that regularly, then your core system will generally be patched fixing almost all exploits in your core system, including this one. If not, you're vulnerable to this exploit and likely a whole bunch more stuff.
Edit: That's the simplest answer but if you're curious you can do a double-check for this particular vulnerability with
apt changelog libc6- generally speaking you won't see recent changes, but if a package has been recently updated you'll see a recent fix. So e.g. for this, I see the top change in the changelog is the fix from a couple weeks back:glibc (2.36-9+deb12u4) bookworm-security; urgency=medium * debian/patches/any/local-CVE-2023-6246.patch: Fix a heap buffer overflow in __vsyslog_internal (CVE-2023-6246). * debian/patches/any/local-CVE-2023-6779.patch: Fix an off-by-one heap buffer overflow in __vsyslog_internal (CVE-2023-6779). * debian/patches/any/local-CVE-2023-6780.patch: Fix an integer overflow in __vsyslog_internal (CVE-2023-6780). * debian/patches/any/local-qsort-memory-corruption.patch: Fix a memory corruption in qsort() when using nontransitive comparison functions. -- Aurelien Jarno Tue, 23 Jan 2024 21:57:06 +0100
-
11 comments
New? This has been fixed for a week or more.
It's a 5-day old article; Lemmy loves those on Sunday.
Lemmy (like its predecessors) is temporally arranged content. Think of it like having a discussion in a pub. Imagine bringing up a topic and someone said: but we discussed this 5 days ago, so we cannot discuss it now. Your obvious response would be: but I wasn't here five days ago. It's okay to repeat a conversation.
If you want more of a hierarchical structure, use wikipedia article conversations. Then each conversation only occurs once (ish). Not encouraging repeated conversation here will lead to slow content death -- like on StackOverflow.