23 points
*

So as a new Linux guy that just has Ubuntu installed on a laptop running media server, sounds like I shouldn’t be worried since it is NAT’d behind my router and this worm compromises telnet and SSH connections. Am I getting the gist right? Totally newb here again.

permalink
report
reply
34 points

Not particularly security savvy, but :

The infected devices then attempt to crack the telnet password by guessing default and commonly used credential pairs.

My understanding is that the worm is targetting connected devices with supidly simple credentials, which is why “Internet-of-Things” is mentioned?

permalink
report
parent
reply
16 points

Looking at sites like insecam.org, the amount of devices still sett to admin/admin is frighteningly high

permalink
report
parent
reply
1 point

There will always be new malware. Just update regularly and use your head. Don’t worry about it too much

permalink
report
parent
reply
5 points

Conventional Linux use should be fine. It’s targeting SSH connections to other things over the net; connecting to a server, remote camera, etc. So it reverse engineers the connection by brute-forcing(?) Weak ssh passwords to install the malware.

I’m not an IT professional but this is my layman interpretation.

permalink
report
parent
reply
5 points

Systems with exposed SSHd, but also properly configured, are also not at risk.

permalink
report
parent
reply
3 points

Hard to tell at a glance.

The telnet vulnerability allows it to infect some older IoT devices (such as CCTV cameras) or if you are using an older router where telnet is enabled (or may be enabled by default). Most modern devices don’t use that method anymore due to security concerns.

The SSH vulnerability can affect a lot more devices. So if you have a Raspberry Pi on your network with a default account/password or a weak password then it can infect that and spread to other devices on your local network. Or maybe a cheap IoT device that has weak security… same problem.

A concern for you is if you have some other device on your network that was vulnerable, because then that device can serve as a point for the worm to jump to your other devices (if they also use default passwords or weak passwords).

Another big question to ask is whether you have UPnP enabled on your router.

Either way I would make sure that you have strong passwords, change the default username, etc, on all of your devices.

permalink
report
parent
reply
4 points
*

People are giving some advice but it doesn’t seem appropriate for an absolute newbie. Here’s what I’d say. Absolutely do not run telnet. Because it’s so insecure and everyone knows that, it’s usually not on by default, and you would have had to start it yourself somehow. It’s unlikely that you did that, but you can check to see.

If you’re new, you very likely don’t need an SSH server running. Unless you’re logging into that computer remotely, you don’t need it. It’s probably not running, but it’s conceivable that it could run by default. Check to see and disable it if you don’t need remote login.

If you do need remote login, use SSH and use a very good password. Ideally, you’d need to leave newbie territory and use public-private keys instead of a password. It’s also not a bad idea to use a nonstandard port, instead of 22. That doesn’t beef security much, but many scanners are going to look for 22 and nothing else.

permalink
report
parent
reply
1 point

To add to this, install fail2ban (most distros have it in their package system) and activate it for the various things that use username/passwords in your system.

Basically it monitors access logs and blocks the IPs that repeatedly fail logins.l for a certain amount of time.

This drastically reduces the effectiveness of brute force attempts - as long as your password isn’t, “password” and guessable in one go.

permalink
report
parent
reply
2 points

Thank you for the well thought out response! I, myself do know my way around networking a bit. Linux in general is what I am just now dipping my toes in. Loving it and learning a lot.

permalink
report
parent
reply
1 point

Can you connect to your server when not on your network?

If no, you’re definitely ok.

permalink
report
parent
reply
4 points

NOT the boreworm!!

permalink
report
reply
3 points

Flash, ahhhhh!

permalink
report
parent
reply
6 points

I’m guessing, per the article, that as long as you’re not exposing telnet/ssh directly, you should be ok? If you’re doing that already, why? I could see having some iot device that isn’t properly segmented from the rest of your lan already problematic, and something like this would be a concern.

permalink
report
reply
-28 points

I shouldn’t be on Linux, I don’t know anything about computers. This is why Windows is the safer bet.

permalink
report
parent
reply
24 points

Whenever linux has a big sercurity issue, its a big deal. whenever windows has a big security issue, its just another tuesday.

That should tell you that windows systems are targeted much more.

permalink
report
parent
reply
1 point

True, but that’s the point.

Linux isn’t safer because it’s more secure, it’s safer because no one writing malware is going to target only 4% of the market when they could write malware for 60% of the market.

permalink
report
parent
reply
2 points

I think it’s because the general public would expect a big company to come and fix it, like Microsoft. They feel safe because it’s a well known OS that everyone uses. So it can’t be unsafe, right? Right?

With Linux you’re fucked if you have no computer knowledge, like most people. That’s the general thinking.

permalink
report
parent
reply
3 points

The security threat isn’t the issue, my skillset is.

permalink
report
parent
reply
1 point

By Jehovah you can’t say that on Lemmy!

permalink
report
parent
reply
10 points

This is why you don’t allow password login for SSH, especially not on systems that are accessible from the internet.

permalink
report
reply
2 points

This might as well be an article about windows systems exposing RDP to the internet.

permalink
report
parent
reply
140 points

This is just an attack that attempts common username/password combinations on ssh, and the article even states that the worm is dime-a-dozen. Unless you have both password auth enabled and an available account with an easily guessable password (and if you have either you should change that), this is nothing to worry about, even with sshd available to the internet.

Sensationalist title.

permalink
report
reply
38 points

Thank you, spared me from giving attention to an unworthy article

permalink
report
parent
reply
4 points

savedusaclick

permalink
report
parent
reply
17 points

Hell, even having a lax fail2ban stops these attacks.

permalink
report
parent
reply
9 points

Prevention, as always, is much easier than a cure.

permalink
report
parent
reply

Technology

!technology@lemmy.world

Create post

This is a most excellent place for technology news and articles.


Our Rules


  1. Follow the lemmy.world rules.
  2. Only tech related content.
  3. Be excellent to each another!
  4. Mod approved content bots can post up to 10 articles per day.
  5. Threads asking for personal tech support may be deleted.
  6. Politics threads may be removed.
  7. No memes allowed as posts, OK to post as comments.
  8. Only approved bots from the list below, to ask if your bot can be added please contact us.
  9. Check for duplicates before posting, duplicates may be removed

Approved Bots


Community stats

  • 17K

    Monthly active users

  • 12K

    Posts

  • 543K

    Comments