This is a presentation I gave about embedded security at the last 2600 meeting. This mostly just referencing other people’s work like Joe Grand and Travis Goodspeed who are embedded security gods.
Here is a brain dump of what happened this weekend at ISTS 9, SPARSA’s Information Security and Talent Search. A bunch of the people from 2600, Raphael Mudge, Punkrokk, Joe, Gerry, and others were part of the Red Team.
The event worked like so: There were 13 Blue Teams, groups competing in the event. Their job was to take the 5 servers that they were given, run specific services in order to get points, and, something a little different than other competitions, hack into other groups for points. If you do this, you will receive points that are tracked throughout the weekend. Finally, challenges were to be performed that were worth more points.
I really like this style for students compared to CCDC or other types that attempt to give competitors the simulation of running an enterprise network. These competitions will force competitors to stand up services, defend against attacks, and write up little reports that explain how the attackers got in and their remediation plan. This is a great simulation for real enterprise environments for students looking to get into a career as a systems administrator, but ISTS gives you a chance to show off your security skills, even the offensive ones.
Friday, students fill up the GCCIS auditorium and the mood is really light. Teams are wearing silly hats, the group that won last year is feeling pretty confident that they’ve earned some cred to be there again. The red team is stalking in the corner, marking its prey. SPARSA goes over the rules, hands teams their packets, and lets them know how the next day goes. Each of the teams have the rest of the night to go home and build up their attack boxes as VM’s. That’s right, they’re allowed to bring their own VM’s, just to attack other players.
The next morning, we arrive at RIT to meet the red eyed SPARSA members who have been working through networking issues all night.
A side note about the network this year: it was very well done. This may seem like a silly thing to note but seriously, you have almost 100 people pummeling each other over the network, issues will occur. Compared to other years, there were very little issues. Last year we were out of a connection for a long time. This year there may have been a blip here and there, but it was quickly remedied.
The battle ground is RIT’s Innovation Center. If you’ve never seen this thing, it’s like something you’ve seen in Swordfish or the Matrix. The walls are all glass including partitions inside the space itself. The Fish Bowl is slathered with power plugs, ports, projectors, and preposterously plush ammenities.
May The Odds Be Ever In Your Favor
Let me make sure I explain the insanity of the first 30 minutes. Blue teams walk in with their own VM’s loaded up with whatever scripts or automated attacks they want to launch. That’s every team, of 5 people, ready to kill the other 60 players, with all kinds of attacks. And then there’s Raphael, prepped with his Armitage server, automated scripts, and a big smile on his face.
If I were competing, I would have chosen a tactic for the first part of the event, just like The Hunger Games. If you’re going to battle ninja v ninja, you had better make sure your weapons and foo is strong or you’ll end up a bloody pile of empty dreams. If you’re relying on a strategic victory, you may decide to focus your energy on protecting yourself from others attacks; I call this the run-into-the-woods strategy.
Let me also just say, that the Red Team had no special information related to the event… though we tried. In fact, in some ways, the Red Team is not necessary because all the other teams are already breaking into each other.
We let the students trickle into their stations and the battle begins. We are just scanning subnets when Raphael announces “I have 10 shells!” His scripts have automatically installed meterpreter sessions that are phoning home. His persistence scripts automatically make sure that we can come back to these accounts later. The rest of the red team is destroying boxes, the same as what the Blue Teams are doing to eachother.
Let’s be honest, the best part about being on Red Team is messing with the other teams. The Blue Teams all started with VNC open which made for some hilarious hacker watching. The first was one team that put all their attack scripts on their desktop. This was actually pretty cool attack script which was a reverse shell that automatically tweeted a user’s password when the owned a box. Follow ISTS Tweeter to see the fun they had.
The other one was a group that decided to plug in a drive that contained a lot of personal information. Including a resume. We passed the file to a nc listener that Justin Elze had running on his machine and printed it out to hand deliver to the group. One team member figured out how to break into a box and trick a hard drive into having a single sector. No seriously. This is pretty awesome. The box was never heard from again. It couldn’t be reformatted. Raphael had some fun with one team’s SMTP server and a VNC payload.
I’m sure that video will show up somewhere soon.
UPDATE 4/1/12 8pm: Video is up
I usually come to the same conclusion after every year which is “damn, I wish I had planned for X.” I think this year, the conclusion is that, “damn that was fun. Let’s do this more often.”
Interlock has recently been donated a bunch of really good equipment. One of the servers has 20G of memory and lots of hard drive space. We’re going to be setting up a proper Warzone that will allow us to run these type of events when we want to. I’m going to rely on the other 2600 people to get something cool setup.
Every month we do the 2600 meetings. Lately I send out this ridiculous email to my circles and social networks explaining a theme of the meeting. It looks something like the one I did for January:
Only 12 months away from the end of days where the Earth’s polarity will completely flip causing server faults to erupt with hot Java and spew volcanic bash. Sudonomies will destroy cities and cause packet storms. 2012 will mark the return of the Carriage causing lines to break all over the world.
This month’s pre-apocalypse meeting will cover topics completely unrelated to your apocalyptic survival. In fact, the skills learned will most likely be completely useless in the face of actual danger. These are the presentations that are happening this month. The titles do not represent any of the subject matter nor the presenters names.0) Antitree: Things I Learned By Not Attending 28c31) Algorythm: Why My SSLScan is Better Than yours2) Punkrokk: Would You Like To Ride My Pwnie (Pwnie Plug talk)3) SecCaoBoi: Mopping The Network With a WPAD Attack4) JewNinja: XSS Attacks: Finding A Hole In a Brick Wall
Doors open to the public at 7pm.The 2600 meeting is a copyright of Emmanual Goldstein and his band of merry hackers. All usage of the 2600 name and logo is directly prohibited without the direct written consent of Captain Crunch. The world may not end in 2012 but it is up to the user to kiss his or her own ass goodbye prior to any apocalyptic event. Ass kissing assistance will not be provide in any case. Members are prohibited from attending meetings. Requests for membership can only be made if you are an existing member and in good standing with Heidi Potter and a resident of the great state of Alaska.
First of all, I recognize how this is very frightening to most. I’ve seen responses like “Where do you get your drugs” or “who the eff is this guy?” Punkrokk showed this to Heidi Potter (the organizer of Shmoocon) and I’m sure it raised an eyebrow. So to explain why I do it here it goes: I don’t know – it makes me giggly.
The random emails have had a consistent reference to how members of 2600 were not invited and you had to not be a member to get in. This came from whenever someone asked me about 2600, they would say “How do you become a member” or “How many members do you have.” To me this was a sign that they had never been to a 2600 meeting and, as Zach Fasel said to me on my first 2600 meeting ever: “Newb.” Of course I’m supposed to say there’s nothing wrong with that, blah blah blah but it was another opportunity to have an inside joke with people that had been to the meetings. So all the references to “Non-members only” was my joke to myself (albeit not even that funny) mostly to entertain myself when only 4 people came to meetings.
What’s also funny is that people at the hackerspace, where we hold the meetings, took “non-members only” to mean that Interlock members were not invited to the meetings which made me laugh as well.
So look at me and my hilariousness. Aren’t I so funny! I’ve created inside jokes that have grown out of control. There. Done.