Security

Half a Second

Easter Sunday, and the Linux world is still digesting Good Friday’s news.

On Friday 29 March, Andres Freund, a PostgreSQL developer at Microsoft, posted to the oss-security mailing list. He had been looking into why SSH logins on a Debian unstable box were using more CPU than expected and throwing valgrind errors: an extra half a second or so. What he found was a deliberately planted backdoor in xz / liblzma versions 5.6.0 and 5.6.1, now tracked as CVE-2024-3094 with the maximum CVSS score of 10.

Why It’s Different

This wasn’t a typo-squatted package or a stolen password. The malicious code was added by a contributor who had spent a long time earning trust as a co-maintainer of the project. It was well hidden: it was in the release tarballs, not the public git repository, and it was built to interfere with sshd authentication on systems where sshd ends up loading liblzma.

The good news is that it was caught early. The affected versions had mostly reached bleeding-edge and testing distributions, such as Debian unstable and Fedora pre-releases, rather than the stable releases most of us run in production.

What To Do

  • Check your xz version (xz --version) and follow your distribution’s guidance. Downgrade or update to a fixed package where needed.
  • Check your build pipelines and container base images too, not just servers.
  • Then ask the harder question: how many single-maintainer projects do we depend on, and what would we notice if one of them changed?

Two years ago I wrote about the importance of source code management, after a maintainer deliberately sabotaged their own package. I also recommended a 1984 paper on trusting the code you didn’t write yourself. Both feel uncomfortably relevant this weekend.

The real hero here is curiosity. Someone noticed half a second and refused to let it go. Performance anomalies are worth investigating, even when everything is “working”.

More Information