Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
CVE-2024-3094 was a backdoor planted in the xz compression library after a two-year social engineering campaign, found by chance days before it reached stable Linux distributions.

What Was the XZ Utils Backdoor?
On 29 March 2024, Andres Freund, a PostgreSQL developer at Microsoft, posted to the oss-security mailing list that he had found a backdoor in xz-utils, the compression library present on virtually every Linux system. The malicious code was designed to let whoever held a particular private key execute commands as root on affected servers by connecting over SSH.
It was given CVE-2024-3094 and a CVSS score of 10.0. What makes it the most instructive supply chain case of recent years is not the payload but the method: the attacker became the maintainer.
xz-utils had been maintained largely by one person, Lasse Collin, as unpaid work alongside a job. In 2021 an account named JiaT75, using the name Jia Tan, began contributing. The contributions were real and useful. Over the following two years the account gained commit access, then release authority.
Alongside this, a cluster of accounts appeared in the project’s mailing list and issue tracker complaining about slow releases and pressing for an additional maintainer. Collin had publicly mentioned mental health difficulties and limited time. The pressure campaign, evidently coordinated, created the opening that the patient contributions then filled.
This is not a software vulnerability. It is a human one, and no static analysis tool would have flagged it.
The backdoor never appeared in the git repository in readable form. The components were:
bad-3-corrupt_lzma2.xz and good-large_compressed.lzma, which looked entirely plausible in a compression library’s test suite.m4/build-to-host.m4 macro present only in the released source tarballs, not in git. During configure, it extracted and assembled the payload from those test files.The result was an object file linked into liblzma. Using an IFUNC resolver, it hooked RSA_public_decrypt in OpenSSL’s symbol table. On Debian and Fedora, sshd is patched to link libsystemd for notification support, and libsystemd pulls in liblzma. That indirect chain put attacker code inside the authentication path of the SSH daemon, where a client presenting a certificate signed with the attacker’s Ed448 key could have commands executed as root before authentication completed.
Freund was benchmarking PostgreSQL on Debian unstable and noticed that sshd logins were taking about half a second longer than expected, with unusual CPU use. Valgrind also produced odd errors. Following that thread led him to the compression library and then to the backdoor.
Nobody was auditing xz. The discovery depended on one engineer finding a 500 millisecond anomaly interesting enough to investigate, which is an uncomfortable foundation for the security of the Linux ecosystem.
The malicious versions, 5.6.0 released on 24 February 2024 and 5.6.1 released on 9 March 2024, reached rolling and pre-release distributions: Fedora 40, Fedora Rawhide, Debian testing, unstable, and experimental, openSUSE Tumbleweed, and Kali Linux images built between 26 and 29 March 2024. Arch Linux shipped the version but does not link sshd against libsystemd, so the backdoor did not activate there.
Stable releases of Debian, Ubuntu, Red Hat Enterprise Linux, and Amazon Linux were not affected. The timing was the saving grace: the versions were weeks away from entering Ubuntu 24.04 LTS and Fedora 40 stable.
The defensive conclusions are uncomfortable but concrete:
CISA and the Open Source Security Foundation issued guidance within days, and the episode strengthened the case behind the EU Cyber Resilience Act’s requirements for component inventories. The NCSC’s supply chain guidance makes the same point about knowing what your software is actually built from, which is where most organisations should start.
At Privia Security, we map which hosts run an affected component, and how it reached them, through our Infrastructure Security Testing Services, because the components nobody has looked at are the ones worth looking at.
Only if it ran xz-utils 5.6.0 or 5.6.1 on an affected distribution, which meant Fedora 40 or Rawhide, Debian testing, unstable or experimental, openSUSE Tumbleweed, or a Kali image from late March 2024. Stable Debian, Ubuntu, and Red Hat Enterprise Linux releases shipped older versions and were never vulnerable. Check with xz –version.
Andres Freund noticed that SSH logins on Debian unstable were taking roughly 500 milliseconds longer than expected while he was benchmarking PostgreSQL, and that Valgrind was reporting unusual errors. Investigating the cause led him to liblzma and then to the injected code. It was found by chance rather than by any audit or scanning process.
Debian and Fedora patch sshd to link against libsystemd so it can report readiness to the init system, and libsystemd depends on liblzma. That indirect chain placed the compromised library inside the SSH daemon’s process. Upstream OpenSSH has no such dependency, which is why the issue was specific to those distribution patches.
Maintain a software bill of materials that includes transitive dependencies so you can answer exposure questions quickly. Prefer reproducible builds and build from source control rather than release tarballs where practical. Monitor advisories for the components you actually ship, and fund or contribute to the critical projects your products depend on.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.