ITWire reports: A flaw in systemd, the init system used on many Linux systems, can be exploited using a malicious DNS query to either crash a system or to run code remotely. The vulnerability resides in the daemon systemd-resolved and can be triggered using a TCP payload, according to Ubuntu developer Chris Coulson. This component can be tricked into allocating less memory than needed for a look-up. When the reply is bigger it overflows the buffer allowing an attacker to overwrite memory. This would result in the process either crashing or it could allow for code execution remotely. “A malicious DNS server can exploit this by responding with a specially crafted TCP payload to trick systemd-resolved in to allocating a buffer that’s too small, and subsequently write arbitrary data beyond the end of it, ” is how Coulson put it. Affected Linux vendors have pushed out patches — but the bug has apparently been present in systemd code since June of 2015. And long-time Slashdot reader walterbyrd also reports a recently-discovered bug where systemd unit files that contain illegal usernames get defaulted to root. Read more of this story at Slashdot.
More:
‘Severe’ Systemd Bug Allowed Remote Code Execution For Two Years
An anonymous reader writes “Michael Nielsen has written a detailed article describing the nuts and bolts of a Bitcoin transaction. He builds the concepts from the ground up, starting with a basic, no-frills digital currency. He then examines it for flaws and tweaks the currency to patch up areas where we run into technical or security problems. Eventually, he ends up with Bitcoin, and explains how a transaction works. It’s an interesting, technical read; much more in-depth than any explanation I’ve heard. Here’s a brief snippet from a walkthrough of the transaction data: ‘One thing to note about the input is that there’s nothing explicitly specifying how many bitcoins from the previous transaction should be spent in this transaction. In fact, all the bitcoins from the n=0th output of the previous transaction are spent. So, for example, if the n=0th output of the earlier transaction was 2 bitcoins, then 2 bitcoins will be spent in this transaction. This seems like an inconvenient restriction – like trying to buy bread with a 20 dollar note, and not being able to break the note down. The solution, of course, is to have a mechanism for providing change. This can be done using transactions with multiple inputs and outputs…'” Bitcoin is going through another period of heavy fluctuation: it fell from a high of around $1, 200 per bitcoin to roughly half that, and as of this writing trade around $760 per bitcoin. Read more of this story at Slashdot.