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).
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).
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.