Looking for something else?
In this excerpt from Chapter 3 of Hacker's Challenge 3, author Bill Pennington provides a detailed example of a situation in which an organization's network is attacked and customer data is compromised. After the excerpt, continue reading the rest of the chapter and then get the solution to this challenge.
|Attack Complexity: Medium|
|Prevention Complexity: Hard|
|Mitigation Complexity: Hard|
Monday, December 19, 2005, 09:17
Siamak was careful about unwarranted e-mails he received, even simple advertising schemes like the one shown in Figure C3-1, which was sitting in his inbox.
Siamak had his identity stolen once by someone who grabbed his mail while he was mountain climbing in Tibet. The person used that information to open up a few credit card accounts and create havoc for Siamak's records. Eventually Siamak cleared everything up with the credit companies, but after the fiasco he was paranoid about his personal information. Siamak wasn't likely to be conned by high-tech means, however, because he worked in technology himself and knew what types of risks were out there. He used a Mac, browsed the web using Firefox, and didn't install untrustworthy software.
Due to his competence and paranoia, Siamak wanted to make sure this e-mail was what it claimed to be. First he verified the e-mail headers as having come from ClimberCentral:X-Gmail-Received: 68db19b59b39cbe1db718b22dbf6bd5d6c8a29d2
Received: by 10.54.104.14 with SMTP id b14cs44461wrc;
Mon, 19 Dec 2005 05:27:10 -0800 (PST)
Received: by 10.36.227.70 with SMTP id z70mr396581nzg;
Mon, 19 Dec 2005 05:27:10 -0800 (PST)
Received: from camp7.sjc.climbercentral.com (camppool07.climbercentral.com [18.104.22.168])
by mx.gmail.com with ESMTP id c12si583418nzc.2005.12.23.13.27.10; Fri, 19 Dec 2005 05:27:10 -0800 (PST)
Received-SPF: pass (gmail.com: domain of email@example.com designates 22.214.171.124 as permitted sender)
Received: from [10.112.159.30] (dingdong-1.sjc.climbercentral.com [10.112.160.30])
by camp7.sjc.climbercentral.com (8.12.3/8.12.3)
with ESMTP id jBNLLwZp015175
Subject: Great ClimberCentral Deal!!
Date: Mon, 19 Dec 2005 05:27:08 -0800
X-Mailer: Kana Connect 6
The e-mail was actually from the ClimberCentral domain. Siamak clicked the Log In link and watched his browser's URL address bar (Figure C3-2).
Not every e-mail he received was an attempt to ruin his life. Content with his investigations, Siamak proceeded to log in and look around the site.
Monday, December 19, 2005, 09:50
Rob stumbled in to work late. It was the holiday season and he'd forgotten to put in for vacation. As a result, he was stuck here in rainy Silicon Valley watching over ClimberCentral's operations while the rest of the ClimberCentral crew was enjoying Hawaii. At least Rob could party this week, with no one at the office noticing that he showed up to work with bloodshot eyes and smelling like stale booze.
"Good morning!" It was Llana; Rob tried to shrug off her attention and slip past her into his cube. Thank goodness for cubes.
"Hey, maybe you could find out what's going on with the gobi web server. Customer order e-mails aren't being sent out, and the thing's chugging under a big load," she added.
"Yeah, on it." Duh, Rob thought, as he plopped down and opened up a shell. Sure enough, so many e-mail messages were lined up in the queue that the whole server had ground to a halt. He ran a quick command to see what was going on:
The mass of marketing e-mails was choking the gobi server with an unexpected load. Rob assumed one of the developers was responsible, so he e-mailed the development team reminding them not to send marketing e-mails from the gobi web server. After he deleted the pending marketing e-mails and got the server up and running again, he relaxed by firing up the Slashdot website and downing some Tylenol.
Monday, December 19, 2005, 13:11
Llana averted her eyes when she entered Rob's cube to find him browsing suicidegirls.com.
"Hey, customer service is worried about some issue with tons of disputed false orders, and since Lex isn't in I suggested they direct the issue to you."
"Yeah," snorted Rob, "but have you heard of e-mail?"
Llana frowned. "I sent you the details, but this is kind of urgent so I wanted to make sure and see if you needed some help."
Rob mumbled something and didn't pay attention as Llana slunk away. Skimming the e-mail, he noticed a suspicious pattern with the "false" orders: they were all being delivered to the same P.O. box. He went to the database to find out more:
This didn't look good. Orders that were supposedly placed by different users were all coming from the same IP address and being sent to the same P.O. box in Alaska. It seemed clear that an attacker had either compromised the individual user accounts or somehow broken into the ClimberCentral system. Rob drew up an action plan:
- Cancel all orders to P.O. Box 37452 in Bloomingdale, Alaska.
- Notify public relations that the company's servers had been compromised, and have them contact affected customers.
- Have Llana take down the website and put up an "under construction" page until they resolved the security hole.
- Block the 253.102.200.3 IP address from accessing the network.
- Begin the investigation process, probably by making backups and contacting Lex.
Monday, December 19, 2005, 14:35
Llana had enrolled a guy from marketing who knew a bit about Linux to help her make backups. Rob was still trying to reach Lex in Hawaii, to see if he knew how they should proceed.
The IP address 253.102.200.3 was the only information Rob had to act on. After getting bored of calling Lex's hotel to find out whether he'd come back from his hike yet, Rob decided to investigate ClimberCentral's access logs and see if he could find other useful information.
Continue reading about this challenge in Chapter 3: Big Bait, Big Phish of Hacker's Challenge 3.