Yesterday, with only hours to go, COPE and the Hash Puppies came to an agreement:  The Hash Puppies gave COPE all of the flags that they had captured that COPE already didn’t have, bringing COPE into a solid first place.  In return, COPE gave the Hash Puppies enough assistance to secure second place.  At first, I was skeptical that COPE would give the Hash Puppies good value for their trade, but it looks like it turned out well for both teams, to the dismay of SwaffleU, who held the lead prior to the deal.

The final scores are as follows:

  1. COPE – 30
  2. Hash Puppies – 27 (with a last submission time minutes prior to SwaffleU’s)
  3. SwaffleU – 27
  4. Wesley’s Unkempt Beard – 18
  5. BitBangers – 11
  6. Team 4 – 9

The game really came down to the wire, with the tie for second broken by time-of-last-submission.  This was probably the most competitive semester of CTF yet.

I had a blast running the game, and I hope that all of the participants had a good time too.  If you participated this semester, please email in any scripts/tools/notes that you wrote during the process of the game, so that we can review them in our post-mortem.  I already have copies of many of them, but I’d like to make sure that I have the final versions you had at the end of the game.

 

This is the last day of CTF for this semester.  At 3:30 PM, it’s all over but the crying.  We’ll have a countdown, likely set to “Eye of the Tiger”.

Yesterday when I arrived to make sure the VMs were still up and running, no teams were in the room.  I was feeling a bit mean, so I took this as an opportunity to power-cycle all of the attacker workstations in order to see how their scripts deal with a power blink.  I also used this moment as a chance to grab scripts and random files left laying around on the various workstations, locked and unlocked.  If you’re in the area, look forward to an upcoming talk: “Found Files of MSU CTF”.

SwaffleU has taken the lead, though COPE and Hash Puppies are not far behind.  It’s likely that one of the lower-ranked teams is quietly waiting for the last moments, as well.  The scores, as of 9AM:

  1. SwaffleU – 24
  2. COPE – 23
  3. Hash Puppies – 19
  4. Wesley’s Unkempt Beard – 9
  5. Team 4 – 8
  6. BitBangers – 7
 

I left early last night to have dinner and watch the new Harry Potter movie, so I neglected to post an update yesterday evening.  I normally make 8AM posts, but this is a Saturday, so you’ll just have to make do with an 11AM update.

COPE have taken the lead with 18 flags, and this represents the first time since the beginning of the game that the Hash Puppies have lost the lead.  I offered them the opportunity to post a flag before this update in order to take the lead back, but they declined.  The Hash Puppies seem to be quite happy in second place.

The best computer that I have seen in the competition so far is this 486, 66 MHz beast that a member of COPE set up:

It’s

  • missing a panel or two
  • has no branding whatsoever (the sticker on the bottom helpfully suggests that it’s a “Notebook Computer”)
  • has a broken keyboard (you can see the edge of the keyboard that’s plugged in on the left)
  • reports itself in some ancient version of Linux as having about 18 and a half megs of RAM (what?)

The current scores are:

  1. COPE – 18 (Last submission 8 hours and 22 minutes ahead of the Hash Puppies)
  2. Hash Puppies – 18
  3. SwaffleU – 10
  4. team4 – 8
  5. BitBangers – 7
  6. Wesley’s Unkempt Beard (previously known as Team 2) – 2

Flag: 4cbd40766a

 

Last night, while my wife had a girl’s night out with some friends, I had the opportunity to hang out in the lab and observe CTF until nearly 10 PM.  Teams were busy in the lab, hacking away the entire time, and I hear that even after I left, there were people in there at 1 AM, and possibly later.  The scores have moved a bit:

  1. Hash Puppies – 15
  2. COPE – 10
  3. SwaffleU – 6
  4. Team 4 – 3
  5. BitBangers – 2
  6. Team 2 – 1

Teams discuss strategy for holding onto flag submissions until the last minute, but often it’s too much to bear to see your team fall down in the current rankings.  A few points placed on the board by one team will often result in points posted by other teams.  I suppose they want to look good on the blog updates ;) .

 

Today has seen a lot of activity from SwaffleU, the Hash Puppies, and COPE (previously known as Team 5), though not a lot of movement in the points.  It remains to be seen how many of those 13 points the Hash Puppies put on the board were sniffed off the wire by other teams that are waiting for a safer opportunity to submit.  The scores, as of 5PM:

  1. Hash Puppies – 13
  2. COPE (formerly Team 5) – 6
  3. Team 4 – 3  (last submission time 1’27″ before SwaffleU)
  4. SwaffleU – 3
  5. BitBangers – 2
  6. Team 2 – 1

On the scoring server, I can see the table of submissions, and can verify that most of the flags submitted represent the “low hanging fruit” of the game.  It’s definitely the right thing to do, to go after these first, since the points are equal for all flags regardless of difficulty.  Hopefully soon though, we’ll see the teams get around to some of the more challenging flags.

Next update will be around 8AM tomorrow morning, or later tonight if something interesting happens.

 

I arrived this morning to find the VMs responsive on the network, however the console of the VM server was locked hard.  If you’re one of the participants, and you had something running on any of the VMs, or any sort of persistent connection, you may have to put it back up the next time you go in.

This morning I heard a gripe about the completely hubbed and sniffable nature of the CTF network.  This player was concerned about his hard work being sniffed and resubmitted by another team.  I do like the need to be creative about your communications though.  We have many teams generating cover traffic, and simultaneously writing scripts and filters to try to make sense of all the traffic on the network.  It’s an interesting arms race, and I think it adds a fun meta-game for the top-tier students who are already doing well capturing flags.  There are some downsides to focusing on sniffing as well.  Imagine a situation where you pull an all-nighter trying to get a certain flag, only to find out when you submit it that you already have that one from the wire.  Time wasted :)

Here are the scores, as of this morning:

  1. Hash Puppies – 13
  2. Team 5 – 5
  3. Team 4 – 3
  4. SwaffleU – 1
  5. BitBangers – 0
  6. Team 2 – 0

Teams that have not decided on a name by this evening (Looking at you, 5, 4, and 2.) will likely have a name of my choice assigned to them by me.  This is probably not something they want.

 

Today, right after the Information and Computer Security class, teams of students began hacking on the capstone exercise for the class: Capture the Flag.  As in past semesters, the students are let loose on an isolated network, and are to scan for vulnerable machines, exploit them, and collect flags that are scattered around the network in the form of 10-digit hexadecimal strings.  These flag strings are then submitted to a scoring server, which also must be located by the students, in order to bump their score.

For the past few semesters, I’ve posted updates throughout the game to this blog, and I’ll try to keep you updated with commentary this time as well.  The game just started about an hour ago, and the scores are currently:

  1. Hash Puppies – 4
  2. SwaffleU – 1
  3. BitBangers – 0
  4. team2 – 0
  5. team4 – 0
  6. team5 – 0

The Hash Puppies took some initiative to submit a handful of flags quickly, trying to get them in before the other teams had set up sniffing programs to intercept.

The game will run until Monday at the beginning of class (3:30 PM Central).  The plan is to have a morning update on the blog and an update in the afternoon/evening of each day, though this schedule may vary a bit over the weekend.

Best of luck to all the teams.  Here’s a free flag for following along on here: 9c09c9cc1d

 

I let the law enforcement class go on break briefly this morning so that I could be there to witness the end of this semester’s Capture The Flag competition.  In the tradition I began last year, playing “Eye of the Tiger” during the last moments of the competition, Chris loaded up “The Final Countdown”.  This is a tradition we enjoy, but it drives most of the participants crazy.

The final scores reflect all of the flags captured by the teams.  Everyone managed to submit theirs on time, just before the 9:30 deadline.  Here are the scores:

  1. Team Firewall – 30
  2. Team Sniffer – 23
  3. Team Wireshark – 20
  4. Team Burp Suite – 15
  5. Team Nmap – 9
  6. Team Tracker – 8

Automated sniffing and resubmission of flags was performed successfully by many teams this semester, and it made for an interesting dynamic in the post-game discussion and wrap-up.  Team Sniffer disclosed that 8 of their flags were captured off the wire and resubmitted.  Other teams also had success with stealing others’ flags in the same way.  This also had an unforeseen circumstance: often a team would sniff and submit a flag without knowing where it came from in the game.  Those teams would then spend time actually breaking into a system to capture a flag, only to find out it was one they already had submitted.

Congratulations to Team Firewall for an outstanding CTF performance, and I am looking forward to examining some of the tools and scripts the teams wrote for this competition.

 

Everyone still has the itus from the food and festivities yesterday, so things are moving a little bit slow in the lab today.  There was only one pen-tester-in-training in there when I just checked, but it was obvious that others had been through, judging from the food wrappers in the garbage.  This is how hackers in the deep south roll on Sundays: It’s a day of rest, but you still have to scratch that itch to hack.

The lone participant was a member of Team Sniffer, and assured me that they have every expectation and plan to catch up with Team Firewall.  There’s a lot of prime late-night hacking time between now and the end of CTF on Tuesday morning, so I don’t think it’s a bluff on Sniffer’s part.

The scores, as of 2:00PM on Sunday:

  1. Team Firewall – 27
  2. Team Sniffer – 11
  3. Team Wireshark – 3
  4. Team Burp Suite – 1
  5. Team Nmap – 0
  6. Team Tracker – 0

For a moment, I thought I needed to get Fyodor to give Team Nmap a call to get them into action (would they know who he is? :) ), but I did notice that Team Nmap has reserved a computer for running processes persistently.  Maybe they’re sitting on their flags for the moment.

 

While everyone else is out partaking in food and fun at MSU’s Super Bulldog Weekend, Old Main Music Festival, and Cotton District Arts Festival this weekend, the true alpha-security-nerds are living it up in the lab.  On my way over to the music festival, I have stopped by the lab to see how the teams are doing.  A couple of guys (from two different teams) were in at the moment, hacking away.

One participant informed me as soon as I arrived that one of the targets was down.  I logged in and took a look: the VM was completely off.  New rule: no “shutdown -h now” :)

The scores as of approximately 7:00PM:

  1. Team Firewall – 27
  2. Team Sniffer – 6
  3. Team Wireshark – 3
  4. Team Burp Suite – 1
  5. Team Nmap – 0
  6. Team Tracker -0

Team Sniffer has bumped their score up significantly, and it’s likely that they are sitting on some un-submitted flags.

I’ll be back at some point tomorrow to post a Sunday update.  For now, it’s off to the Old Main Music Festival for me.

© 2012 McGrew Security Suffusion theme by Sayontan Sinha