18 ms·
Ubuntu Systemd Vulnerability
- danirod 9y agoWho could have predicted that bloating PID 1 process could result in funny CVEs like this!
- pietroalbini 9y agosystemd-resolved is a separated binary of the systemd project, not the PID 1...
- TimWolla 9y agosystemd-resolved is a separate process (not PID 1) that just was written by the same authors as systemd-the-pid-1.
- tveita 9y agoMaybe there would be less confusion if they changed the name to something not including systemd, and decoupled the development and distribution of these clearly unrelated projects. Then this DNS resolver could get the distribution and usage it deserves based on its own merits. Of course, that's not going to happen, because the creators want systemd to be an OS by itself, with every buggy unreliable component standing as a monument to them only, and that means strong-arming in projects that could never compete with the existing working solutions on merits.
- digi_owl 9y agoEffectively Freedesktop has given up on defining the Linux desktop by specification, and have switched to do so by canonical (heh) implementations.
- digi_owl 9y agoAnd maintained within the same tree so that they can change interface details between the "independent" parts at a whim. In contrast i can pass data between GNU core utils, BSD equivalent, busybox, toybox, and expect things to work. Because the way they communicate is documented and stable.
- vbernat 9y agoNot true: https://www.freedesktop.org/wiki/Software/systemd/InterfacePortabilityAndStabilityChart/ https://www.freedesktop.org/wiki/Software/systemd/InterfaceP....
- digi_owl 9y agoThat is between systemd as a whole and third party code, not between components of systemd (systemd-init, logind, resolved, etc etc etc). In contrast i can mix ls from GNU, grep from BSD, etc, just fine.
- userbinator 9y agoA year ago, there was this: https://lists.dns-oarc.net/pipermail/dns-operations/2016-June/014964.html https://lists.dns-oarc.net/pipermail/dns-operations/2016-Jun... discussed at https://news.ycombinator.com/item?id=11845051 https://news.ycombinator.com/item?id=11845051 The 3rd bullet point is worth reading several times, in order to take in the absurdity of it all.
- kuschku 9y agoOn the other hand, it improves safety and security for many users. Because on most distros, using unbound or BIND9 as local DNS server, they bind to all interfaces, publicly. Which is the reason why DNS amplification DDoS even is possible. I’ve seen it often enough happen, and basically every person who’s set up their own servers has made the mistake of leaving the defaults.
- jeltz 9y agoOn Debian, and I assume its derivates, Unbound will by default only listen to localhost. What distribution has changed this, because I think that is also the upstream default?
- kuschku 9y agoUbuntu 14.04 and Debian old-old-stable listened on all interfaces. The versions provided by most cloud hosters are also misconfigured to listen on all interfaces.
- jeltz 9y agoHm, as far as I can tell Debian has never shipped a version which listens to something other than localhost by default. The upstream fixed this in 2007, before Debian started packaging Unbound.
- lottin 9y agoBut who runs a DNS server? 99% of users only do DNS resolution and for that you don't need to run a DNS server on your system.
- Filligree 9y agoMemory corruption... Someone would ask this sooner or later, so.. why is this written in C, really?
- tormeh 9y agoBecause proper, hardcore programmers never make memory management mistakes and memory management is not that big of a problem, obviously. /s
- 128312983891 9y agoAnd non-hardcore programmers never write anything at all but evangelize other languages instead. /s
- fao_ 9y agoI mean, calling systemd programmers 'proper', 'hardcore', or even 'responsible' is a real stretch [http://suckless.org/sucks/systemd http://suckless.org/sucks/systemd]
- setq 9y agoIndeed. Merely "loud" programmers with corporate backing.
- revelation 9y agoThat is not what springs to mind, more "why the fuck are you reimplementing DNS in init". Like, this stuff was built tens of years ago and that code is crappy too but we have pretty much got rid of the most obvious security issues. Nobody wants to relive history so you can finally implement a broken DNS client.
- s_kilk 9y ago> "why the fuck are you reimplementing DNS in init" Because systemd
- vertex-four 9y ago
- jaimehrubiks 9y agoDoes this affect computers that did not ask for such packet (dns response)?
- chillydawg 9y agoDNS is UDP so you might just get a broken packet sent to you, I guess?
- wwwv 9y agoTCP or UDP transports.
- icebraining 9y agoOnly if daemon is listening to the outside, which I hope is not the case by default.
- agwa 9y agoIt's extremely easy to induce a computer to make a DNS request. For example, embed an IMG tag in a web page pointing to the attacker's domain. Anyone loading that page will get the malicious DNS response.
- sunseb 9y agoLet's face it: systemd is a bad design... The solution I found: FreeBSD and OpenBSD !
- fao_ 9y agoYou might like suckless.org
- digi_owl 9y agoThere are Linux distros that still have not succumbed.
- dijit 9y agoNone that I would use in production (as a sysadmin)
- na85 9y agoSlackware ?
- _ZeD_ 9y agoNot even a slackware?
- teksimian 9y agomaybe if they had package dependencies sorted out. they didnt last time i checked.
- digi_owl 9y agoCould have sworn that i have seen companies opt for Gentoo in production, because they could tailor the end result specifically to their needs...
- mobilethrow 9y agoI've been toying with GuixSD recently and really love the immutable system configurations. There are some caveats, but I would not mind using it on production servers. Sadly I haven't been able to convince my colleagues yet.
- throwawaymanbot 9y agoIs anyone else fed up of systemd yet? Increasingly Jack of all trades, master of none. Can we have something new instead? Or maybe Red Hat can put Pottering back in his holster? I'm sick of Linux Servers I use, being "improved" with Desktop implementation in mind.
- setq 9y agoYes. I've burned hours on systemd related problems that just didn't exist before. From DBus message delivery failures, debugging things that haven't broken for 20 years (which has incidentally got MUCH harder) to the whole shit crock that is NTP and locale management. That and the whole desktop buggery that has been going on for the best part of 8 years now has really put me off. To be honest you haven't really experienced systemd's fuckery until you have a hosed box. It's like negotiating a boot with a pigeon. Any other platform is ZERO hassle and that includes windows, OSX, freebsd, openbsd etc. And you can't criticise it anywhere (watch the downvotes). The problem is it lacks the mysterious as in Zen and the Art of Motorcycle Maintenance class "quality". Merely glitter around a turd. However we're stuck with it so it's suck it up or move on. On the subject of moving on, you could run FreeBSD to run your servers. Much lower resource overheads, native ZFS, simple service management, some documentation worth more than toilet paper and the best thing of all, more sleep at night. Now there are binary updates and packages it's pretty easy. No more make world of any of that stuff.
- throwawaymanbot 9y ago> However we're stuck with it so it's suck it up or move on. This here is the hubris and arrogance of the entire thing. I take heart that in the linux community, there is enough technical skill to come up with a viable, more in spirit of linux alternative. And I believe that I shall see the day where it is implemented. Lenny P and the gang should be less arrogant, and better at improving their product with this in mind. No one needs red hats "buy in" for this.
- digi_owl 9y agoThing is that none of them have the backing of Red Hat's finances. Thus they can'ẗ keep up with the churn that systemd and other RH backed projects produce.
- avian 9y agoCurrent situation in Debian: Jessie is not vulnerable. Stretch is vulnerable (no patch yet), but systemd-resolved is not enabled by default. https://security-tracker.debian.org/tracker/CVE-2017-9445 https://security-tracker.debian.org/tracker/CVE-2017-9445
- Etzos 9y agoThe title is slightly misleading since it is specifically the optional (but installed by default on Ubuntu) systemd-resolved package (an ancillary package under the systemd name), not systemd the init system as I think many people will assume. Edit: It seems Ubuntu builds it together with systemd so users have no choice. There may be a good technical reason for this, but I'm not sure what it is because it seems very user-hostile to remove choice like this. Edit2: Upon further inspection this appears to be common practice, you just don't enable the parts you don't want. It would be nice if they could be put into separate packages or something of that nature though.
- pietroalbini 9y agoI don't exactly know why it's in the same package as systemd, but why do you consider it an user-hostile decision? Unless you have so little storage you can't afford to have an extra binary installed in the system, there is no downside of having it on the machine. You can still disable the daemon and switch to another one (like dnsmasq), as if it was in a different package.
- Etzos 9y agoIt's not as user-hostile as I originally assumed (I thought it was built and enabled with no option to turn it off). As long as it can be completely disabled so that nothing will ever touch it, then it's fine. And that does indeed appear to be the case here. Regardless, I'm sure there are some people who would love to claim a few KiB back without having to compile things for themselves.
- Shish2k 9y agoTechnically it's not a huge problem; politically, bundling unrelated software together means that the bundled software has an advantage and a tendency to get more market share than its competitors who compete fairly. In the case of open source distros, I'm sure that this isn't illegal, but it seems like it isn't in the interests of the community.
- pietroalbini 9y ago
- runn1ng 9y ago"Rewrite It In Rust" should be the default, pre-set comment to every article about every vulnerability
- tyingq 9y agoMaybe every memory access related one. I assume rust still allows you to pass untrusted user input around, for example.
- fetbaffe 9y agohttps://github.com/ansuz/RIIR https://github.com/ansuz/RIIR
- setq 9y agoWell no not really. Vulnerabilities exist outside the realms of the language implementations. There are poorly designed protocols and access controls to contend with as well. I'd argue there are a lot more of those classes of problems out there. The ones enabled by programming languages are merely easier to find as you don't have to understand the precise problem domain of the application for each one found.
- rurban 9y agoUsing a safe language would help even more. Safer than C != Safe.
- the_common_man 9y ago16.04 is not affected
- teksimian 9y agoI bet init is also unaffected.
- 5ilv3r 9y ago14.04 used upstart (also used by chromeos). sysvinit was used in ubuntu prior to upstart, and there are some distros that use bsd style init. Go read up on init system options a bit more.
- teksimian 9y agoyes, i'm aware of bsd init, sysvinit, upstart, systemd et al. systemd & upstartd all aim to replace pid 1/init. Which as far as i'm concerned anything beyond bsd init is over complicating things, and these are the results.
- deleted 9y ago[deleted]
- agwa 9y agoThe most dangerous thing about systemd-resolved is that it exposes its own non-standard DNS resolution protocol over dbus, which the documentation recommends applications use instead of standard, interoperable protocols[1]: > The native, fully-featured API systemd-resolved exposes on the bus. See the API Documentation for details. Usage of this API is generally recommended to clients as it is asynchronous and fully featured (for example, properly returns DNSSEC validation status and interface scope for addresses as necessary for supporting link-local networking). systemd wants applications to depend on systemd-resolved so it becomes irreplaceable. This is very bad, because the first thing you should do on a system with systemd-resolved is uninstall it. The systemd developers are not qualified to write either DNS software[2] or C code that talks to the network. [1] https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html https://www.freedesktop.org/software/systemd/man/systemd-res... [2] See http://seclists.org/oss-sec/2014/q4/592 http://seclists.org/oss-sec/2014/q4/592, which came out after Lennart Poettering had the hubris to call systemd-resolved a "pretty complete caching DNS and LLMNR stub resolver"[3] even though the dangers of DNS cache poisoning were already well known at the time. [3] https://lwn.net/Articles/609740/ https://lwn.net/Articles/609740/
- RussianCow 9y agoDoes anyone have any insight as to why systemd has its own DNS resolution API? That seems like a very strange decision. Is it really only so that systemd "becomes irreplaceable"?
- 5ilv3r 9y agoIt's more about dbus, really. They are trying to get rid of 'everything is a file' and move to a pub/sub service model.
- deleted 9y ago[deleted]
- rsync 9y ago"They are trying to get rid of 'everything is a file' and move to a pub/sub service model." I thought we were trying to move towards "everything is a file" ... isn't that the goal of the plan9/Inferno movement ? I thought that was the progressive direction in UNIX design. We want to move away from "everything is a file" ?
- 5ilv3r 9y ago> systemd-resolved could be made to crash or run programs if it received a specially crafted DNS response. As nation states are hording zero days, and the security sheep herd insists updates are the way to go, I have never been more convinced that sticking to an OLD AND TRUSTED source code base for your infrastructure is the way to go. You can pop layers on top of that to get newer software running if you like, but trying to keep up with this psuedo-rolling-release avalanche of crap coming down the pipe is not a fair burden for administrators to handle. The devs need to shove it because we don't want it. I am hoping the next economic recession starves out the enthusiasm for disposable infrastructure and "move fast and break things" and businesses can go back to focusing on long term stability.
- rsync 9y ago"I have never been more convinced that sticking to an OLD AND TRUSTED source code base for your infrastructure is the way to go." I recently (2016) built a little network appliance for a specific task that needed to be safe and secure. I used FreeBSD 4.11.
- qb45 9y agoAre you sure it has no remote vulns since it's been discontinued or did I just prove Poe's law?
- wahern 9y agoI think that's called security by obsolescence. Not sure how well that actually works. Root kits don't just disappear and FreeBSD 4.1 isn't as obscure as, say, VMS. But as long as there are no remote vulnerabilities it's probably no worse than a typical Linux install, in the sense that both would be trivially rootable once you get your foot in the door.
- 5ilv3r 9y agoUsually with BSD you can apply new patches to old systems without any trouble. No need to upgrade everything.
- deleted 9y ago[deleted]
- ausjke 9y agoDebian without systemd: https://devuan.org/ https://devuan.org/
- ausjke 9y agoDebian without SystemD https://devuan.org/ https://devuan.org/
- TotallyGod 9y agoLooks like you need to make a DNS request to a malicious server to be vulnerable. This means you are safe if you are using 8.8.8.8? Or another trusted network? (Or your ISP if you trust they haven't been compromised).
- qb45 9y agoThe real danger is a script kiddie on your LAN with a sniffer or some advanced attacker in the position to MITM you on the wide Internet, depending on whether you are a small fish or a big fish.
- 5ilv3r 9y agoUS corporations control the root name servers and seem to have no problem cooperating with government requests to fuck^H^H^H^Hkeep a close eye on everyone else.
- pas 9y agoK root is operated by RIPE NCC M root is opreated by WIDE from Japan http://root-servers.org/ http://root-servers.org/ Use DNSSEC, it's pretty tamper proof, keys are in HSM and "geo distributed" ( https://www.schneier.com/blog/archives/2010/07/dnssec_root_key.html https://www.schneier.com/blog/archives/2010/07/dnssec_root_k... ), the weak points are probably the facilities themselves in the US (one on the East Coast and one on the West Coast), but the trust anchor is pretty much fixed in the root servers, and it'd be quickly discovered if someone rolled a new one out of schedule.
- tptacek 9y agoDNSSEC does absolutely nothing to resolve the problem the parent commenter is referring to. In fact, DNSSEC cryptographically ratifies the status quo of the most important TLDs being de-facto controlled by Five Eyes governments. In years of watching for mentions of DNSSEC on HN, I can't remember off the top of my head a single case in which DNSSEC was introduced into a conversation as having some benefit where that benefit was real. It's weird what people believe about DNSSEC.
- alsadi 9y agoIt only affect ubuntu's way of systemd that is discouraged by systemd's community Some one called a title another systemd's vulnerability a click biat Quote Try to guess what title catches more clicks: 1. CVE-2017-9445: systemd Hit By New Security Vulnerability 2. CVE-2017-9445: systemd-resolved, which is not recommended on most systems and isn't used outside of Ubuntu Hit By New Security Vulnerability
- JdeBP 9y agoThis is not CVE-2017-9217, note. * https://github.com/systemd/systemd/pull/5998 https://github.com/systemd/systemd/pull/5998 * https://news.ycombinator.com/item?id=14451642 https://news.ycombinator.com/item?id=14451642