Slashdot Mirror


Cisco Removed Its Seventh Backdoor Account This Year, and That's a Good Thing (zdnet.com)

An anonymous reader quotes a report from ZDNet: Cisco, the world's leading provider of top networking equipment and enterprise software, has released today 15 security updates, including a fix for an issue that can be described as a backdoor account. This latest patch marks the seventh time this year when Cisco has removed a backdoor account from one of its products. Five of the seven backdoor accounts were discovered by Cisco's internal testers, with only CVE-2018-0329 and this month's CVE-2018-15439 being found by external security researchers. The company has been intentionally and regularly combing the source code of all of its software since December 2015, when it started a massive internal audit. Cisco started that process after security researchers found what looked to be an intentional backdoor in the source code of ScreenOS, the operating system of Juniper, one of Cisco's rivals.

Juniper suffered a massive reputational damage following the 2015 revelation, and this may secretly be the reason why Cisco has avoided using the term "backdoor account" all year for the seven "backdoor account" issues. Instead, Cisco opted for more complex wordings such as "undocumented, static user credentials for the default administrative account," or "the affected software enables a privileged user account without notifying administrators of the system." It is true that using such phrasings might make Cisco look disingenuous, but let's not forget that Cisco has been ferreting these backdoor accounts mainly on its own, and has been trying to fix them without scaring customers or impacting its own stock price along the way.

102 comments

  1. the number of backdoor accounts. by Anonymous Coward · · Score: 2

    seven down so many more to go.

    1. Re:the number of backdoor accounts. by Anonymous Coward · · Score: 2, Interesting

      Backdoors don't just magically appear on their own. Someone at Cisco had to put them there. Someone at Cisco had to be told to put them there. It is impossible that Cisco didn't know these backdoors were there.

    2. Re:the number of backdoor accounts. by Narcocide · · Score: 1

      Well, unlikely but not completely impossible. Of course, if they really didn't already know, that actually says something far worse about them.

    3. Re:the number of backdoor accounts. by Anonymous Coward · · Score: 2, Insightful

      Well, unlikely but not completely impossible.

      So . . . you' re saying that code can just magically appear somewhere, on it's own. Sorry, it just doesn't work that way. It doesn't happen accidentally, it doesn't happen magically all by it self.

      *SOMEONE* (most likely more than one person) had to make a deliberate decision
      *SOMEONE* had to create that backdoor and put it in there.
      *SOMEONE* (most likely more than one person) has known about it from day one.

      The *REAL* question is "How is it possible that Cisco doesn't know exactly who did it, when they did it, who authorized it, etc." This is trivial even on the shittiest version control system.

      *THAT* is incompetence at a truly epic level.

    4. Re: the number of backdoor accounts. by Anonymous Coward · · Score: 1

      As someone who has first hand knowledge, many of these are put there during development, by developers, on their own, and either leave them in by accident or on purpose for ease of future development and support. Debugging sucks, and having a hard-coded account at least makes it suck a little less.

    5. Re:the number of backdoor accounts. by Joce640k · · Score: 1

      It is impossible that Cisco didn't know these backdoors were there.

      You don't know that.

      Maybe the NSA is sending a continuous stream of people to apply for jobs at CISCO and put back doors into the code.

      --
      No sig today...
    6. Re:the number of backdoor accounts. by Joce640k · · Score: 2

      The *REAL* question is "How is it possible that Cisco doesn't know exactly who did it, when they did it, who authorized it, etc." This is trivial even on the shittiest version control system.

      *THAT* is incompetence at a truly epic level.

      Not if somebody's messing with the version control, impersonating other users, etc.

      Or maybe it's somebody at management level.

      --
      No sig today...
    7. Re:the number of backdoor accounts. by Anonymous Coward · · Score: 0

      In your scenario, anybody NEW to Cisco could have full reign on the source? Very interesting. So why hasn't Juniper/Alcatel/HP not sent someone there to hose that system? Seems like easy to do and we know PHB's would find that perfectly feasible. ;)

    8. Re: the number of backdoor accounts. by Anonymous Coward · · Score: 1

      Debugging sucks, and having a hard-coded account at least makes it suck a little less.

      If you let that slip out into the real world, you suck a whole lot and have no business being in the industry.

      If your management/security team is allowing this, they also have no business in the industry.

      Cisco makes core infrastructure for people's network that directly impacts security. If they're putting products out into the wild with hard-coded accounts, they're not to be trusted -- they're certainly not to be praised for removing them.

      I've been a developer, and if I'd left a backdoor in my software to make testing easier, someone would have cut my balls off.

      Lazy developers who introduce security holes with backdoors are dangerous to have around. I wouldn't have them on my team.

    9. Re:the number of backdoor accounts. by Anonymous Coward · · Score: 1

      They send a continuous stream of court orders to a small number of people in the company. The details of how these things get done were present in the NSA leaks a couple of years ago.

    10. Re:the number of backdoor accounts. by Anonymous Coward · · Score: 1

      Well, no, programmers under pressure, trying to connect with an authentication service that is either not present yet, or needs so much fucking around with to set up, that it's easy for a 'oh just get it so it responds instantly with a superuser token if they use testing123456 as a password, otherwise call the real service, and we'll just remember to change it back before we ship...' attitude to develop.

    11. Re:the number of backdoor accounts. by gweihir · · Score: 1

      Seven. Incredible. Other systems with really bad security have one.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    12. Re:the number of backdoor accounts. by gweihir · · Score: 1

      With one, yes. With two, maybe. With 7, definitely foul play, no other explanation.

      --
      Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
    13. Re: the number of backdoor accounts. by Anonymous Coward · · Score: 0

      I've been a developer, and if I'd left a backdoor in my software to make testing easier, someone would have cut my balls off.

      But if you have no balls left (or not have one in the first place)? :P

    14. Re:the number of backdoor accounts. by quintus_horatius · · Score: 1

      Cisco knew they were there, and knows how many more are present. But they can't just go and remove them all today. They have to clear each one with the people that wanted the backdoors there in the first place.

  2. Fuck Off by Kunedog · · Score: 1, Offtopic

    Leave your value judgement out of the headline.

    1. Re: Fuck Off by Anonymous Coward · · Score: 0

      Well, you see, its complicated and thatâ(TM)s a good thing. What is complicated, you are certain to ask? Well, my gender of course.

    2. Re:Fuck Off by Anonymous Coward · · Score: 0

      You like it in the backdoor eh? I guess we knew that.

    3. Re:Fuck Off by Anonymous Coward · · Score: 0

      Media headlines are pure propaganda. They are useless without an effort to influence the reader.

  3. A good thing by alvinrod · · Score: 4, Funny

    It's a good thing the headline pointed out that it was a good thing. I'd never be able to have figured it out for myself if I hadn't been told. Now could someone please tell me what products to consume?

    1. Re:A good thing by Anonymous Coward · · Score: 0

      Cisco[tm][r] cloud products, of course. With the really really expensive support contracts, like all the other Cisco[tm][r] products, but the added benefit they stop working once you stop paying for your Cisco[tm][r] cloud product cloud subscription. Because cloud!

      In other news, it's clear why beauhd likes zdnet so much. Thinking is hard! For beauhd.

      Me, I think this is Cisco[tm][r] catching up after years of (wilful) neglect. "A good thing", eh, if you'd want to call it that. They deserve to be dinged for their earlier negligence. But then, too many people don't really take their favourite vendors to task for their failings, allowing this sort of bullshit to fester.

    2. Re:A good thing by sjames · · Score: 1

      I suppose it's good in the same sense that a serial killer pledging to murder less people this year is good news...

    3. Re:A good thing by sabbede · · Score: 1

      I'll send you my Christmas list.

  4. updates $100/mo per device by Joe_Dragon · · Score: 2

    updates $100/mo per device

    1. Re:updates $100/mo per device by Anonymous Coward · · Score: 0

      Every other vendor has free security updates, cisco instead makes you pay for mistakes made by them.

    2. Re:updates $100/mo per device by Anonymous Coward · · Score: 0

      updates $100/mo per device

      Paid updates that add security holes to the product? Most likely.

      Cisco should fire all of it's overseas (i,e, "India") programmers so that USA & European programmers can do more secure work.

      Cisco is being paid, after all, for it's updates so why not use the best programmers out there.

    3. Re:updates $100/mo per device by q4Fry · · Score: 1

      It's this, except at the org-level?

  5. good thing? pigs arse it is by bloodhawk · · Score: 1

    The fact they have to search for and find the backdoors after the fact means they have broken internal security coding review processes. These should never be getting to the stage where they can be found in this fashion,.

    1. Re:good thing? pigs arse it is by jonwil · · Score: 4, Interesting

      Any hardware manufacturer that allows backdoors to even end up in a shipping device clearly has something wrong with the way they do software development. And when they do find things like this, they need to backtrack via version control and see who allowed this crap to happen (in terms of the developer and the all the different levels of people who were supposed to review that developers code before it got out there) and give the people who allowed it to happen or should have caught it a good talking to so the people involved change the way they do things so it cant happen again.

      Then again, given what Snowden has told us, all these backdoors in all these internet connected things may well be intentional and only closed or covered up when someone not sworn to secrecy finds one...

    2. Re:good thing? pigs arse it is by postbigbang · · Score: 2

      Yep. It means a smashed QA process.

      But no one will fall on their swords. More will be found. No necks hung from a yard arm, even though the backdoors are probably known.

      Were they inserted at the request of intelligence agencies? We'll never know. However, this is my suspicion. There is a great hunger for such things among the spooks.

      --
      ---- Teach Peace. It's Cheaper Than War.
    3. Re:good thing? pigs arse it is by Pinky's+Brain · · Score: 1

      They don't like cooperating either, so you get one backdoor per agency.

    4. Re:good thing? pigs arse it is by rtb61 · · Score: 1, Offtopic

      Now guess what the back doors were used for, hmm, corporate environment, the home of insatiably greedy psychopaths, perhaps more than just a little insider trading. The SEC rightfully should investigate with the FBI, to see who did the back dooring and how those back doors were used, insider trading by far the most profitable way to use them, especially widely distributed back doors, billions to be made. Talk about failing to disclose stuff that would have a significant impact on share value, two reasons to investigate but I suppose no hedge fund manager is paying a lobbyists to chat with SEC political appointees (CISCO competitors, honestly you people are a bit slow).

      --
      Chaos - everything, everywhere, everywhen
    5. Re:good thing? pigs arse it is by Anonymous Coward · · Score: 0

      https://www.asd.gov.au/infosec/epl/

      Ha ha - they put one over the Australian Security. How do they live down the shame. Reputational damage.

    6. Re:good thing? pigs arse it is by Interfacer · · Score: 2

      I suspect this is not just a matter of adding admin accounts with a fixed password.

      I manage a large production control system in a pharma plant. The software is from a well known vendor (in that industry) and comes with a lot of certifications. There are no hard coded user accounts, though there are privileged accounts that I know the password of because I set them up. But regardless of the fact that I know those passwords, this is an enormous pile of software comprised of services, user applications, scripting engines, background process, etc, and different parts of the software are running distributed over 15 different servers. As a collection, some of that software is 30 years old and cobbled together from lots of pieces from lots of different sources.

      I come from a software developer background, doing mostly kernel level work, interprocess communication, software infrastructure etc. When I look at the pile of software I have been managing for over a decade now, I see many ways to abuse running services or schedulers, and making do things they are not supposed to.

      Not because I can 'log in' as a service account, but because I know for example that one of those privileged accounts is getting information from some place in order to determine what to do, and because of an oversight or bug, I can affect the information telling that account what to do. Due to less than perfect design (or possibly because of legacy software that cannot easily be changed) I could piggy back a script or executable on top of something else and have that executed in a privileged manner.

      So I really think that this is not so much a cisco developer adding in privileged accounts. After all that would be trivial enough to find in code audits. But it is much more likely that there are ways to influence what a privileged process inside the cisco system is doing. The term 'backdoor' implies a much bolder and intentional issue, which I really don't think is going on here.

      And since Cisco has developers who are very much at home in their own software, it doesn't really surprise me that they can look at their own code, and figure out things that may have unexpected vulnerabilities.

    7. Re:good thing? pigs arse it is by Joce640k · · Score: 2

      Any hardware manufacturer that allows backdoors to even end up in a shipping device clearly has something wrong with the way they do software development.

      Either that, or... enemies working inside the company.

      --
      No sig today...
    8. Re:good thing? pigs arse it is by Joce640k · · Score: 2

      I suspect this is not just a matter of adding admin accounts with a fixed password.

      It won't be as simple as "cat /etc/passwd", no.

      --
      No sig today...
    9. Re:good thing? pigs arse it is by drinkypoo · · Score: 1

      Were they inserted at the request of intelligence agencies? We'll never know. However, this is my suspicion. There is a great hunger for such things among the spooks.

      Further, the only safe assumption is that they were intentionally placed there to be used, because if you don't follow that assumption you may miss something. Everyone who has any Cisco gear anywhere in their network should be especially diligent about assuming that the communications equipment can be compromised.

      --
      "You're right," Fisheye says. "I should have set it on 'whip' or 'chop.'"
    10. Re:good thing? pigs arse it is by cellocgw · · Score: 1

      I suspect this is not just a matter of adding admin accounts with a fixed password.

      It won't be as simple as "cat /etc/passwd", no.

      You bet it won't be. It'll take
        %% cat >> /etc/passwd stopthisnonsense
      %% usr:galacticoverlord
      %% passwd: root
      %% stopthisnonsense

      --
      https://app.box.com/WitthoftResume Code: https://github.com/cellocgw
  6. A good thing? by Anonymous Coward · · Score: 0

    A good thing that:

    They removed this backdoor account?
    They removed 7 this year?
    There were only 7 this year?
    They didn't find all the others?

    1. Re:A good thing? by Anonymous Coward · · Score: 0

      all of the above.

  7. And we're surprised, uh, why? by NoNonAlphaCharsHere · · Score: 3, Funny

    So you're saying you're surprised a company named Crisco has a lot of backdoor accounts?

    1. Re:And we're surprised, uh, why? by Anonymous Coward · · Score: 0

      Aw common - this should get a 'funny" flag, or was it a giant WHOOSH?

  8. support contracts required to get updates by QuesarVII · · Score: 2

    Cisco requires you to pay for a support contract (yearly) to have access to the updates for a switch when they already charged 3x what it's worth to begin with.

    I don't know how that's even legal when you have big security holes like this. The product is not fit for use, yet you have to pay even more $ to make it "safe" again.

    1. Re:support contracts required to get updates by Anonymous Coward · · Score: 0

      Large companies will pay any price to be abused by big names like Cisco, Oracle, and IBM... initially successful vendors that have been cost-cutting and coasting on their reputations for a long time. You'd think reality would eventually catch up to them, but I guess you can't overestimate the gullibility of the non-technical management who are writing the checks.

    2. Re:support contracts required to get updates by Moskit · · Score: 2
      There is a separate upgrade policy for security breaches. Cisco offered a free software upgrade for a number of such issues.

      https://tools.cisco.com/securi...

      As a special customer service, and to improve the overall security of the Internet, Cisco may offer customers free software updates to address high-severity security problems. The decision to provide free software updates is made on a case-by-case basis. Refer to the Cisco security publication for details. Free software updates will typically be limited to Critical and High severity Cisco Security Advisories.

      Sample security advisory:

      https://tools.cisco.com/securi...

      Cisco has released free software updates that address the vulnerability described in this advisory. Customers may only install and expect support for software versions and feature sets for which they have purchased a license.

      They do a reasonable thing on support side by the look of it.

    3. Re:support contracts required to get updates by Anonymous Coward · · Score: 0

      >for a switch when they already charged 3x what it's worth to begin with.

      This is false by default. If they charged x, and you paid x, it was worth x.

    4. Re:support contracts required to get updates by Anonymous Coward · · Score: 1

      There was a time when I tried getting those "free" updates. Cisco support didn't know how to provide them and couldn't even read the policy on the Cisco website.

      That was the day I stopped buying anything from Cisco.

    5. Re: support contracts required to get updates by Anonymous Coward · · Score: 1

      The fact that Cisco can con c-level executives into buying their crap at highly inflated prices does not mean the engineers that are then forced to set it up believe for one second that it possesses such value.

  9. Took a Shit in the Pool by Anonymous Coward · · Score: 0

    It is true that using such phrasings might make Cisco look disingenuous, but let's not forget that Cisco has been ferreting these backdoor accounts mainly on its own, and has been trying to fix them without scaring customers or impacting its own stock price along the way.

    Cisco has been taking long-term processing dumps in the pool. Cisco has been floating high-fiber, non-flushing matter in the pool. Cisco has been using a scoop meant for cleaning up after dogs but used on humans and then dumping them in the pool. It's all a good thing because no matter how much you swallowed, the pool was heavily chlorinated through Cisco efforts and Cisco made sure people kept on coming in the water because they weren't scare about all the brown floating human byproduct.

  10. I beat my wife 65% less , and that's a good thing. by king+neckbeard · · Score: 5, Insightful

    Yes, the direction the code is moving in is an improvement, but that's not good, that's less awful. But the fact that there were seven backdoor accounts to remove is a huge problem.

    --
    This is my signature. There are many like it, but this one is mine.
  11. How ridiculous by enrique556 · · Score: 1

    Does cisco hardware not run on open source software? If not, this would be a great time for open source pundits to start jumping up and down and waving their hands around.
    Intel seems to have the same critical mental disability when it comes to *not* putting gaping, obvious security holes in the closed source of its firmware, so from here it's pretty obvious that even the biggest, most reputable hardware companies cannot be trusted with this task.
    If I was a Cisco customer I'd be calling up my "account manager" and asking them if they got any of them open source based routers and if not, we'll get our routers somewhere else.

    1. Re:How ridiculous by Anonymous Coward · · Score: 0

      Does cisco hardware not run on open source software? If not, this would be a great time for open source pundits to start jumping up and down and waving their hands around.
      Intel seems to have the same critical mental disability when it comes to *not* putting gaping, obvious security holes in the closed source of its firmware, so from here it's pretty obvious that even the biggest, most reputable hardware companies cannot be trusted with this task.
      If I was a Cisco customer I'd be calling up my "account manager" and asking them if they got any of them open source based routers and if not, we'll get our routers somewhere else.

      Cisco products may have some basis in open source code, but you will never get the actual source code from Cisco. Never. NEVER.

      Buy your routers somewhere else.

      Cisco products are overpiced underperforming piles of scrap that are endlessly hyped by their employees as being the greatest thing since sliced cheese.

      magicword: militant

    2. Re:How ridiculous by Anonymous Coward · · Score: 1

      Until 5 or so years ago, Cisco products primarily ran on VxWorks. After some acquisitions an other alignments, they began using Linux. In general, IOS runs on VxWorks while IOS XE runs on Linux. I don't know when the transition for firewalls took place. I'm fairly certain FTD runs on Linux while PIX and possibly ASA run on VxWorks. A lot of telecom equipment was deployed running VxWorks.

    3. Re: How ridiculous by Anonymous Coward · · Score: 0

      Cisco maintains a cult of followers much in the same way that Apple does. Objectivity leaves the building when talking about their precious brands....

  12. And that's a good thing by Anonymous Coward · · Score: 0

    Ohhhh /. What have you become

    1. Re:And that's a good thing by Anonymous Coward · · Score: 0

      irrelevant.

  13. Cisco good, Juniper bad by Anonymous Coward · · Score: 0

    Or thatâ(TM)s my take away from the summary

    1. Re: Cisco good, Juniper bad by Anonymous Coward · · Score: 1

      Ya, and ScreenOS isn't even a Juniper OS, it's a legacy OS they acquired when they bought NetScreen years ago. That entire product line was end of life long ago, SRX is Juniper's current firewall and runs JunOS.
      But when the ScreenOS vulnerability was found, Juniper dusted off the code, fixed it, and issued an update despite it having been ebd of support for quite some time.

  14. How many other governments had the by AHuxley · · Score: 1

    keys?

    --
    Domestic spying is now "Benign Information Gathering"
  15. Re: number of beauhd backdoor astroglide entries by Narcocide · · Score: 1

    Your racist ascii-art skills are garbage. What, did you auto generate those from a gif you saved in 1995 or something?

  16. , and That's a Good Thing! by Anonymous Coward · · Score: 0

    Thank you dear author for framing my emotions before processing your work.
    Thank you for empowering people who only read the title that what has happened is in fact... a good thing.

  17. Why? by LaughingRadish · · Score: 3, Insightful

    Would someone care to explain how these backdoors got in the code in the first place?

    1. Re:Why? by Anonymous Coward · · Score: 1

      I am sure it was done from the highest levels and passed QA just fine. You behave surprised when found out.

    2. Re:Why? by AmiMoJo · · Score: 3, Interesting

      Most seem to be simple support backdoors. Customers losing passwords and guys arriving on-site without the right info is a big problem for support, so they like backdoors.

      For support security is the enemy, it's something that makes their job harder. The customers don't really care about it, they just want stuff to work.

      --
      const int one = 65536; (Silvermoon, Texture.cs)
      SJW, n: "Someone I don't like, and by the way I'm a fuckwit" - AC
    3. Re:Why? by Moskit · · Score: 2

      It seems that programmers put hardcoded accounts for testing purposes and did not remove them from production code.

  18. I'm surprised... by Anonymous Coward · · Score: 2, Informative

    ... that there were only seven found and fixed this year.

    A search of the US-CERT vulnerability database turns up more than 300 hard-coded credential CVEs against Cisco since records were kept.

  19. Warranty of merchantability, fitness for purpose by raymorris · · Score: 3, Interesting

    The relevant legal term is "warranty of merchantability". It's an implied warranty that manufacturers cannot (successfully) disclaim. The warranty of merchantability essentially guarantees that the item is fit to sell. It doesn't guarantee the quality is better than cheaper brands, but it does warrant that the product is fit for the marketplace - that it properly suits the needs of some purchasers.

    I haven't done a deep dive on these particular Cisco accounts yet since I'm off work this week. At first blush, Cisco probably has a legal obligation to provide an update to fix this issue at no charge. Because it was never fit for sale, that needs to be fixed. If they choose to fix it with an update that also provides new features that's fine, but using the magic words "warranty of merchantability", preferably in a letter that sounds like it was written by a lawyer, should get you updates at no charge.

    In addition, Cisco provides a LOT of documentation about which of its products are suited for which purposes, and how to configure them for different purposes. I've read literally thousands of pages from Cisco myself. By stating, in writing, that this particular product is suited for this particular purpose, Cisco may have also created a "warranty of fitness for a particular purpose". When they say in writing that a particular ASA is designed to function as a VPN gateway for enterprises with 1,000-5,000 employees, that may legally create a warranty that it is in fact somewhat suitable for the purpose claimed. If these security issues make it not suitable for the advertised purpose, Cisco needs to fix that at no charge.

  20. Re: Cisco bad, Ubiquiti good by CranberryKing · · Score: 1

    Yes yes. Don't read the dribble.

  21. It's not a good thing. by Anonymous Coward · · Score: 0

    These problems have been known long enough that none should exist in any of their "mature" products. We are past the point where newly-discovered backdoors should be considered evidence of criminal negligence.

  22. Cisco E2500 debacle by Jerry · · Score: 1

    About a couple months after I purchased a Cisco E2500 WiFi, six or seven years ago, I got had a notice pop up on my screen asking me if I wanted to update the WiFi's firmware. It explained that in order to confirm the update I had to go to Cisco's cloud server and create an account. THEN, they would update the WiFi firmware. A search around the web at the time revealed that many folks who bought Cisco WiFi's received that notice and requirement. Some suggested that the NSA forced Cisco to update their firmware to include a backdoor. True or False? I don't know, but considering what Snowden blew the whistle on, it would be easy to believe it. That's when I decided to update my E2500 firmware with DD-WRT instead. In addition to being open sourced and more secure, it gave me access to features on the WiFi that Cisco's HTML interface would supply. My next and current WiFI also has DD-WRT firmware on it.

    --

    Running with Linux for over 20 years!

  23. Suck it China by Anonymous Coward · · Score: 0

    for putting your made up chips/devices to do some evil stuff one computer at a time..

  24. Re: number of beauhd backdoor astroglide entries by apparently · · Score: 1

    Okay, so you posted totally hip ASCII art of Trump's stupid fucking face, so what's your point exactly?

  25. A better question by Anonymous Coward · · Score: 0

    Would be what they're adding when they claim they're removing ...

  26. Cisco isn't flying with the angels. by Excelcia · · Score: 4, Interesting

    Backdoors don't just magically appear on their own. Someone at Cisco had to put them there. Someone at Cisco had to be told to put them there. It is impossible that Cisco didn't know these backdoors were there.

    Exactly. And as per Snowden's revelations years ago. Cisco was pointed to as purposefully backdooring its products at the behest of the NSA years ago, and today they are suddenly on the side of the angels because they have graciously patched out a few of them?

    Meanwhile, what has the NSA already installed on those systems through those backdoors? If they are getting patched out now, it's only because Cisco's keepers don't need it any more.

  27. How many new backdoors did they create though? by ayesnymous · · Score: 1

    Otherwise they'd be in breach of their agreements they have with the government.

    1. Re:How many new backdoors did they create though? by Anonymous Coward · · Score: 0

      The new ones are "buffer overflow bugs".

  28. Re:I beat my wife 65% less , and that's a good thi by Anonymous Coward · · Score: 1

    It's a complete abuse of trust, and it should be grounds for revoking the corporate charter.

  29. Seven Accounts? by Weirsbaski · · Score: 2

    Cisco removed seven backdoor accounts, huh? How many more are in there?

    That's not rhetorical- I'd really like to know.

    --

    I am not a sig.
    1. Re:Seven Accounts? by Moskit · · Score: 1

      They have thousands of products, running many different systems/codes. This is not seven backdoors in one product or one OS.
      Cisco also acquires a lot of companies - some of the past backdoors were disovered after internal Cisco check revealed them post acquisition.

    2. Re:Seven Accounts? by PPH · · Score: 1

      How many more are in there?

      I think that's all of them.

      --
      Have gnu, will travel.
  30. For every account they remove by Anonymous Coward · · Score: 0

    They probably add 2 more.

  31. Re:I beat my wife 65% less , and that's a good thi by DNS-and-BIND · · Score: 1

    And shitty comments like this are why nobody tries to get better. Why bother if all you're going to get is abuse? It's very telling you chose a feminist way of thinking about it. They are the champions of being toxic people and granting no credit for positive developments. It's one of the reasons they lost their way some time ago.

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!
  32. Suuure by Anonymous Coward · · Score: 0

    That explains all an no deeper investigations are required.

  33. Or better by Anonymous Coward · · Score: 0

    Encrypt everything, trust only an OpenBSD firewall. Never send anything in plaintext over a CISCO or Juniper product. And yeah, don't use OpenSSL. OpenSSL is a can of worms.

  34. Bingo by Anonymous Coward · · Score: 0

    That is why the Russians have their own CPU, Elbrus.

    The Chinese have Loongson.

    They use their own hardened Linux version or OpenBSD on these self-made CPUs.

    Never trust Intel out of Israel. That is where their digital design comes from.

    1. Re:Bingo by Anonymous Coward · · Score: 0

      What the fuck does this have to do with Intel? This has to do with Cisco being a giant knob and the fact that they're generally untrustworthy.

  35. Nah by Anonymous Coward · · Score: 0

    Their QA is a bunch of social scientists who cannot comprehend a single line of C code. That is what we must expect.

  36. At least it's not China... by Anonymous Coward · · Score: 0

    Oh wait America is far more incompetent.

  37. It won't change anything, U.S. equipment is unsafe by Anonymous Coward · · Score: 0

    that's just how it is, and it's thanks to America First mentality and your government agencies and their private courts who can order any telecom company to do anything they want.

    If you purchase U.S.-made communication equipment, then the U.S. government has a way into your systems. You should buy Ericsson, Huawei, or Nokia, they are among the ten largest manufacturers in the world, and their equipment has always stood up to scrutiny and inspection.

  38. good thing? by sad_ · · Score: 1

    fine, they are closing backdoors, which they put there themselves and aparently have a hard time finding.
    i just hope they are also educating their devs to never put in backdoors again, otherwise this will be a never ending story.

    --
    On a long enough timeline, the survival rate for everyone drops to zero.
  39. Re: number of beauhd backdoor astroglide entries by sabbede · · Score: 1

    Geez, fine, you're gay, we get it. Nobody cares.

  40. OpenBSD *is* well suited to firewalls by raymorris · · Score: 1

    I don't use OpenBSD anywhere else, but I agree it's particularly well suited to firewalls.

    At one point I set up a machine that did nothing but store credit card numbers. It wasn't a web server or a database server or anything else, it had a single function so that it could be stripped of most software (since software has bugs). That too would have been a good place to use OpenBSD.

    The one issue with that is because that's the only place I'd use OpenBSD, I'm not nearly as familiar with OpenBSD as I am with Linux. Using a system you don't know well to build a firewall on is also a bad idea, if you can instead use an operating system that you know inside and out.

  41. Re:I beat my wife 65% less , and that's a good thi by Anonymous Coward · · Score: 0

    And shitty comments like this are why nobody tries to get better. Why bother if all you're going to get is abuse?

    Cisco makes infrastructure which is tied into the lowest levels of the network. It's how people implement their damned security.

    Are you saying we should be praising Cisco for fixing security holes that anybody with any concept of network security should have never allowed to exist in the first place? There is no scenario in which engineers at Cisco couldn't be aware that hard-coded backdoor passwords were a security risk. Not if they are competent in any way.

    That's stupid, and is not unlike praising a car company for no longer making cars which burst into flames in an accident ... yes, it's good you've fixed that, but you never should have allowed it to happen in the first place. We also don't praise people who stop shitting on the floor.

    Cisco was grossly incompetent in allowing these back doors. They're fixing their own incompetence. But don't expect high praise for that.

  42. Re: I beat my wife 65% less , and that's a good th by Anonymous Coward · · Score: 0

    This. I favor complete dissolution of companies that systematically abuse the public trust. That definitely includes all of of the big ones whose incomes rival those of nation states.

  43. Fuck Cisco by sexconker · · Score: 1

    Fuck Cisco
    Fuck IBM
    Fuck Oracle

    If you EVER do business with these clowns, you will regret it.

  44. Re:I beat my wife 65% less , and that's a good thi by king+neckbeard · · Score: 1

    I gave them credit. They've moved to "less awful," a major upgrade from "OHGODOHGODKILLITWITHFIRE." They don't get to the point of actual praise until they can make it through at least a year without having to remove an account that should have never been available on an end-user product.

    --
    This is my signature. There are many like it, but this one is mine.
  45. There is nothing good about Cisco by gweihir · · Score: 1

    That is the only reasonable conclusion from this extreme level of insecurity. They probably have some of these seven that are actual screw-ups (very, very bad) and certainly some that were placed intentionally (even worse). The only valid conclusion is to not buy from them, as they are even too stupid to hide intentional backdoors well...

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  46. Re:I beat my wife 65% less , and that's a good thi by DNS-and-BIND · · Score: 1

    Are you a male feminist? You won't get laid that way, you know. It doesn't work.

    --
    Shutting down free speech with violence isn't fighting fascism. It IS fascism!