New Multi-Purpose Backdoor Targets Linux Servers
An anonymous reader writes A new multi-purpose Linux Trojan that opens a backdoor on the target machine and can make it participate in DDoS attacks has been discovered and analyzed by Dr. Web researchers, who believe that the Chinese hacker group ChinaZ might be behind it. "First, Linux.BackDoor.Xnote.1 sends information about the infected system to the server. It then goes into standby mode and awaits further instructions. If the command involves carrying out some task, the backdoor creates a separate process that establishes its own connection to the server through which it gets all the necessary configuration data and sends the results of the executed task," the researchers explained.
Well those certainly look like reputable links by famous 'researchers' to me! As an IT guy, I'll definitely have to go click on them so that my workstation gets infected too.
You have to run the file as a system admin for it even to work. This is a non issue joke.
The source was Dr. Web's own marketing page.
This smells like a press release (which smells coincidentally like spam).
Come on!!!
What vulnerability? What port? What gets attacked?
Is there more than one vulnerability?
I wonder -- I really, really wonder. Are Slashdot "editors" getting kickbacks?
What a loaded pile of crappy advertising.
OpenBSD has always supported networking.
"The malware will only be installed in a system if it has been launched with superuser (root) privileges"
aaaand i've already gone back to my tea.
any sysop worth her salt knows the rules:
0. It will build without root or not at all.
1. It will come from a repository or reputable source.
2. It will check its md5 and check it twice.
3. It will be compatible with standard secops tools like chroot, jails, cgroups, propolice, and selinux. this includes sandboxing.
4. Isolate, quarantine, and deploy the secops team. any compromised machine, any network, any server without question.
5. Slap about with a large bit of herring or trout the dev or luser in accordance with LART policies.
Good people go to bed earlier.
"Who also know nothing about Unix/Linux"....
Who are the editors here, and have they ever even *used* a linux distribution????
If telephones are outlawed, then only outlaws will have telephones.
The linked article mistranslates the original russian.
The vector is SSH, brute force attempts to guest the root password. The net-security article mistranslates to SSL.
That would have been funnier if you didn't refer to your "back door" as "Multi Purpose" :-0
At minimum, it passes solids, liquids, and gases... and sometimes, you'd swear, plasma. I call that multi-purpose.
"You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
"A new multi-purpose Linux Trojan that opens a backdoor on the target machine and can make it participate in DDoS attacks has been discovered and analyzed by Dr. Web researchers.
.. The malware will only be installed in a system if it has been launched with superuser (root) privileges".
How does the 'Trojan' get onto the target machines?
"To spread the new Linux backdoor, dubbed Linux.BackDoor.Xnote.1, criminals mount a brute force attack to establish an SSL connection with a target machine
For fucks-sake slashdot, remember when this was a serious technology mag, instead of providing free adverts to some AV company.
Actually, it's pretty simple to stop SystemD from listening on network ports. It's called "socket activation". Look it up. It's pretty neat. All you need to do is stop the specific socket service, and then edit the appropriate socket file.
You'll also be interested to know that the Debian install of SystemD doesn't use socket activation by default. Not yet, anyway.
As for systemd security auditing, from what I've heard, the people at Redhat run the source code through various tools designed to pick out bugs. Also, I've read of at least one person doing an independent audit of the code. I presume there would be many more than that. So, as far as security testing is concerned, it's far from having nothing done.
There's always a workaround. Even for SystemD.