this post was submitted on 10 Jan 2024
99 points (70.7% liked)

Technology

59581 readers
3372 users here now

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


founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 23 points 10 months ago* (last edited 10 months ago) (7 children)

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.

[–] [email protected] 34 points 10 months ago (1 children)

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?

[–] [email protected] 16 points 10 months ago

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

[–] Jackinopolis 6 points 10 months ago

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.

[–] [email protected] 5 points 10 months ago

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

[–] [email protected] 4 points 10 months ago* (last edited 10 months ago) (2 children)

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.

[–] [email protected] 2 points 10 months ago

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.

[–] [email protected] 1 points 10 months ago

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.

[–] [email protected] 3 points 10 months ago

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.

[–] [email protected] 1 points 10 months ago

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

If no, you're definitely ok.

[–] [email protected] 1 points 10 months ago

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