Wednesday, September 9, 2009

"Daemon" by Daniel Suarez.

A must-read for everyone interested in the future of AI, automation and technology in general.

This novel is awesome. All the enumeration, sniffing and penetration methods and tools used in the story are all real and up-to-date. A computer game software genius dies and leaves behind the best AI ever created and a kick-ass "daemon" process to automate things. How do you fight evil packets? Go figure it out how the rest of the story unfolds.

So for a change, get out of your chair, away from your computer monitor and pick up the book from the nearest bookstore t. Currently enjoying the Audio Book version for my second reading of the book, and drooling of having my hardcover copy signed by the author.


http://thedaemon.com/

Below is a brief E-mail exchange with the genius behind the book, Daniel Suarez:


Excellent novel Daniel, looking forward to Freedom (TM).

One question though, regarding this line from the novel:

"So far, Gragg had a cache of nearly two thousand high-­
net-­wort identities to sell on the global market, and the Brazilians and Filipinos
were snapping up everything he offered."

Does this mean that based on your research (and statistics), most of these bad guys lurking around IRC channels are either from Brazil or the Philippines?

I am a Filipino residing here in the Bay Area and I am into VoIP Security, and overall IP-based Systems Security as well.

All the best,
Ron

+++

Hi Ronald,


Thanks for the kind note. I'm glad you enjoyed Daemon.

When I wrote Daemon back in 2004, Brazil and the Philippines were big
centers for identity theft; however, much of that has since moved to other countries. With the rise of botnets, though, it's increasingly difficult to tell where exploits and penetrations originate (with zombies serving as proxies...).


Best,
D.S.

+++

Daniel,


Agreed, 2004, those where the days. Now the Philippines is into hosting Call Centers
(and exploiting them) and Brazil is into US-Satellite tapping, lol.


Do you mind if I post your reply to my blog? (http://packetboyperseus.blogspot.com) I am planning to put up a simple personal review so my network of friends can see it and eventually pick it up from the nearest bookstore. I am sure they will love it as well.

All the best,
Ron


Hi Ronald,

My main point is that the future of cyber warfare is going to be driven by botnets and
distributed attacks originating from small groups of individuals (not
nations).

I don't want to sound like I'm 'blaming' that on Russians,
Brazilians, or Filipinos. The root cause of our IT security problem is
the inherently open architecture of global networks and the monoculture
that is modern software.

There are now cyber criminals and cyber warfare
units all around the world, and solving the infrastructural issues is
more important than playing international whack-a-mole with would-be
perpetrators--no matter what country they hail from.

Best,
D.S.

+++

Saturday, September 5, 2009

Tracing packet drops in Florida and sniffing traffic from 35K feet

I recently traveled to Hollywood, Florida for a customer on-site network troubleshooting. We usually do things over the phone and remote access if needed, but this customer insists that its our VoIP application acting up, and not their network. So the next day I went to their facilities, met with one of their IT Staff and immediately started mapping out their wired network (for fun and profit).



After a couple of minutes of tracing un-labeled RJ45 cables and network devices in general, I was able to trace the root cause. The bottleneck is originating from a commercial firewall installed on their network. I am not going to identify the brand and model, but its one of those firewall not meant to handle tremendous amount of traffic. In short, its a small-office-home office firewall/router. Their facility generates around 12 to 20mbps of outbound traffic on a daily basis.

This firewall goes gaga when hit by too much traffic; it simply drops all concurrent connections and resets as evident on the firewall and router logs. Good thing their Network Admin made the right choice and decided to get hold of a Cisco ASA 5505 Security Appliance and replace their current firewall. The problem is this guy does not know how to configure the ASA and needs to outsource the configuration and installation, so the ASA needs to wait while the problem still persists on their converged network.

To add salt to the wound, they are using old-school workstations; running Celeron 2.0ghz processors with a measly 256mb of SDRAM. Understand that these workstations handle a softphone-based VoIP client, a web-based CRM, Instant Messaging client, and Agent productivity apps. I say good luck with that. As suspected, Agents usually encounter the white screen of death where everything halts and freezes, hitting the Reset button is their usual routine.

Add the workstation hardware issues and misconfiguration on the network and you get a very painful and regretful VoIP experience.

Knowing how painful this experience is to their Agents, what I did was strip down Windows XP Pro to the bare minimum to free additional memory and overall system resources. What I meant with a stripped-down version is by disabling all Local Services that are not needed, adjust the workstation to Best Performance, disable tons of start up and running applications via msconfig, and finally, lock down the Agent login to Limited Rights so they can't install those nasty shopping IE add-on toolbars, lol. Things you must do when no Domain Controller is not present on a large network.

O
n my way back home to the Bay Area, I had some fun on-flight thanks to Gogo In-flight Internet without actually signing up for their service.

Thanks to Wireshark, ZenMAP GUI, and my laptop's Intel(R) Wireless WiFi Link 5100 card I was able to take a glimpse of the WiFi activity on-board the plane.

Intense Scan plus UDP output on NMAP:
nmap -sS -sU -T4 -A -v -PE -PA21,23,80,3389 172.19.131.2

Starting Nmap 5.00 ( http://nmap.org ) at 2009-09-03 16:40 Pacific Daylight Time
NSE: Loaded 30 scripts for scanning.
Initiating ARP Ping Scan at 16:40
Scanning 172.19.131.2 [1 port]
Completed ARP Ping Scan at 16:40, 0.22s elapsed (1 total hosts)
Initiating Parallel DNS resolution of 1 host. at 16:40
Completed Parallel DNS resolution of 1 host. at 16:40, 11.39s elapsed
Initiating SYN Stealth Scan at 16:40
Scanning 172.19.131.2 [1000 ports]
Discovered open port 80/tcp on 172.19.131.2
Completed SYN Stealth Scan at 16:40, 5.05s elapsed (1000 total ports)
Initiating UDP Scan at 16:40
Scanning 172.19.131.2 [1000 ports]
Completed UDP Scan at 16:40, 4.26s elapsed (1000 total ports)
Initiating Service scan at 16:40
Scanning 1001 services on 172.19.131.2
Service scan Timing: About 0.40% done
Service scan Timing: About 1.50% done; ETC: 18:43 (2:00:31 remaining)
Service scan Timing: About 3.00% done; ETC: 18:13 (1:29:33 remaining)
Service scan Timing: About 4.50% done; ETC: 18:02 (1:18:15 remaining)
Service scan Timing: About 5.99% done; ETC: 17:57 (1:12:09 remaining)
Service scan Timing: About 7.49% done; ETC: 17:54 (1:08:07 remaining)
Service scan Timing: About 10.39% done; ETC: 17:43 (0:56:12 remaining)
Service scan Timing: About 10.49% done; ETC: 17:50 (1:02:43 remaining)
Service scan Timing: About 13.39% done; ETC: 17:43 (0:54:02 remaining)
Service scan Timing: About 13.49% done; ETC: 17:48 (0:58:55 remaining)
Service scan Timing: About 16.38% done; ETC: 17:43 (0:52:03 remaining)
Service scan Timing: About 16.48% done; ETC: 17:47 (0:55:49 remaining)
Service scan Timing: About 19.38% done; ETC: 17:42 (0:50:03 remaining)
Service scan Timing: About 19.48% done; ETC: 17:46 (0:53:11 remaining)
Service scan Timing: About 22.38% done; ETC: 17:42 (0:48:06 remaining)
Service scan Timing: About 28.37% done; ETC: 17:42 (0:44:16 remaining)
Service scan Timing: About 34.37% done; ETC: 17:42 (0:40:29 remaining)
Service scan Timing: About 40.36% done; ETC: 17:42 (0:36:45 remaining)
Service scan Timing: About 46.35% done; ETC: 17:42 (0:33:01 remaining)
Service scan Timing: About 52.35% done; ETC: 17:42 (0:29:19 remaining)
Service scan Timing: About 58.34% done; ETC: 17:42 (0:25:37 remaining)
Service scan Timing: About 64.34% done; ETC: 17:42 (0:21:55 remaining)
Service scan Timing: About 70.33% done; ETC: 17:42 (0:18:13 remaining)
Service scan Timing: About 76.32% done; ETC: 17:42 (0:14:32 remaining)
Service scan Timing: About 82.32% done; ETC: 17:42 (0:10:51 remaining)
Service scan Timing: About 88.31% done; ETC: 17:42 (0:07:10 remaining)
Service scan Timing: About 94.31% done; ETC: 17:42 (0:03:30 remaining)
Service scan Timing: About 98.90% done; ETC: 17:43 (0:00:41 remaining)
Completed Service scan at 17:42, 3688.53s elapsed (1001 services on 1 host)
Initiating OS detection (try #1) against 172.19.131.2
NSE: Script scanning 172.19.131.2.
NSE: Starting runlevel 1 scan
Initiating NSE at 17:42
Completed NSE at 17:43, 36.19s elapsed
NSE: Starting runlevel 2 scan
Initiating NSE at 17:43
Completed NSE at 17:43, 5.02s elapsed
NSE: Script Scanning completed.
Host 172.19.131.2 is up (0.0014s latency).
Interesting ports on 172.19.131.2:
Not shown: 1000 open|filtered ports, 999 filtered ports
PORT STATE SERVICE VERSION
80/tcp open http?
| html-title: Site doesn't have a title.
|_ Did not follow redirect to http://airborne.gogoinflight.com/abp/page/abpDefault.do?REP=127.0.0.1&AUTH=127.0.0.1&CLI=172.19.131.153&PORT=54273&RPORT=54272&acpu_redirect=true
MAC Address: 00:E0:4B:22:96:D9 (Jump Industrielle Computertechnik Gmbh)
Warning: OSScan results may be unreliable because we could not find at least 1 open and 1 closed port
Device type: general purpose
Running: Linux 2.6.X
OS details: Linux 2.6.18 - 2.6.27, Linux 2.6.26
Uptime guess: 0.405 days (since Thu Sep 03 07:59:45 2009)
Network Distance: 1 hop
TCP Sequence Prediction: Difficulty=197 (Good luck!)
IP ID Sequence Generation: All zeros

Host script results:
|_ nbstat: ERROR: Name query failed: TIMEOUT

Read data files from: C:\Program Files\Nmap
OS and Service detection performed. Please report any incorrect results at http://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 3757.66 seconds
Raw packets sent: 4045 (148.498KB) | Rcvd: 31 (1502B)
Wireshark Capture Screenshot:



Noteworthy discovered Protocols and Services gathered from the Wireshark .pcap capture:

- Cisco IP-SLA
- TACACS and XTACACS
- BOOTP
- TFTP
- CLDAP (Connectionless Lightweight Directory Access Protocol)
- Cisco Wireless LAN Context Control Protocol
- Mobile IP Protocol (RFC 3344)
- RIP (Routing Information Protocol)
- OpenVPN
- OCSP (Online Certificate Status Protocol)
- Slimp3 Communication Protocol (Device ID: 101) (Firmware Revision: 6:12 (0x6c)
- Base Station Subsystem GPRS Protocol (BSSGP)
- CFLOW (Cisco NetFlow/IPFIX)
- CUPS (Common Unix Printing System)
- GPRS Tunneling Protocol (GTP)
- H.225.0 RAS

Discovered Network Device Signatures/MAC OUI's:

- JUMP INDUSTRIELLE COMPUTERTECHNIK GmbH (00:e0:4b)
- Hon Hai Precision Ind. Co., Ltd. (00:22:69)

You can easily Google those two identified manufacturers and you will have and idea what type of devices they produce.

As always, hit me up on E-mail if you want a copy of the complete .pcap capture and I will be glad to send you a copy, for research and analysis of course. Let me know if you guys need additional information as well about my recent 35K feet packet-sniffing adventure.

On my next flight, I am bringing an external USB antenna with packet-injection capability :-) attached to my future 1000HE netbook.

Happy packet-sniffing everyone and try not to break any law in the process!
Ron

Friday, August 28, 2009

Source Codes for a Skype Eavesdropper Trojan Released for Public Viewing

trojanhorseAs announced some weeks ago the Skype trojan sourcecode will be available for download. You find the source packages in the Tools & sources section if you are the impatient type.

The code is simple and straightforward. You have know malware development is no rocket science and if you expect big magic you are at the wrong place. The backdoor receives instructions from the dropzone and transferres audio files. The Skype-Tap intercepts the Skype function calls, extracts and dumps audio data to files, converts it to the mp3 format and encrypts it.

The code is not 100% complete. I removed the plugin system in the backdor and also the firewall bypassing system is not there anymore. I will publish both of them in separate tools later. If you don’t like this … well, I can’t help you. Thats how it is. Take it or leave it.

As always I am open for your opinions and criticism.



Complete article and technical details from Megapanzer's website:

From http://www.megapanzer.com/

Monday, August 24, 2009

The day my box almost got 0wn3d by Chinese boxes

Last month, I moved to a new apartment and decided to hook-up a high-speed Cable Internet from Comcast (as openly documented on this very same blog) as my primary connection to the world wide weird. This was July 15 and I was working at home that day.

With no router or a switch at hand yet, my Sony Vaio
VGN-BZ560 laptop is connected directly to Comcast's modem, getting a dynamic Public IP address from time to time. Something exciting happened right in front of my eyes as my Symantec Endpoint Protection software started displaying notification windows, stating a couple of Intrusion Prevention logs. I immediately accessed the Client Management Logs - Security Log feature of Symantec's Endpoint Protection and here's what I found:

[SID: 20081] MS SQL Stack BO detected.
Traffic has been blo
cked from this application: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe

Traffic from IP address 58.51.89.122 is blocked from 7/15/2009 1:33:12 PM to 7/15/2009 1:43:12 PM.

Active Response that started at 07/15/2009 13:33:12 is disengaged. The traffic from IP address 58.51.89.122 was blocked for 600 second(s).

I immediately launched my Wireshark to capture the network interface, then went inside Symantec Endpoint Protection's Client Management - Security Logs and turns out the attack has started since 5AM this morning PST!

Here are the logs of the first attempt:

[SID: 20081] MS SQL Stack BO detected.
Traffic has been blocked from this application: C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe

Traffic from IP address 218.23.37.51 is blocked from 7/15/2009 5:48:38 AM to 7/15/2009 5:58:38 AM.

The logical thing for me to do is to trace where these IP addresses are coming from. So I made a few back traces using my VisualRoute Tool and surprise! Surprise! Yes, the IP addresses are all from China.

The source IP's are all from China, if the back trace is reporting it correctly and these attackers are not using some mechanism to hide their real location, or probably just a bunch of compromised boxes or BotNets serving their master somewhere here in the States. But my guts keep on telling me that these are really coming from China.

My Sony Vaio Laptop is running Windows XP SP3. Installed is Microsoft Office 2007, with Microsoft SQL Server 2005 pre-installed which is the backdoor of this attack based on the Symantec Endpoint Protection Security Logs.

I am sure that my MS SQL Server 2005 service is not running on the background as a Service on my laptop turns-out that our new customer network connectivity troubleshooting tool called PathView by Apparent Networks is using a Local SQL Server Service on my laptop as well. By virtue of logic, I believe this application gave another backdoor for this MS SQL based vulnerability.

Below are actual screen shots while the attack is occurring:

(Click on the images to enlarge them)

Symantec Endpoint Protection Client Management Logs - Security Logs

PathView SQL Server running as a Local Service

Wireshark capture while the attack is happening

Let me know if you guys need a copy of the actual Wireshark capture (.pcap file) for analysis, I have no problem sending it out.

So what have I learned from this? Always double-check your new machine what applications are pre-installed on it, as well as ensure that unnecessary Services are not running on the background. This happened to me because I got lazy when the new Sony Vaio was handed over to me from work and I did not bother hacking into it like what I usually do with my personal machines.

Peace out and spread the word.





Monday, July 13, 2009

The madness stopped on the 4th day: My Comcast Hell


It took them 4 days in total, to resolve a simple physical connection problem. Turns out that my actual cable was disconnected. The apartment located on the 2nd floor got disconnected from their Comcast Service so someone from Comcast Provisioning disconnected them. They did not even check that the connection was originating from a splitter, one goes to the apartment on top of me, one goes to my apartment. They disconnected the entire cable feed. Another epic provisioning to on-site tech coordination FAIL.

My savior on my 4th day in fire and brimstone of zero Internet was a good-natured on-site tech guy named Tom. Tom was a classic good-ol'-American gentleman. He reminded me of those 1950's to 60's Handymen portrayed on television. He has a cool utility belt with all the tools he need, he has a cool mustache and beard, and sports an old-school baseball cap. He was a little bit odd with his seemingly non-sense gibbering while tracing the coax cables from my living room all the way outside the veranda but one thing is for sure, he knows his craft. He knows how to pacify someone who has been deprived of their connection for days by virtue of hard-work and results. Comcast Tech Support people should take a page out of Tom's book of work ethics.

All work, less talk. No promises.

Monday, July 6, 2009

My Comcast Hell Continues....

It has been 3 days now and my Comcast Cable Internet is still down. I guess that gives me the right (and pleasure) to say that Comcast Technical Support sucks, as well as how they coordinate with their local dispatch units that handles installation and on-site troubleshooting.

The thing is, Comcast Call Centers are distributed in North America and most of their on-site technicians are contractors, even better, sub-contractors. lol. Earth to Comcast, please stop hiring and giving out contracts to clueless companies to render service to your poor customers.

And one more thing, in case you call in Comcast Technical Support Hotline, ask them to transfer you to their Call Center based in Tucson, Arizona because the guys there will help you. The rest are plain stupid, newbies, too old to do technical support jobs, or just completely clueless.

I was in a hurry to go home today so I can meet the Comcast tech guy at 6PM PST, as promised over the phone yesterday by another clueless Supervisor. So around 5:45PM PST they called me and I told them to wait for just at least 5 minutes, 8 minutest tops, because I am already on my way to my apartment walking, coming from the BART station.

You know what was the reply of the guy who called me representing Comcast?

"Sorry, but we cannot wait because we have other job orders pending today." And that was it.

OMFG. I have been patiently waiting for the past 3 days for them to restore my Internet service, and the freakin' on-site Tech Guys couldn't even wait for just 10 minutes for a customer who has been down for 3 days?!

How I wish Comcast Managers can read my post. You guys gave me a new definition for ultimate customer service FAIL.

Have a goodnight Comcast people.

Saturday, July 4, 2009

Sorry Comcast, but first impression lasts!




So I just moved to a new apartment. The place is totally empty, I have no furniture yet except for my laptop, HD LCD and game console. That's it. My clothes are still inside my traveling bags even, and yes, I am sleeping on the carpeted floor, reminds me of my college years.

So whats the very first thing I worked on on my first day at the new spot? Yes, you got it, Internet. I am nothing without Internet, the rest of the bare necessities can wait.

In reading the Apartment Lease form, I saw a big Comcast Cable Service Ready smack at the bottom of the document. Turns out Comcast has first dig on the apartment complex, AT&T can't touch the area for some reason. So I immediately called the courteous guys at Comcast and in a couple of minutes a technician is already installing the Cable Internet. He brought a used Modem with a big Comcast logo on it, I said fuck it, I don't mind if its used, as long as its working right. So after a few minutes, Coax Cable on wall to the back of the Modem is installed. Ethernet Cable plugged it, and I politely asked the tech guy if I can hook it up at the back of my laptop already so we can test it. He said "Ok but its not up yet, I need to call to get it provisioned, but yeah you can hook it up because I need to check on it as well."

After hooking up the modem I immediately launched the terminal console on my Macbook to check what IP the gray box is giving me. The box was on a default gateway IP address 192.168.0.1, immediately opened my Firefox 3.5 and headed straight to it. The modem has a web-based configuration access but there is nothing we can do currently because it still needs to be provisioned. The tech guy said "Hmm, so you know how to do this huh?" I said, yeah only a little. This guy definitely needs to look around my empty living room because right next to us are scattered Cisco and CISSP books, lol.

The tech guy made a few calls on his NexTel phone, and after like 10 to 15 minutes, modem was up and operational, signal was good, and firmware updated. I saw this with my own eyes. The tech guy told me to do some speed tests, so he directed me to speedtest.net. The site testing gave me remarkable results, 15mbps download, 3mbps upload. Destination San Jose, from my place in Union City. Perfect. He told me that's Powerboost baby, but since you are not signed up for it, you may only get something like around 8mbps down, and 2mbps up. So I said, ok, its cool, still more than sufficient for my needs. Signed the papers that service was installed and working properly, a few chit-chat, tech guy left.

Everything was doing good till the next day, the freakin' Cable Internet went out on me. Multiple calls to their 24x7 Support Department wasn't fruitful, they could not even tell remotely from their Support Contact Center if there is a problem with the line or the modem. The first tech support guy that I spoke with told me I need to pick up a replacement modem, for free of course, but turns out I need to drive all the way to their office in Fremont or Hayward. Fuck that, its freaking far. So I told them I'd rather go to Radio Shack because Its right next to my place, all I need to do is walk.

So I asked the guys at their Technical Support Department, Supervisors included, what is my assurance that once I go out and spend like 40 to 60 bucks on a cable modem, swap it, that it will fix the problem?! Their answer? NONE. If its not a modem issue, I'm negative 60 bucks, if its a line issue, they can only send in an on-site tech guy on Monday, because of the long weekend. WTF. Another epic FAIL in customer service.

So I made a call again to their Support Department next day, 2nd day of my outage, made a plea of my case, and finally, they told me they will send in a tech guy on-site to check on the modem. The tech guy will bring a modem so he can swap it out. So I said yes, finally progress, and a sign of true customer service. But turns out there was a catch to it. If it turns out to be a line problem, cable problem, etc, or anything aside from the the modem being the source of the problem, they will charge me $46.00+ for the on-site service. Wow. The rabbit hole gets deeper. But the courteous lady tech support told me, I can avoid the service charge If I sign up for the 99 cents monthly service fee to cover such similar issues. Wow, another can of crap opened right in front of me. I politely replied to the support lady that I will not sign up, just send someone out for heavens sake, I just signed up for your service, and its already out the next day. Do me a favor please.

So here I am, typing this blog, spilling my guts out in disgust to their service at Starbucks so I can be online, its $3.99 plus tax for 2 hours by the way. They told me to wait for the call somewhere between 1PM to 5PM PST. They will call me on my mobile phone before they drop by. So I said, fuck it, I'll give them another chance, or not.

Its almost 4:15PM PST, assuming they come and fix the problem today, what I am going to do is call first thing on Monday and cancel the service. I am switching to AT&T's DSL and Telephone Line service instead.

Ah, revenge, so sweet I can almost taste it. Sorry Comcast, but first impression lasts!

A playground for network security enthusiasts, innovators and early adoptors


Welcome to my blog, this is me thinking out loud about Voice over IP security (VoIP), managing and optimizing converged networks, Metasploit Framework, Cloud Computing, general security and privacy concerns, grappling adventures, and tuning my MKIV VW Jetta.

All inputs, feedbacks and violent reactions are welcome.

Packet Boy Perseus
Helping spread a positive image why we hack things.

About Me

I am an InfoSec Innovator, a Blue Ocean Seafarer and a Paul Graham Pupil.