Linux systemd affected by memory corruption vulnerabilities, no patches yet – slashdot

Major Linux distributions are vulnerable to three bugs in systemd, a Linux initialization system and service manager in widespread use, California-based security company Qualys said late yesterday. From a report: The bugs exist in ‘journald’ service, tasked with collecting and storing log data, and they can be exploited to obtain root privileges on the target machine or to leak information. No patches exist at the moment. Discovered by researchers at Qualys, the flaws are two memory corruption vulnerabilities (stack buffer overflow – CVE-2018-16864, and allocation of memory without limits – CVE-2018-16865) and one out-of-bounds error ( CVE-2018-16866).

They were able to obtain local root shell on both x86 and x64 machines by exploiting CVE-2018-16865 and CVE-2018-16866. The exploit worked faster on the x86 platform, achieving its purpose in ten minutes; on x64, though, the exploit took 70 minutes to complete. Qualys is planning on publishing the proof-of-concept exploit code in the near future, but they did provide details on how they were able to take advantage of the flaws.

Shitty windows-ini-style Unit files, binary logs, 12 different subsystems gobbled up and "integrated" … I mean did this kind of shit surprise someone? Really? After years of supporting Systemd and solving it’s problems for others I can say with limited authority that, yes, it really is garbage. I know there were a few people who thought systemd was just "progress", but no it’s a schism, a coup, a shitty revolution that left everyone worse than when they started. Linus and friends are too old and retarded now apparently to lose face and be critical of it because they stood by and shrugged while the Potterites and Fedora assholes ruined Linux. I mean BSD was always better, don’t get me wrong. So, it’s not as big a loss as some would frame it to be. However, it used to be fun, useful, and relatively untainted by anything this heinous but a few unenlightened windows folks came along and created this svchost.exe ripoff (systemd) for the purposes of enhancing GNOME and now you get this smelly mess that is now Linux. Ah well, it was (sorta) fun while it lasted. Back to my BSD boxes.

It really does just suck. It’s not haters, it’s not bias, it’s not politics. It’s also not only people resisting change, Systemd is just flat out technically inferior. Bad choices were made and the chickens definitely are coming home to roost. I get a *lot* of calls from frustrated/confused sysadmins who run into issue after issue with systemd. From subtle problems from malformed unit files to clear-as-mud dependency graph issues between units. Yes, they are fixable most of the time but systemd just throws obstacle after obstacle into your path. Want to know why something didn’t work? Well, there’s journald hording your logs as binary. Hope you have the magic decoder when your system crashes and journalctl pukes. I dug into systemd deeply because I support Linux and other systems professionally. I’ve studied a lot of the code to run down bugs or issues. I learned it quite well and it seems obvious that I know it’s internals better than it’s cheerleaders do. It shouldn’t be this controversial. The only reason it is stems from the leadership folks not wanting to lose face and admit they made a serious mistake. Systemd sucks on it’s own. It doesn’t need fixing, it needs replacing. It’s bad design that violates the "do one thing and do it well". It does a zillion things: all poorly.

I was a RedHat user back on v5.1. I tried to upgrade my system, and it was awfully painful. But I stuck with RedHat. Then I upgraded again. And again. Every time it got a little less painful, but it still sucked. Then I decided to try out another distro. Mandrake. It was nice, and I liked KDE! I upgraded a couple of times, and it wasn’t too bad. So change was good. After a few more upgrades, it still wasn’t that smooth. I decided to try out Ubuntu, and I really liked it. Since I was liking KDE I switched to Kubuntu. Change was good! I upgraded a couple of times – near flawless! Change was great! Then KDE started to really annoy me – too much flash, and eventually a bug cropped up that caused me all kinds of headaches. So I switched to Xubuntu. XFCE was great, and change was good! I upgraded that system several times, and it was very smooth. After 7 upgrades, things were getting less stable. Since i was going to reinstall anyway, i looked at other distros…. ah, Linux Mint. Polished, but with XFCE not overly so. I had found my distro, change was great! The method of upgrading was to reinstall cleanly, so I made sure to set up my new system so that was minimally painful. Then I was able to upgrade in place – painlessly! All was right.

Then after one upgrade, I noticed that my machine started having various issues. I couldn’t shutdown cleanly. I would take minutes to shutdown, where it used to take seconds. I thought it was hardware at first, but it wasn’t. It was systemd. I hadn’t noticed before upgrading that they were switching to systemd. I had begun to trust Mint so much that I just thought it would be smooth. I learned more and more about systemd, and tried to fix the issue. No deal. So I gritted my teeth and dealt with it. Change can be bad. Eventually I got a different computer, and then I had complete confirmation that my issues weren’t hardware related because they persisted. It was time to find a new distro.

I looked at the BSDs, Arch, Slack, and a few others. But because I was familiar with and really liked the apt package manager, I chose Devuan. It was not only a great distro, but I know that it is specifically focused on NOT implementing systemd. It was a simple install and upgrade, and my system is fast as ever and shuts down within seconds again. So again… change is great!