back door in ssh; red hat says not affected

Right now no Debian stable versions are known to be affected.
Compromised packages were part of the Debian testing, unstable and
experimental distributions, with versions ranging from 5.5.1alpha-0.1
(uploaded on 2024-02-01), up to and including 5.6.1-1. The package has
been reverted to use the upstream 5.4.5 code, which we have versioned
5.6.1+really5.4.5-1.
 
Debian has been my choice for 30 years.

So basically right from the beginning then. Unfortunately for me, linux wasn't usable as a desktop until about early 2000's. I had both hardware incompatibilities and software that needed windows. I think I finally got everything moved over around 2002. Started on Mandrake and had lots of fun with xfree86 mode lines but switched to Ubuntu when they started up and then a while ago I moved to debian stable.
 
Unfortunately for me, linux wasn't usable as a desktop until about early 2000's.
I didn't start loading the Linux desktop until about 2010 and still mostly don't. Command line only is my preference for servers and I don't run Linux Desktop.
 
I didn't start loading the Linux desktop until about 2010 and still mostly don't. Command line only is my preference for servers and I don't run Linux Desktop.

I haven't run windows since 2002. I've fixed a ton of family/friends machines though so I know I still won't touch it if I can help it. People complain about linux having 2 different feels (qt/gtk) but windows has them beat as every new release comes with a tweak and a change in styling and I bet they must have a mix of 4 or 5 different styles now going all the way back to windows 98 for some config dialogs (I saw one the other day somewhere in the tcp/ip settings I think?)

I'm not necessarily an admin, my line of work is mostly as a software engineer but when you have a small team and you're the only real nerd on it you end up doing a bit of everything.

I doubt this xz malware package would make it past our servers (thankfully), even if the malware ends up being in earlier versions as well. They're saying it looks like a key might be embedded in the software giving him access that way but from the 10 second search I think he still needs an account name, and I've been running fail2ban which cuts anyone off right at the firewall after a few failed attempts. Root is banned of course.
 
SANS update (which is more readable than what I originally posted).

Malicious Code Founds in xz utils
(March 29 & April 1, 2024)


Both RedHat and the US Cybersecurity and Infrastructure Security Agency (CISA) have warned of embedded malicious code in xz utils data compression library versions 5.6.0 and 5.6.1. CISA recommend downgrading to an unaffected version of the library. Researchers Andres Freund reported the vulnerability to Openwall on Friday, March 29.

Editor's Note

[Ullrich]
Luckily, this can be classified as a win for the good guys. But the danger to the supply chain is real. Not only was the backdoor very unique and sophisticated, but it was supported by a long term social engineering campaign at least as complex as the backdoor itself. Take a minute this week, and send a thank you note to an open source project that made a difference for you this week.

[Honan]
This incident brings strong echoes of the famous Ken Thompson's paper, “Reflections on Trusting Trust”. If you have not read it, I strongly recommend you do.
www.cs.cmu.edu: Reflections on Trusting Trust (PDF)

[Dukes]
This attack would have been highly effective if not for an engineer’s curious mind. Of note is the use of an advanced cryptographic scheme that ensures only they can use the bug for attack – a level of sophistication often found in nation-state backed operations. While the focus will be on the integrity of open-source software, it’s also a reminder for product vendors and the security controls they have in place for software configuration management.

[Murray]
APT class actors have discovered the potential efficiency of the supply-chain. We must hold suppliers accountable for shipping malicious code. Open-Source is an easy target and a big risk. At a minimum, we should require open source contributors to sign their work and include a SBOM for any code that they reuse.

[Frost]
What makes this one different is the sophistication and the targeting. This hidden code only appeared on compilation through an M4 macro and within the test trees. This requires a high degree of understanding of how to manipulate compiled binaries in systems. It appears that this was targeting xz’s use in SSH on specific systems. This would be a very innocuous and hard-to-understand backdoor in one of the most critical and trusted secure protocols that we rely on.

Read more in:
- nvd.nist.gov
: CVE-2024-3094 Detail
- www.openwall.com: backdoor in upstream xz/liblzma leading to ssh server compromise
- access.redhat.com: CVE-2024-3094
- www.redhat.com: Urgent security alert for Fedora Linux 40 and Fedora Rawhide users
- www.cisa.gov: Reported Supply Chain Compromise Affecting XZ Utils Data Compression Library, CVE-2024-3094
- www.nextgov.com: CISA sounds alarm on deep-seated vulnerability in Linux tool
- arstechnica.com: What we know about the xz Utils backdoor that almost infected the world
- www.scmagazine.com: Backdoor in utility commonly used by Linux distros risks SSH compromise
- therecord.media: Malicious backdoor code embedded in popular Linux tool, CISA and Red Hat warn
- www.theregister.com: Malicious SSH backdoor sneaks into xz, Linux world's data compression library
 
Back
Top Bottom