this post was submitted on 19 Oct 2023
80 points (96.5% liked)

Technology

34780 readers
222 users here now

This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.


Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.


Rules:

1: All Lemmy rules apply

2: Do not post low effort posts

3: NEVER post naziped*gore stuff

4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.

5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)

6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist

7: crypto related posts, unless essential, are disallowed

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] NocturnalMorning@lemmy.world 20 points 1 year ago (1 children)

Read the article. I think you're misunderstanding the exploit.

[–] TheDarkKnight@lemmy.world 3 points 1 year ago (2 children)

Yeah this is one is on Cisco in general, still wondering why you'd have the web interface enabled anyways...just asking for problems right there.

[–] Shadow@lemmy.ca 8 points 1 year ago* (last edited 1 year ago) (1 children)

If a fresh deployment isn't secure out of the box, that's definitely on cisco. There's a lot of people out there who just plug in some hardware and then use the GUI to configure it. Just because it's best practice to turn it off, doesn't mean everyone is skilled enough to do so.

We did have one compromised router from this at work, a fresh deploy that someone did a while ago and then the project got put on hold before it was actually configured. Was just sitting there with a public IP not doing much, but sure enough it was owned when I looked.

One interesting thing is that the machine had HTTP enabled, but we had locked down SSH already. In the config you could see the attacker tried to enable SSH but couldn't get it working (subnet inverted, lol cisco).

[–] TheDarkKnight@lemmy.world 1 points 1 year ago

Yeah it is on Cisco, not questioning that.

Good catch getting it early, teach the young guys to kill those web portals...nothing but trouble. But I hear ya, sometimes CLI can be a pain.

On a home network, I like having the web UI enabled for local access out of convenience, and I like buying higher end networking equipment. I don't enable it for external access though, that's just asking for trouble.

It makes absolutely no sense in an enterprise environment, but there are a non-trivial number of non-enterprise customers of enterprise equipment.