Slashdot Mirror


More on Last Year's Cisco Source Code Theft

grazzy writes "The New York Times has a story about last year's theft of Cisco source code: The incident seemed alarming enough: a breach of a Cisco Systems network in which an intruder seized programming instructions for many of the computers that control the flow of the Internet. "

56 of 266 comments (clear)

  1. Did they steal the editor too? by P3NIS_CLEAVER · · Score: 3, Funny

    What's a Thef????

    --
    Please sign petition to restore sanity to our banking system!!!

    http://financialpetition.org/
    1. Re:Did they steal the editor too? by Anonymous Coward · · Score: 2, Funny

      What's a Thef?

      A chef with a lisp?

    2. Re:Did they steal the editor too? by Anonymous Coward · · Score: 5, Funny

      Most amusing part to me is that the title was corrected but it still has "Years" instead of "Year's".

  2. Stakkato by natron+2.0 · · Score: 2, Interesting


    so now the hunt is on for the elusive stakkato...

  3. cmdr taco by mondoterrifico · · Score: 3, Funny

    Master of the ebonics.

  4. But on 24 they said cisco networks were by Anonymous Coward · · Score: 4, Funny

    self defending?????

  5. Question for an expert... by wcitech · · Score: 5, Interesting

    I'm without a doubt no networking expert, so I'd like to ask one of you who is: if the source code for cisco's equipment is leaked, would that person have the ability to create some kind of virus/malware that could bring the internet to a screaching halt? What can they do, infect routers with viruses now? I guess I'm unclear on the real dangers in a situation like this.

    1. Re:Question for an expert... by CaymanIslandCarpedie · · Score: 5, Funny

      No, that just makes it more secure sense more eyes will be looking at it ;-)

      --
      "reality has a well-known liberal bias" - Steven Colbert
    2. Re:Question for an expert... by Phil246 · · Score: 4, Insightful

      only if there are flaws in said code.

    3. Re:Question for an expert... by globalar · · Score: 2, Insightful

      No, likely not.

      1) Cisco IOS does not run the *whole* Internet. Different IOS versions apply as well.

      2) Revealed source code != massive untapped exploits.

      3) IOS doesn't have an execution environment with "open" interfaces like a desktop OS. Routers don't execute transport data or routing data. This means no script kiddies. There are of course other ways to crash a router.

      4) IOS is mature and (obviously) well tested. People have been throwing all sorts of strange things as Cisco routers for a long time now. Outside the main "train," any exploit would be a real chore to find.

    4. Re:Question for an expert... by lazlo · · Score: 2, Insightful
      3) IOS doesn't have an execution environment with "open" interfaces like a desktop OS. Routers don't execute transport data or routing data. This means no script kiddies. There are of course other ways to crash a router.


      I kinda wonder about this sometimes. As a for instance, here is an excellent example of how to write an SMTP client in the TCL shell included in recent IOS versions. Of course, getting the shell to start out with is left as an exercise to the reader, but routers operate more and more heavily on the data that passes through them and arrives at them. On a modern IOS router, you have a bunch of routing processes handling routing protocols, as you would expect, and then you've also got a telnet server, an ssh server, a couple of small tcp/udp services (if for who knows what reason you've decided to turn them on), snmp support, a web server with the capability of executing scripted code directly on the router... In short, there's a lot that's potentially explotiable there.

      Of course, I completely agree with your basic assertion that the leak of the source code isn't a particularly big deal, from a security standpoint. The best evidence of this, for me, is the fact that I don't feel at all insecure with the linux-based routers I use, and (sarcasm) I understand the source code to linux got leaked quite a while ago. (/sarcasm)

      --
      Pound! Bang! Bin! Bash! is this a shell script or a Batman comic?
    5. Re:Question for an expert... by dgatwood · · Score: 2, Interesting
      I'd be more worried about a timebomb. Somebody writes a worm that spreads to all the Cisco routers on the planet, then sits and waits until some specific time---say... the anniversary of the first movie theater opening---then thus down the IOS processors and locks the OS up in an endless reboot cycle.

      If somebody did something like that, it could basically bring the majority of the internet to a grinding halt. By anybody's book, this is a bad thing. Indeed, that's why I've been saying for so many years that we need more diversity on the Internet, that we depend way too much on Cisco and their systems, and that the Internet isn't nearly as reliable as we think....

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    6. Re:Question for an expert... by dgatwood · · Score: 2, Insightful
      True, but with the IOS code, a black hat might be able to do it in a way that wouldn't be as easily traceable as a packet flood or whatever. You know, like "generate a single UDP packet that is larger than n bytes with the byte sequence 'x y z a b c' at offset k" or whatever.

      IMHO, there are two models that work: tight security on source code and open source, the former because black hats have less tools to find security holes, the latter because the white hats vastly outnumber the black hats. Closed source that leaks is probably the worst of both worlds.

      --

      Check out my sci-fi/humor trilogy at PatriotsBooks.

    7. Re:Question for an expert... by Keruo · · Score: 2, Informative

      They didn't use holes in cisco routers to break into their network.

      They used stolen passwords gathered from other hacked machines by using trojaned sshd's.

      Says so in TFA.

      --
      There are no atheists when recovering from tape backup.
    8. Re:Question for an expert... by strikethree · · Score: 2, Insightful

      only if there are flaws in said code.

      which translates into: yes!

      --
      "Someone needs to talk to the tree of liberty about its ghoulish drinking problem." by ohnocitizen
  6. Heh by mattmentecky · · Score: 2, Funny

    Internet Attack Called Broad and Long Lasting by Investigators

    Thats about the only thing nerds/hackers are ever going to be doing that is described as "broad" and "long lasting".

  7. Doesn't make sense by afidel · · Score: 3, Interesting

    Cisco uses two factor one time passwords for remote access. I don't see how planting a trojaned copy of SSH on the lab computers would give the hacker access to Cisco's systems.

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    1. Re:Doesn't make sense by dr_dank · · Score: 2, Interesting

      From the tone of the article, it seems that a keylogger was used to grab passwords from a cisco user, which were then used from machines in that lab remotely exploited by an ssh rootkit.

      --
      Where does the school board find them and why do they keep sending them to ME?
    2. Re:Doesn't make sense by afidel · · Score: 2, Interesting

      Yes, but if things were working as they should have been a password logger doesn't do you ANY good. The password as entered by the user consists of two parts, the first part is their passphrase, which is like a traditional password, but the second part is a numeric sequence which is spat out by a numeric FOB which is synced to the master access server. These combined passwords must be entered within a narrow window, and once accepted are no longer valid. Someone must have f'd up big time to allow an internet accessible machine to bypass this very strong access mechanism.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
    3. Re:Doesn't make sense by rcw-home · · Score: 4, Interesting
      Cisco uses two factor one time passwords for remote access. I don't see how planting a trojaned copy of SSH on the lab computers would give the hacker access to Cisco's systems.

      I don't know how Cisco has their stuff set up, but it's easy to imagine such a breach playing out:

      1. Black hat replaces ssh client at University lab computer.
      2. Authorized but unwitting user uses University computer to VPN into Cisco's network and then uses the trojaned ssh client to connect to a computer on Cisco's network.
      3. The trojaned ssh client is now able to execute arbitrary code as the unwitting user on an internal Cisco computer. It uploads an executable to the internal Cisco computer that regularly makes outgoing TCP connections (they could even look like web browser traffic) to a computer under the black hat's control. The black hat sends control commands through these connections which the executable gladly obeys.
      4. The black hat is now free to scan the internal network to look for a host they can get root on, or hope that the user's account on the internal server they control will be used to connect to other internal systems, perhaps using more highly privileged accounts. (Any admins ever had to sit down at a users' computer and ssh into a server to fix something?) The longer the initial breakin is left unidentified, the better the chances of this occurring.
      5. Eventually the black hat will strike paydirt and get root on a system. From then on, the rootkit that the black hat installs can use any credentials anyone uses to access any systems remotely. Ssh into something? It can run commands on the remote host. Connect to a file server? It can replace executables that you have write access to and wait for someone else to run them.

      While an attacker would need a fairly deep understanding of the software infrastructure he is attacking and of the usage habits of the users there to pull this off, the same basic strategy is applicable to UNIX, Windows, anything. I remember reading several years ago that the breakins at Exodus and VA Linux happened this way.

      We're only used to the stuff we hear about not doing any real damage, because it's all dumb worms running without anyone at the controls. Just because we can fend off that stuff doesn't mean that someone with determination, knowledge, and patience won't get in and stay in.

    4. Re:Doesn't make sense by dr_dank · · Score: 2, Interesting

      Its not easy to pull off, but if you can enter the sequence before it expires, you can gain entry. IIRC, for the RSA SecurIDs, its 90 seconds.

      --
      Where does the school board find them and why do they keep sending them to ME?
    5. Re:Doesn't make sense by afidel · · Score: 2, Insightful

      Nope, once it is used that sequence is removed from the valid pool. This is to insure against replay attacks just as you describe. I've done it to myself before where I hit disconnect on accident and was unable to relogin until the next number came up on the fob.

      --
      There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  8. Timing.. by gmerideth · · Score: 5, Interesting

    Rather good timing that last night on "24" we see Cisco's name all over the screen's at the CTU command center and the actress works in the line "the Cisco network is defending itself" followed immediately by an Alienware laptop on the screen.

    Just in time for major articles about how bad Cisco's security was that they had some source code stolen. /golfclap foxtv

    And people wonder why I don't watch television. Sad..just sad.

    --
    Why do overlook and oversee mean opposite things?
    1. Re:Timing.. by Anonymous Coward · · Score: 3, Insightful

      If you dont watch TV how did you see that?

    2. Re:Timing.. by gad_zuki! · · Score: 5, Funny

      >And people wonder why I don't watch television.

      So this vision of 24 came to you in a fever dream then?

    3. Re:Timing.. by JTek · · Score: 2, Insightful

      Last night on "24"...And people wonder why I don't watch television. Sad..just sad.

      Obviously, you do watch television.

  9. hackiis6's 18yr old rule should be tossed out. by hydroxy · · Score: 2, Informative

    This definetly goes to show that www.hackiis6.com's 18yr old rule was probably imposed to simply limit the number of hackers who will enter. Props to the kid for pulling this off... even if he did get into trouble =).

  10. Alarming ? by alexhs · · Score: 5, Insightful
    The incident seemed alarming enough

    Why alarming ? The internet is still up and running since that last years theft.

    (I guess it should be read last year's)

    Sensationnal breaking news !
    The programming instructions of Linux and Free/Net/OpenBSD, which run many of big corporations servers, is avalaible to the sight of anybody! That's alarming!

    --
    I have discovered a truly marvelous proof of killer sig, which this margin is too narrow to contain.
    1. Re:Alarming ? by iztaru · · Score: 3, Interesting

      I think the problem with this could come from two corners: 1- The people at Cisco are not as confident with their source code as the people of Linux, Free/Net/OpenBSD 2- There are back doors in the Cisco systems for the government to use and they are afraid anyone else might find them useful!

  11. Wren Montgomery by kevin_conaway · · Score: 3, Insightful

    So let me get this straight. This lady knew that someone had breached her system and she a.) kept right on using it and b.) taunted the person who had breached her system? What was she thinking? If your machine has been compromised, pull the plug and clean it!

    1. Re:Wren Montgomery by Rauser · · Score: 2, Insightful

      My guess is that "her system" was just an account on some university *nix box, and that she had no more power to "pull the plug" than any other user.

      And anyway, since when does etiquette play into the considerations of teenage vandals of any kind?

      --
      The white zone is for loading and unloading only. If you need to load or unload go to the white zone. It's a way of life
    2. Re:Wren Montgomery by Otter · · Score: 2, Insightful

      And while normally I'd applaud her attempt to shove a PowerBook into the picture regardless of the actual topic, in this case Mac zealotry probably should have counseled some restraint...

    3. Re:Wren Montgomery by thulorn · · Score: 2, Informative

      Your guess is perfectly accurate; a Berkeley department cluster, with Wren having no power beyond informing the sysadmins of the breakin, which she promptly did.

  12. Contradiction? by simon2263 · · Score: 5, Insightful

    On one hand, the article claims that "With such information, sophisticated intruders would potentially be able to compromise security on router computers of Cisco customers running the affected programs" and on the other hand that Cisco itself claims that "the improper publication of this information does not create increased risk to customers' networks". These statements are, IMHO, in direct contradiction of each other. Who the hell should we believe?

  13. Thef by Doc+Ruby · · Score: 4, Interesting

    What do Slashdot "authors" (editors) do all day? They publish about 35 stories in a 24 hour cycle, usually about 4 editors participating. That's about 1-2 stories an hour, with 1-2 authors overlapping shifts. The summaries take about 2 minutes max to read, and the stories take max 5-10 minutes. That seems ample time to catch dups, fix typos, spelling and punctuation errors. Why not? What else are they doing? Maybe they don't read Slashdot after they've published, so they don't see all the feedback on their poor editing performance.

    --

    --
    make install -not war

    1. Re:Thef by gowen · · Score: 5, Funny
      What else are they doing?
      Applying massive amounts of negative mod-points to posts criticising Slashdot Editors... See you at (-1 Troll), baby).
      --
      Athletic Scholarships to universities make as much sense as academic scholarships to sports teams.
    2. Re:Thef by Doc+Ruby · · Score: 4, Interesting
      Moderation 0
      50% Interesting
      20% Troll
      20% Redundant

      Where's another post running a time analysis of Slashdot editing? Even given Slashdot's absence of features to prevent comment redundancy, isn't a chorus of "not again!" appropriate? And how is my coherent, accurate comment, which I haven't seen before, a "Troll"?

      Perhaps this comment is just the criticism uberpost, destined to point out all the serious flaws in Slashdot's publishing system model. If so, here's some constructive suggestions for fixing it:

      1. Submitted story queue filter: editors see a story, with links listed separately (already a Slashcode function). Links already published in a previous story are indicated, linked to the previously published story. Publishing such links includes an "ongoing coverage" indication in the new published story.

      2. Submission spell/grammar checker

      3. Submission link checker: links in stories in submission queue are interlinked through a Slashdot redirection script which sets a flag. Until each link's flag has been set, by following the link (through the script) to the linked object, the story cannot be published.

      4. Mod comments: Negative moderation must be accompanied by an explanatory comment, which can be viewed by metamoderators. Metamoderation gets more "teeth", with 3 "unfair" metamods cutting modpoints for a month, and 3 such suspensions cutting modpoints forever.
      --

      --
      make install -not war

  14. I get the very uneasy feeling... by kclittle · · Score: 5, Insightful

    ...that all the discovered breaches are by inept, pimply-faced teens (regardless of how many times some news article quotes some 'expert' about how 'particularly clever' the idiot was), and that the really serious harm is being done by real pros who never leave a trace.
    Scary...

    --
    Generally, bash is superior to python in those environments where python is not installed.
  15. Seriously, what's the problem? by daniel_mcl · · Score: 5, Insightful

    As a good number of regular slashdot readers are no doubt aware, full source code to Linux, Apache, etc. is available to anyone and they are more secure than their counterparts for this reason. If access to the source code for Cisco routers makes it possible to write a whole bunch of backbone-targeting virii that would really drop my opinion of Cisco routers considerably.

    If you actually read the article, the exploit was not big deal either; some guy just distributed a trojan'd SSH client to a bunch of people and collected their passwords and then ran a bunch of rootkits. Nothing to see here.

    --
    I used to read Caltizzle. I was a lot cooler than you.
  16. [OT] Re:Did they steal the editor too? by ackthpt · · Score: 5, Informative
    What's a Thef????

    You expect these things when someone begins a sentence 'More on'

    One of my English profs explained the importance of thinking through sentence structure so as not to be phonetically or grammatically careless, i.e. 'Me and Jim went to the arcade' as it could sound like 'Mean Jim went to the arcade', proper grammar is 'Jim and I went to the arcade.'

    Thus endeth today's grammar report.

    --

    A feeling of having made the same mistake before: Deja Foobar
    1. Re:[OT] Re:Did they steal the editor too? by unitron · · Score: 5, Funny
      Excuse me, did you say Gemini went to the arcade?

      Proper grammer is admirable, but it's no substitute for careful enunciation.

      --

      I see even classic Slashdot is now pretty much unusable on dial up anymore.

  17. Cisco VPN Client by Malc · · Score: 2, Interesting

    Tell me again why our IT department insists on using this buggy Cisco VPN Client POS that causes me grief on a daily basis...

  18. Catastrophic apostrophic by Ancient_Hacker · · Score: 3, Informative

    "last years theft" : A theft, in the last years of Cisco "last year's theft": A theft, in the previous year. Apostrophes do make a difference.

  19. This is actually kinda funny by Jetifi · · Score: 4, Interesting

    I mean, 'cybersecurity' bigheads are all worried about Terrorists disabling our Internet Infostructure etc., but in real life it turns out that any vulnerabilities that could be used to break into (e.g.) the JPL, White Sands, the DoD etc. have already been exploited by petulant teenagers.

    So in this sense, the script kiddies of the Internet are kinda like an early warning system: it's almost certain that before someone with serious intentions finds a nasty flaw and uses it, it'll be discovered by some kid who will promptly boast about it on IRC.

    How lucky we are that terrorists find themselves vastly outnumbered by people with too much free time on their hands!

  20. More Source Code stolen for Routers by Anonymous Coward · · Score: 2, Funny

    In other news, the source code for a different router/firewall technology was posted on the net: http://www.openbsd.org/cgi-bin/cvsweb/

  21. not just Cisco! by Heisenbug · · Score: 4, Funny

    a breach of a Cisco Systems network in which an intruder seized programming instructions for many of the computers that control the flow of the Internet.

    Just wait until these guys see apache.org ...

  22. John Markoff by wackysootroom · · Score: 5, Informative

    Note that this article was written by the person famous for creating the myth of Kevin Mitnick being a super hacker. Markoff is largely responsible for the fear and paranoia surrounding Mitnick and consequently his unfair prison experience.

    His articles were full of lies and exaggerations back then so I would take this article with a grain of salt as well.

    1. Re:John Markoff by thulorn · · Score: 2, Informative

      I've known Wren since college, and I share two (non-Berkeley) systems compromised by "Stakkato", and much of the article was spot on. The Cisco stuff I don't know anything about, but the hacker had broken into clusters at Berkeley and Caltech, and a private shared machine, and bragged about much much more. People we knew near Caltech security didn't say much, but indicated that the wave of breakins was in fact widespread and worrisome. IT people I know at Indiana University with TeraGrid connections also indicated at the time that much was going on. E-mails forwarded from the hacker showed much immaturity and petty malice, on top of deleting her home directory ("computer file directory" in the article.)

      Oops, another friend closer to the action said the Cisco stuff is accurate too.

      As for the powerbook in her lap, that was posed by the photographer. It was the UCB Unix machines which were hacked.

  23. RTFA by Anm · · Score: 3, Informative

    She did taunt anyone. She recieved taunts. It was these taunts that lead the authorities onto the trail. More so, his anger came from monitoring emails to the sys admin where he was called a "quaint hacker". The messages were not taunts. They were not even directed at him.

    Anm

  24. Re:Contradiction? Sorta. by RealProgrammer · · Score: 2, Interesting

    As odd as it sounds, both are correct. A sophisticated intruder could compromise security with the stolen code. Or not.

    But for the sake of argument, suppose they do find flaws in Cisco's code. An exploit shows up on rootkit.org or someplace. It should be apparent from the exploit which flaws they're using, and so Cisco cleans up the flaw. In the long run, customers are actually safer.

    It's sort of a backasswards way to open source your code.

    --
    sigs, as if you care.
  25. I wouldn't believe everything in this story. by Anonymous Coward · · Score: 3, Interesting
    Note that this article is by John Markoff, who has established a history of trying to milk arrests of people for his own personal profit, by not only sensationalizing security breeches, but assisting authorities to the point of being on site during the arrests, and doing book and movie deals afterwards.

    Don't confuse this story with independent journalism; Markoff is out to make a mint here, however he can.

    Markoff reportedly was pissed of at Kevin Mitnick for spurning a movie deal, and later set himself up to write "the Kevin Mitnick story", earning over a million dollars in the process.

    Here's a link: http://www.labmistress.com/kevins_story.php

    So one really has to wonder what the Truth is here, and whether Markoff is just trying to screw over some teenage kid in Europe in order to make another million off of it.

    So I'd take anything that John Markoff has to say with a LARGE grain of salt. The same goes for the New York Times, which has officially encouraged this practice.

    The real truth is probably out there; but I wouldn't expect to hear it from either John Markoff or the NY Times.

  26. We got hit. by glockenspieler · · Score: 4, Interesting

    My laboratory was hit. We're all linux machines. Turns out that I still had an account on a system at Stanford where I was faculty and I transferred some files via scp to my machine at my current university. 4-5 days later, i see some logins from Stanford to my machine but I because I had been using the Stanford account recently, it just didn't register.

    One day later, I'm on another lab machine using my lab /home directory (different from my main machine) and i notice a program (it was either brk.c or dobrk.c I think) that was on an unpatched system, allowed a priviledge escalation. I switch to root and look at the history and see a command to stop recording the command history but he (and the article indicates the person is male) misstypied it so i could see that he logged into this machine from mine, grabbed the source code for the exploit from a warez site, compiled, ran, got root, and just tooled around a little.

    Because our machines are pretty isolated and don't have any hint of financial stuff, he seemed to just drop it. I called the sysadmin at Stanford, turned out that on a machine with over 500 accounts (i won't say which department), the machine had been rooted about 2 months prior and every password was being captured during that time. The breakin was tracked back through a couple of departments, then back to University of Michigan, then to Uppsala.

    Three valuable and perhaps obvious lessons here. Local priviledge escalation exploits are important even if your system has very few users. Keep your system patched (duh...), and remember, if you log onto your machine from another, ask yourself "What do I know about the integrity of this machine?". I really assumed that my stanford account was pretty secure and so I didn't even think about logging from that machine to my current one. No more.

    The other interesting thing was that the local exploit used on my machines was announced well after the Stanford machine was hit. I don't think I ever heard of how that machine was comprimised.

    1. Re:We got hit. by s.d. · · Score: 4, Informative

      it was probably dobrk, that was one of the vulnerabilities the attacker(s) used last year to root systems.

      see http://xforce.iss.net/xforce/xfdb/13880 (this was the 1st google link i saw, there are probably others with better information but i'm lazy).

    2. Re:We got hit. by natet · · Score: 3, Insightful

      One other thing you should be aware of: Pull, don't push, data. In other words, don't log into a remote system and then use scp to send the data back to your system. That exposes your password on your local system to the remote system. Instead, use one shell window to find what you want to get, then open a separate shell window on your system to pull the data from the remote system, or use any one of the many graphical SCP clients to log in, navigate around, and pull data back down.

      I have seen several incidents where the former pattern was used and it resulted in a compromise of the users password. The lab where I work has gone to 2 factor authentication to make exploiting this pattern more difficult, but with session hijacking, it is nearly impossible to eliminate.

      I also want to point something out to those that have been critisizing Cisco's network security. The failure wasn't on the Cisco side of things. The actual security breach happened on a network 1 or more hops away from the Cisco network. As far as Cisco was concerned, a legitimate network transaction was happening. Someone with valid credentials logged on to the system, and until they do something out of the ordinary (install a root kit, scan the network, etc...) they are virtually undetectable, as they don't differ from normal valid network usage.

      --
      IANAL... But I play one on /.
  27. Re:It's not theft! by Halo- · · Score: 4, Informative
    Oh wait, sorry, we're talking about code not music. It's theft!

    I know you're trying to be funny, but I think you're missing something basic. The reason this is "theft" and not "infringement" is because the intruder made a copy of something not generally released. (the source code).

    In the music world, if someone buys an album, and gives copies to his or her friends, he is violatating the artist's right to control copies. (i.e. their "copyright"). If that same person hacks into the artist's recording studio, and downloads unreleased tracks, the artist has had those tracks stolen. It is a "theft".

  28. Re:Books on how to hack Cisco routers by Master+of+Transhuman · · Score: 2, Funny


    Yes, I'm shocked anybody thinks a CCNA can control a Cisco router...

    --
    Richard Steven Hack - This sig is TOO GODDAMN SHORT TO DO ANYTHING USEFUL WITH! MORONS!