The officially official Devuan Forum!

sgage

Member

Registered: 2016-12-01

Posts: 341  

Linux systemd Affected by Memory Corruption Vulnerabilities

https://www.bleepingcomputer.com/news/s … tches-yet/

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.

Edit: If you want to follow the fun on Slashdot (or add to it):

https://linux.slashdot.org/story/19/01/ … atches-yet

Last edited by sgage (2019-01-10 21:29:12)

yeti

Member

From: I'm not here: U R halucinating

Registered: 2017-02-23

Posts: 335  

Re: Linux systemd Affected by Memory Corruption Vulnerabilities

  _____( Mwhuaaaaahahahahaaaa.... )

---

*𝚛𝚒𝚋𝚋𝚒𝚝!*

golinux

Administrator

Registered: 2016-11-25

Posts: 3,317  

Re: Linux systemd Affected by Memory Corruption Vulnerabilities

I found the comments at https://forums.theregister.co.uk/forum/ … gs_qualys/ most entertaining

---

Get answers - Help Devuan - Report a bug - Search packages

Panopticon

Member

Registered: 2018-01-27

Posts: 306  

Re: Linux systemd Affected by Memory Corruption Vulnerabilities

Those should be fixed quickly even if no exploits yet for those CVE's.

yeti

Member

From: I'm not here: U R halucinating

Registered: 2017-02-23

Posts: 335  

Re: Linux systemd Affected by Memory Corruption Vulnerabilities

I really hope for Systemd based OSes to evolve into their own direction, so that in a while (months sure will not be enough) they will be an own "digitope" or brand like e.g. Android or ChromeOS is today.

We should applaud on every add-on to Systemd that makes it more incompatible with classic Unixens to support this divergence!
Let them go!
In peace...
The faster, the better!
The farther away, the better!

Last edited by yeti (2019-01-11 15:08:34)

---

*𝚛𝚒𝚋𝚋𝚒𝚝!*

Panopticon

Member

Registered: 2018-01-27

Posts: 306  

Re: Linux systemd Affected by Memory Corruption Vulnerabilities

I just love some of the excuses for systemd behavior in some of those slashdot comments, like .
Its a part of a process copied by another process but we dont know how the actual process works until said process is shared with other processes and copied and sym linked to a set of new usr processes we really should not daemonise. Oh shit, that really caused the memory leak we were after umm no sorry thats bad code sorry.....

Jump, Bounce, Up Down....

https://www.youtube.com/watch?v=wz1ca1-_-MY

Last edited by Panopticon (2019-01-11 16:44:10)