Slashdot Mirror


Hundreds of Cisco Switches Vulnerable To Flaw Found in WikiLeaks Files (zdnet.com)

Zack Whittaker, writing for ZDNet: Cisco is warning that the software used in hundreds of its products are vulnerable to a "critical"-rated security flaw, which can be easily and remotely exploited with a simple command. The vulnerability can allow an attacker to remotely gain access and take over an affected device. More than 300 switches are affected by the vulnerability, Cisco said in an advisory. According to the advisory, the bug is found in the cluster management protocol code in Cisco's IOS and IOS XE software, which the company installs on the routers and switches it sells. An attacker can exploit the vulnerability by sending a malformed protocol-specific Telnet command while establishing a connection to the affected device, because of a flaw in how the protocol fails to properly process some commands. Cisco said that there are "no workarounds" to address the vulnerability, but it said that disabling Telnet would "eliminate" some risks.

76 comments

  1. hmmmm by Anonymous Coward · · Score: 0

    typically cisco has a fix ready for the NSA backdoors. this one must have been a missed memo from NSA.

  2. If you still run Telnet by subk · · Score: 3, Interesting

    You deserve to have this happen to you.

    --
    Now, if you'll excuse me, I have backups to corrupt.
    1. Re:If you still run Telnet by Anonymous Coward · · Score: 0

      but what if I took special precautions and use it in the following fashion?:


      while read -p "> " command ; do echo "$command" | rot26 'secret_key!' | telnet 127.0.0.1 31337 ; done

    2. Re: If you still run Telnet by Anonymous Coward · · Score: 1

      It's more like, if you intentionally run into a wall, you can expect your head hurt.

    3. Re: If you still run Telnet by bobbied · · Score: 0

      Those in glass houses should not do target practice with a sling shot in the hose unless they expect to break glass....

      OR...

      Those who drive though nails should expect to get flat tires...

      If you do stupid things, you get what is coming to you.

      Cisco has warned users for decade NOT to use telnet, just like they have warned users to change the default username and password (cisco/cisco). If you don't get the message or insist on being stupid, you get what's coming to you.

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    4. Re: If you still run Telnet by Anonymous Coward · · Score: 0

      They sell them a product and warn them not to use it, you think this is OK? What world do you live in?

    5. Re: If you still run Telnet by Anonymous Coward · · Score: 0

      Your car will exceed the speed limit, no? The speed limit warns you not to use the accelerator or face consequences.

      Just because you can, doesn't mean you should.

    6. Re: If you still run Telnet by Anonymous Coward · · Score: 1

      I live in a world where customers bitch to holy hell if you turn off telnet. Without going into details, I can say that millions of devices are today shipping with Telnet as a feature because so many customers threatened to walk if we disabled it and forced SSH. And at the end of the day it's my job to make things people want to buy, not tell them what to buy because I know better than they do. Customers don't like that, and they don't buy stuff from you if you treat them that way.

      BTW, the same damn thing is true of SNMPv2. Customers will NOT buy the damn product if you force V3 because it's secure.

      There are many other examples. Ignorant whiners can complain all they want, but customers rule the roost.

    7. Re: If you still run Telnet by Anonymous Coward · · Score: 1

      >protocol you don't like
      >telnet sends information in cleartext

      Anyone using telnet to connect to a network is either unqualified or mentally incapable of critical thought. I'll just assume you're not up on all that decade-old networking jazz.

    8. Re: If you still run Telnet by Anonymous Coward · · Score: 0

      As an exact example of this, I own a Ducati 900 SS motorcycle. In the first few pages of the manual there are safety instructions that explicitly say, multiple times; "WARNING: This vehicle is capable of extremely high rates of speed and should be used with caution by experienced operators only." (Or something to that effect, I don't have the manual in front of me at this moment for the exact wording.)

    9. Re:If you still run Telnet by Anonymous Coward · · Score: 0

      Yeah, except see, for a long, long time, Cisco considered all forms of cryptography, including SSH, a feature you had to pay extra for.

    10. Re: If you still run Telnet by Anonymous Coward · · Score: 0

      Outdated, use rot52.

  3. That's nice, but... by acoustix · · Score: 2

    That means someone would have to be dumb enough to
    1) Have the mgmt of the switch be publicly available
    2) Have Telnet enabled.

    Don't get me wrong, it's a bad bug. But a security-minded admin should not have these problems.

    --
    "A plan fiendishly clever in its intricacies"- Homer Simpson
    1. Re:That's nice, but... by HumanWiki · · Score: 4, Interesting

      That means someone would have to be dumb enough to
      1) Have the mgmt of the switch be publicly available
      2) Have Telnet enabled.

      Don't get me wrong, it's a bad bug. But a security-minded admin should not have these problems.

      Err.. yes/no..

      If I was going to attempt to exploit something like this, I'd assume most would be inaccessible from the internet as a general use or would be white listed only..

      What I WOULD do is use this in conjuction with a machine level hack/compromise inside their network and then run amuk from there.. That's much easier to do and less will have full firewall off from within their networks from all PC segments.

    2. Re:That's nice, but... by sunderland56 · · Score: 2

      That means someone would have to be dumb enough to
      1) Have the mgmt of the switch be publicly available
      2) Have Telnet enabled.

      3) Purchase from a vendor that does not understand security well enough to disable telnet.

    3. Re:That's nice, but... by skids · · Score: 1

      Most switches support ACLs on all services, and/or on switch SVIs (if you don't have prohibitively many of those), and/or CoPP, so you can tell the switch not to talk to anything but your management stations. You just have to set things up so you can alter those ACLs en-masse when needed. No need for a firewall, really, as long as you aren't using ridiculous utilities that do not belong on a switch in the first place.

      That said, there's pretty much zero reason to use telnet these days, and even the last vestiges of FTP and TFTP are starting to become unnecessary as more switch facilities are supporting SCP or (sigh) SFTP. Sigh on the latter because you really are putting a lot of trust in the other end of the connection because SFTP subprotocol code is not production quality code, even in the openSSH tree. But at least someone has to actually own the endpoint to get at it.

    4. Re:That's nice, but... by HumanWiki · · Score: 3, Insightful

      Most switches support ACLs on all services, and/or on switch SVIs (if you don't have prohibitively many of those), and/or CoPP, so you can tell the switch not to talk to anything but your management stations. You just have to set things up so you can alter those ACLs en-masse when needed. No need for a firewall, really, as long as you aren't using ridiculous utilities that do not belong on a switch in the first place.

      That said, there's pretty much zero reason to use telnet these days, and even the last vestiges of FTP and TFTP are starting to become unnecessary as more switch facilities are supporting SCP or (sigh) SFTP. Sigh on the latter because you really are putting a lot of trust in the other end of the connection because SFTP subprotocol code is not production quality code, even in the openSSH tree. But at least someone has to actually own the endpoint to get at it.

      Yes, I understand that, that's great, a lot of that is best practice and in all my years and all the companies I've worked for and systems I've helped migrated, worked on, have managed, etc. I can count on one hand the number of them that were properly configured with ACLs blocking of stuff from user segments, properly configured interconnectivity, complex passwords, clear text protocls being fully off, etc. Not allowing this station etc. And you think your management computers are safe? not really. I've seen plenty of bastion systems being used as source mgmt points for all manner of systems and lazy engineers using web browsers on them to download whatever utility or tool they need. Just because you've locked out your stuff to a bastion server doesn't mean it's protected, it just means your compromise point is now actually pinpointed to a singular or group of devices. Lucky me. Less field work to do.

      That's all great on paper, but it's not as wide-spread in most places as you'd think. I've met many CCIEs that are outright lazy when it comes to locking down switching and routing connections because it makes their job even harder to deal with the ever changing zones, lans, nodes, and whatever wildass hair mgmt gets in their butt that week about which people/persons "need" access to what and when.

      I use firewall generically here and not literally a Firewall as well.

    5. Re:That's nice, but... by bobbied · · Score: 1

      Now that's not fair. Cisco goes to great lengths to make sure the users know to TURN OFF TELNET. It's been in their documentation for decades. It's one of the first things you learn in CCNA training.

      Now, how do you suppose one would configure a cisco switch from bare metal w/o special hardware if they didn't do this?

      --
      "File to fit, pound to insert, paint to match" - Aircraft Maintenance 101
    6. Re:That's nice, but... by Anonymous Coward · · Score: 0

      4) buy slaveware switches like a dumb fuck.

    7. Re:That's nice, but... by Lumpy · · Score: 1

      Exactly. Management VLAN should be very protected.

      --
      Do not look at laser with remaining good eye.
    8. Re:That's nice, but... by Anonymous Coward · · Score: 0

      > documentation for decades.

      No. I managed hundreds of routers and dozens of switches when I retired in 2003. I have never used SSH with a cisco switch nor do I remember see it in the documentation before I retired. cisco has not supported that for "decades." Maybe half a decade, but certainly not decades.

    9. Re:That's nice, but... by WhiteKnight07 · · Score: 1

      If they bothered to generate a keypair on first boot, then SSH. Problem solved. The F5 LTM does this. Why can't a switch? Besides, its not like a Cisco console cable is "special hardware". Especially in the networking world. If you work with any amount of Cisco gear you probably have 20+ of the things just lying around on desks and stuffed in drawers. Hell, I have crimped my own Cisco compatible console cables on many occasions, its not like the pinout is a secret or anything. There is absolutely no reason for any piece of serious network hardware to ship from the factory with telnet enabled.

      --


      We're going to make information free Mr. Anderson, whether you like it, or not.
    10. Re:That's nice, but... by acoustix · · Score: 2, Informative

      That means someone would have to be dumb enough to
      1) Have the mgmt of the switch be publicly available
      2) Have Telnet enabled.

      3) Purchase from a vendor that does not understand security well enough to disable telnet.

      Telnet is not enabled by default on any interface on Cisco switches. I've been using them since 1999 and I can't think of a time when an out-of-the-box switch had Telnet enabled.

      --
      "A plan fiendishly clever in its intricacies"- Homer Simpson
    11. Re:That's nice, but... by acoustix · · Score: 1

      That means someone would have to be dumb enough to
      1) Have the mgmt of the switch be publicly available
      2) Have Telnet enabled.

      Don't get me wrong, it's a bad bug. But a security-minded admin should not have these problems.

      Err.. yes/no..

      If I was going to attempt to exploit something like this, I'd assume most would be inaccessible from the internet as a general use or would be white listed only..

      What I WOULD do is use this in conjuction with a machine level hack/compromise inside their network and then run amuk from there.. That's much easier to do and less will have full firewall off from within their networks from all PC segments.

      Which would still require Telnet to be enabled.

      --
      "A plan fiendishly clever in its intricacies"- Homer Simpson
    12. Re:That's nice, but... by Megane · · Score: 2

      I worked *FOR* Cisco in the early 2Ks (as a Software Eng, but not on IOS) and I recall them being very slow to put SSH into their firmware, long after the problem of plaintext passwords was well known. I don't think they even had it by 2005. So maybe *a* decade at most, but not decade*s* plural.

      --
      #naabhaprzrag, #sverubfr-000, #agi-fcbafberq, negvpyr[pynff*=' negvpyr-ary-'] { qvfcynl: abar !vzcbegnag; }
    13. Re: That's nice, but... by PoopJuggler · · Score: 2

      No reason except for Cisco getting paid by the government to make their products exploitable...

    14. Re:That's nice, but... by Anonymous Coward · · Score: 0

      >R&S CCIE
      >expected to be a security expert

      Might as well as them to design your 5,000 host network while you're at it. R&S is more for, well, routing and switching. What a concept.

    15. Re: That's nice, but... by Anonymous Coward · · Score: 0

      And when they did it was SSH v1

    16. Re:That's nice, but... by Barlo_Mung_42 · · Score: 1

      To be fair, the headline said "hundreds". I came in thinking that's not bad at all.

    17. Re:That's nice, but... by pnutjam · · Score: 1

      Lazy admins are a dime a dozen, which is what companies want to pay, unfortunately.

    18. Re:That's nice, but... by pnutjam · · Score: 1

      Serial port, even a standard ssh account would be more secure then telnet. Telnet should be disabled.

    19. Re:That's nice, but... by HumanWiki · · Score: 1

      Which would still require Telnet to be enabled.

      Which isn't anywhere as farfetched as you'd think.

  4. Who has switches with a public IP? by Anonymous Coward · · Score: 0

    In every place I've ever worked, they used 10/8 or 192.168/16 addresses.

    1. Re:Who has switches with a public IP? by sunderland56 · · Score: 3, Insightful

      Don't ever assume that all hacks are coming from the outside.

    2. Re:Who has switches with a public IP? by Anonymous Coward · · Score: 0

      You are absolutely correct, but that assumption blocks 99+% of the attacks so it is still valuable. Security isn't black and white. You do what you can. As Bruce Schneier said, "security is a process, not a product." Blocking a good portion of the attacks is a good part of the process.

    3. Re:Who has switches with a public IP? by silas_moeckel · · Score: 1

      Any sane configuration limits traffic to the routing gear. We have been able to programmatically generate configs forever it's not like it used to be with hand everything.

      --
      No sir I dont like it.
  5. Reasons to leave clustering enabled by skids · · Score: 1

    1) You are using proprietary multichassis bonding
    2) You need to make multiple switches look like one for licensing $$ purposes.

    And that is about it. Look at any vendor's release notes and a substantial portion of the bugs are in the clustering regime. Just turn that crap off unless you need it... since inductry-wide it's a proprietary lock-in gambit and doesn't have to survive interop shootouts, there's no way the code is worth running otherwise.

  6. Hardware view is obsolete by Tablizer · · Score: 1

    You can't treat such "hardware" as hardware anymore: it's a computer, which needs security updates like any other computer that's connected to a network.

    If there is not a realistic way to know about, get, and add security patches to ANY computer that connects to a network, don't buy it.

    1. Re:Hardware view is obsolete by Anonymous Coward · · Score: 0

      You can't treat such "hardware" as hardware anymore: it's a computer, which needs security updates like any other computer that's connected to a network.

      Ummm, seriously dude? That is your insightful statement?

      Cisco has been documenting flaws (and selling support contracts to fix flaws) for a looong time (decades).

    2. Re:Hardware view is obsolete by Tablizer · · Score: 1

      If MS charged directly for Windows security patches, they'd be flogged. Cisco's model is outdated.

    3. Re:Hardware view is obsolete by Anonymous Coward · · Score: 0

      If MS charged directly for Windows security patches, they'd be flogged. Cisco's model is outdated.

      For all of Cisco's flaws (and there are lots), Cisco does release security patches for free.

      You have to contact Cisco and ask though, which is very annoying.

      Oddly enough, if you call Cisco for one of these free updates, they don't even try to upsell you to a service contract.

    4. Re:Hardware view is obsolete by Anonymous Coward · · Score: 0

      I've managed cisco equipment since 1988, and I have never seen them charge for a security-related update. I've gotten hundreds of free software updates from them. Just mention a security problem and you'll get great support from TAC and free upgrades. They're not as bad as HP or Microsoft that require you to pay money for security updates.

    5. Re:Hardware view is obsolete by Tablizer · · Score: 1

      The other poster said "and selling support contracts to fix flaws". So which is it? Are some flaws fixed for free and others charged for?

    6. Re:Hardware view is obsolete by Anonymous Coward · · Score: 0

      The other poster said "and selling support contracts to fix flaws". So which is it? Are some flaws fixed for free and others charged for?

      Cisco sells support contracts, which means they will fix (and configure) routers for you. You also get new features with new software.

      But if you know what you are doing and only need the security fixes, then you don't need a support contract from cisco.

    7. Re: Hardware view is obsolete by Anonymous Coward · · Score: 0

      If I don't need a contract with them, free or otherwise, where is the cisco.com hosted link that let's me download these free updates?

    8. Re: Hardware view is obsolete by Anonymous Coward · · Score: 0

      Just ask the Nigerian Prince. He's always delivered for me.

    9. Re: Hardware view is obsolete by Anonymous Coward · · Score: 0

      Call them up, they'll be happy to provide a link for you. You simply need to cite a security reason to update, without a workaround being possible.

    10. Re:Hardware view is obsolete by Anonymous Coward · · Score: 0

      Cisco gives out their security patches for free. It's the service patches that you have to pay for.

    11. Re: Hardware view is obsolete by Tablizer · · Score: 1

      Call them up, they'll be happy to provide a link for you. You simply need to cite a security reason to update, without a workaround being possible.

      Let me get this straight: you need to supply a security reason to get security updates? What's an example "workaround"? Would it be like, "Nevermind, I caught the Nigerian Prince in a giant spring-loaded net. We're good."
         

  7. Another demonstration of why users need control by Anonymous Coward · · Score: 0

    While having a complete set of code to ones device is not an absolute certainty to security it is a basic foundation necessary to being reasonably assured your devices are in your control and not somebody else’s. Sadly with products like this there is little incentive outside of the home / consumer router market to release the source code such that the community is able to analyse the code itself. There is another problem in the technology sphere of technology changing too fast for proper security reviews and proper coding in general. I'd probably say we should be utilizing 20 year old router technology. The reality is without the standardization and use of chipsets long term we can't hope to properly review and improve the code to a quality that is half decent- given the amount of technology and code that has to be reviewed in the technology sphere in general.

    If you don't believe in copy"right" or "intelectual property" and support privacy/encryption/security/decentralization/etc and most of all you support liberty and freedom you should check out Somaliafest 2017: https://www.somaliafest.com/ Another event and group led by a migration of principled libertarians and voluntaryists to New Hampshire with the aim of forming a free society. Similar to the Free State Project this event differs in that it heavily focuses more on areas of technology and freedom. Porcfest also immediately follows the event on the same camp ground. So many participants and vendors are planning to attend both events.

    1. Re:Another demonstration of why users need control by skids · · Score: 1

      I'd probably say we should be utilizing 20 year old router technology.

      That would be a security mistake... a lot of essential security features are younger than that. Heck, there are some switches that old where the only option for administration is through telnet. Switches that old (or new switches not properly configured, or anything in the prosumer market or lower) are pretty much an open killing field for intruders to forge, intercept, and bypass traffic.

      The problem with open-sourcing these things is price and operating costs... open designs for the hardware would have to be mass-producible at the same price point as vendors have managed to achieve, and since they handle transit traffic, without open hardware, anything could be in that silicon to inject watermark CnC in packet headers or transmit timing.

      So you have to be pretty damn cash-flush to spy-proof your access network... otherwise you just have to hope whoever can own your net doesn't want to and is competent enough to keep the house keys hidden from others that would.

  8. wikileaks delivers by Anonymous Coward · · Score: 0

    From TFA:

    "Motherboard reported that WikiLeaks has yet to provide details of the security flaws to the companies in question. "

    Ha. Guess Motherboard either didn't talk to Cisco, or Cisco didn't tell them anything, or Cisco lied waiting until they published their advisory. In any case, Motherboard's attempt to paint Wikileaks as "extorting" the companies is completely false, or fake, if you will.

    "'Fortunately, WikiLeaks' Vault7 has permitted Cisco's security team to identity the vulnerability without releasing the exploit code. Cisco was the most proactive of the US manufactures and its security team initiated contact with WikiLeaks last week,' said the spokesperson."

    Good for Cisco for getting on top of this and protecting their customers. Now, why the fuck is Microsoft, Google, Apple dragging their heels about protecting their customers?

    1. Re:wikileaks delivers by Anonymous Coward · · Score: 0

      I was under the impression all Cisco network equipment always diverted to an NSA warehouse to be backdoored prior to shipment to final destination minus any markings to reveal the diversion nor tampering.

    2. Re:wikileaks delivers by Anonymous Coward · · Score: 0

      All? Uh, no. Here's an article from Ars Technica talking about TAO package interception.
      https://arstechnica.com/tech-policy/2014/05/photos-of-an-nsa-upgrade-factory-show-cisco-router-getting-implant/

      Here’s how it works: shipments of computer network devices (servers, routers, etc,) being delivered to our targets throughout the world are intercepted. Next, they are redirected to a secret location where Tailored Access Operations/Access Operations (AO-S326) employees, with the support of the Remote Operations Center (S321), enable the installation of beacon implants directly into our targets’ electronic devices. These devices are then re-packaged and placed back into transit to the original destination. All of this happens with the support of Intelligence Community partners and the technical wizards in TAO.

      The big name delivery services are thought to be set up to work with federal government IC to allow for interception of packages and re-transit.

    3. Re:wikileaks delivers by AHuxley · · Score: 2

      Re: "warehouse to be backdoored prior to shipment to final destination"
      Tailored Access Operations (TAO)
      "Photos of an NSA “upgrade” factory show Cisco router getting implant" (5/15/2014)
      https://arstechnica.com/tech-p...
      GCHQ, NSA, CIA have different ideas on what they want and why.

      In some nations the NSA might be working with a national telco over decades. So it is safe for the NSA to use a that nations gov staff as they more loyal to the NSA than their own nation over generations.
      In other nations the telco network might still be staffed with people who are totally loyal to their own nation. So that big dump of data back to a domestic staging server network might be detected. Code litter from another nations malware is left to fool any contractors or other gov investigators.
      Other methods are needed.
      The CIA might have a trusted local person sneak into a building under the cover of been new staff, a friend or more than a new friend to a long term staff member. Physical access gets past any network security and trusted devices can be altered on site and data collected by a person later on site. No internet link needed but physical device access is needed to alter code and then collect the result. No code litter is found.
      Or just send a command to a US brand's hardware and collect it all with the internet.
      Different methods for different nations and if staff are still loyal to their own nation.

      --
      Domestic spying is now "Benign Information Gathering"
  9. Unfixed Vault 7 vulnerablities... by slashkitty · · Score: 2

    So, this leads to many questions: How long did the CIA know about this flaw and not tell Cisco Or, did Cisco know about this flaw and not warm users. How many other unpatched flaws are in the Vault 7 Is Cisco no issuing a REAL fix for this?

    --
    -- these are only opinions and they might not be mine.
    1. Re:Unfixed Vault 7 vulnerablities... by guruevi · · Score: 2

      From the synopsis it does seem like Cisco is not providing a fix for this issue, only a "potential" workaround (meaning they baked it in and there are other methods of exploiting the same issue).

      --
      Custom electronics and digital signage for your business: www.evcircuits.com
    2. Re:Unfixed Vault 7 vulnerablities... by Anonymous Coward · · Score: 1

      >From the synopsis it does seem like Cisco is not providing a fix for this issue,

      Yeah, that's why commenting on the information gleaned from TFS is stupid.

      https://tools.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-20170317-cmp

      "Cisco will release software updates that address this vulnerability. There are no workarounds that address this vulnerability. "

    3. Re:Unfixed Vault 7 vulnerablities... by AHuxley · · Score: 2

      Re "How long did the CIA know about this flaw"
      The US goes down a list of flaw questions.
      Is the US the only one using the same issue? Will other nations find it soon?
      Are other groups in the wild using it now? Will AV software detect the flaw soon?
      Can it be used against the USA if discovered without been noticed?
      Will the USA be detected in a later code review or from code litter?
      Can the flaw be proved to be the work of another nation when the US uses the same method?
      After all that is worked out, the USA will keep the flaw or find some way to get it fixed if it is a risk to the USA.

      Re "How many other unpatched flaws are in the Vault 7"
      That depends on the US and its public budget for its clandestine services per year and the cost per flaw created or found? How much can be coded for or created for the US clandestine services per year per budget?
      100 well crafted methods? To cover a year of changing consumer, prosumer and professional product lines globally of all brands the US has interest in?
      Other methods need physical access to place methods and or physical access to collect the resulting data.
      Create too many really unique methods in the wild and many groups start noticing the flow of data and the cost of nation funded staging servers.
      Too much expert code litter starts to point to national funding. Loss of methods to other nations, cults, faith groups, other nations trusted police, "trusted" NATO or EU nations, criminals using the same methods later might also keep the flaw count down per year. The US likes to track who got their code later and is using it and how it leaked.
      If not a lot of other nations, groups would be using the same methods back in the USA for their own political or national advantage.
      Other "trusted" nations might leak to the press and interesting nations then stop using that US crypto or US hardware. Low count, good quality that collects all.

      --
      Domestic spying is now "Benign Information Gathering"
  10. Welcome to Cisco by Sycraft-fu · · Score: 2

    Where telnet is still a thing, and last I checked was on by default.

    1. Re:Welcome to Cisco by drinkypoo · · Score: 1

      How about "Welcome to Cisco, Where security was never a thing, and we always insert back doors." I mean, if you want to be accurate.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
  11. Something to think about. by jondeanmack · · Score: 0

    There seems to be a case for some free software that blocks fake news based on the users basic input. For example, I have no children and will never have a child or children. A child born from a thief is in possession of stolen property. Every now and then a fake website pops up with a news story like "Are your teens strung out on tech?" which is obviously fake. Rhetorically, Are you going to die and leave the computers contents with your fake news? It's a bit like running a Nuclear Power station and leaving it to melt down by not shutting it down before dying.

  12. Only on shitty networks. by Lumpy · · Score: 0

    If your switch has it's administration ports open out to the internet or to anything but a protected LAN, then you need to fire everyone in IT and hire competent people.

    --
    Do not look at laser with remaining good eye.
    1. Re:Only on shitty networks. by Anonymous Coward · · Score: 0

      It seems some of the really, really, REALLY shitty IT people have mod points today. Lumpy is actually very correct, if your management VLAN is not very protected you absolutely should fire all of IT and start over with competent people.

    2. Re:Only on shitty networks. by Anonymous Coward · · Score: 0

      Wow.

      You are correct, sir. Arrogant as Hell but correct.

      My corporation buys up other corporations as an operational strategy. It's just part of the world as far as we are concerned. Last year, for instance, we bought two national corporations. N-A-T-I-O-N-A-L.

      This leave us in the position of meshing multiple-multiple (or many-lots if you like Pratchett) networks into ours on a monthly basis, and while we would all love to work in a perfect world, most of us realize we live in the real world and need to deal with what we are given. Not every corporation we buy has an unfettered IT budget and neither do we (that's sarcasm, son). The corporation buys, the companies merge, I.T. deals with it, and we all move on.

      In a perfect world we would replace old equipment and fix every security problem, but this is not a perfect world. We do what we can with what we have. That's it.

  13. Only 300 switches? by Anonymous Coward · · Score: 0

    "More than 300 switches are affected by the vulnerability"

    Is that 300 devices or 300 models?

    Maybe it's Nintendo Switches.

  14. Yay...another CISCO security flaw by Anonymous Coward · · Score: 0

    Good lord...it's like something horrifying every two weeks with this company.

  15. It's an *intentional* flaw by Anonymous Coward · · Score: 0

    Make no mistake, this was an intentional flaw designed specifically by Cisco's Chinese firmware house to give the Chinese government access to American networks. Of the products affected, most are -M series used in Military networks in the US.

  16. What? by Anonymous Coward · · Score: 0

    What about:

    The non-blocking inter-switch speed without sacrificing a single port?
    The ease of management?
    The stack resiliency?

    I'm a huge fan of the technology and licensing is not an issue of any kink. There is literally no licensing cot to enable or disable clustering. There's a stacking cable, but that's it.

    What I'm trying to say, is that you're mad as a hatter with your conspiracy theory.

    1. Re:What? by skids · · Score: 1

      I have no conspiracy theory, just a disdain for switch clustering suites. If you're talking about the vendor lock-in point, ask an SE where a standards-based inter-vendor clustering suite is on the company/industry roadmap. It's just a de-facto reality.

      I haven't seen many switches lately that have a separate backplane cable for clustering. They all use their uplinks, since it only took vendors a decade or two to get cluster management packets adequately prioritized.

      On ease of management I'll give you one more item: if the cluster supports hitless upgrading that's not doable through other means, and if your SLA doesn't leave you any windows that's an attractive feature. So three, three good reasons.

      But unless you have only one cluster you're dealing with multiple CLI/SNMP/SDN endpoints anyway, so you might as well start automating, there will only be more over time.

      "Stack resiliency" really is only applicable to HPC, and in that case you'll be using #1 from my original list anyway. The MTBF on these things is so low these days that for most purposes you are past the point of diminishing returns on any other level of reliability.

  17. Not on by default by l0n3s0m3phr34k · · Score: 1

    On the new 2960X's we just bought, it is NOT on by default. You have to go into a second tab during your express setup and purposely enable it.

    1. Re:Not on by default by acoustix · · Score: 1

      I can't think of *ANY* Cisco switch that had telnet enabled by default.

      --
      "A plan fiendishly clever in its intricacies"- Homer Simpson
  18. How to fix this by AHuxley · · Score: 2

    Keep your brand or company secure by:
    Keep your most advanced work and secrets away from any network.
    Only use advanced US networks, US products for work that is in use and in public.
    When new services, products, contracts are been considered don't store anything on servers, network facing hardware.
    Hold design meetings in secure areas, don't bring in smart phones, devices. Keep vital encrypted notes on paper in that secure room.
    Use a one time pad to send vital messages to distant staff. Use staff to move a message to staff globally, face to face, in person.
    Use a networked company message board as a numbers station to broadcast information globally. Everyone looks at it everyday but the message is only for one person.
    If you have the funding set up bait, a honey pot of digital ideas on US branded hardware that faces the internet as normal.
    Pack it with the most amazing new ideas your competitors had, renamed as your own emerging products. Patents, secret bank accounts, staff lists, work with other nations. Make that server amazing. Use very different code names for emerging products and projects. See if anyone comes looking later for the same junk words or for the staff that are internal security risks on lists that are fake.
    Set up a random safe house with trusted security teams for years based on that staff risk review. See if anyone tries to offer the fake staff member a new job, wants to be "friends", makes a cash offer or poses as your nations security services to do an interview...
    Really simple counterintelligence that any nation or company can create.
    That needs a lot of funding but protects against human and network methods.
    Be aware of any new staff from other nations or your own nations new staff. New "friends" wanting a secure site tour. Physical site access can plant malware thats then collected later by hand.

    --
    Domestic spying is now "Benign Information Gathering"
  19. CIA + Russia by Anonymous Coward · · Score: 0

    These hacks were released when they weren't so useful. Probably from Assanges Russian government friends, since they seem to be a package from the same group.

    So the consequence of CIA not telling CISCO to fix it, is that every network using these CISCO routers is potentially backdoored by Russia at this point.

    How many election systems? How many business secrets? How many weapons manufacturers? How many politicians emails? How many booking sites? Banking sites? Press computers?

    That's just the primary attack, what about secondary? How many computers compromised that are used to develop smartphone apps, or other apps that then are compromised. Juniper had this, a source control system that was compromised and in turn allowed injection of malicious software into their routers, which in turn left holes in their customers systems.

    The CIA thought it would only be themselves who would exploit it, and America got owned and so now everyone got owned.

  20. Buy Ericsson or Huawei instead by Anonymous Coward · · Score: 0

    Ericsson in particular are known for quality, reliability, and security.