Wednesday, February 8, 2012

Aireplay-ng


Aireplay-ng


Aireplay-ng is my favorite tool of all. It has a variety of functions but all of them are used to speed up attacks.


Different attacks:


Usage:

aireplay-ng <options> <interface>

Here are some basic options. More options will be covered with each specific attack. (replay attacks require different options)

·        -b         BSSID
·        -s         source MAC

I will be posting each attack on its own.

Tuesday, February 7, 2012

Using airodump-ng


Airodump-ng


Airodump-ng is primarily used for capturing 802.11 frames over the air. Airodump-ng displays APs and STAs of nearby networks.

usage: airodump-ng <options> <interface>

Common options:

Options:
Description:
-w       
writes output to specified file in pcap format
- -bssid           
filters APs for specified BSSID
-c        
filters out networks for a specified channel


Airodump-ng output is filled with a lot of useful information about discovered networks. Notice the example output below:



In the header fields you will notice the channel, elapsed time and date. If you do not specify the channel, airodump-ng will hop channels.

The upper half shows the APs that have been discovered. Here are the descriptions of the fields shown:

BSSID: MAC of the AP.

PWR: Signal strength of the AP. (-25 is a strong connection where -80 is weak)

Beacons: # of beacons the AP sends.

#Data: Amount of captured data packets. This is also the number of IVs if you are attacking WEP.

#/s: Data packet captures per second

CH: Channel the AP is operating on.

MB: Speed that AP supports.

ENC: Type of encryption the AP is using. Options include: OPN, WPA, WPA2, WEP, WEP? (encryption but not enough data to specify)

CIPHER: The cipher used for encryption

ESSID: Broadcasted name of the AP. If hidden, this field will provide the ESSID length or remain empty.

The lower half of the airodump-ng output displays the connect STAs.

            STATION: MAC of the STA.

            Rate: Speed that the STA supports.

            Lost: Amount of packets lost by the STA over the last 10 seconds.

            Packets: Amount of packets sent by the STA.

            Probes: The ESSID probed by the STA.


Airodump-ng is going to be used for almost all of our wireless attacks. Get familiar with the tool and its output fields.


See the airodump-ng video for more practical usage and tips on using airodump-ng.






Using Airmon-ng


Airmon-ng



Airmon-ng is a tool that is used to enable or disable monitor mode on your wireless interface.

usage: airmon-ng <start|stop> <interface> [channel] or airmon-ng

Where:
  • <start|stop> indicates if you wish to start or stop the interface. (Mandatory)
  • <interface> specifies the interface. (Mandatory)
  • [channel] optionally set the card to a specific channel.

For all wireless attacks it is necessary to put your card in “monitor mode”. Monitor mode allows your computer to monitor all wireless traffic over your wireless interface. (note that not all wireless chipsets support monitor mode)

After you set your wireless interface in monitor mode, airmon-ng will create a virtual access point (VAP), often called mon0, on your computer. The interface mon0 will be the interface we call upon in later attacks.

            To attack a specific network, you may want to put your card in monitor mode on a specific channel. To do this, tear down your previous VAP and start a new one on the desired channel.



Example:



Assumptions: Your alfa card is plugged in and is shown as ‘wlan0’.

Verify using the iwconfig command. (iwconfig shows your wireless extensions)

 iwconfig



Set your alfa card in monitor mode using airmon-ng.



airmon-ng start wlan0






Run iwconfig or airmon-ng to see your new virtual interface ‘mon0’. (Note that wlan0 still exists)






Tear mon0 down using airmon-ng.


airmon-ng stop mon0


Run iwconfig again and notice that your mon0 interface is gone, but your wlan0 still exists.

To start your wireless card in a specific channel, simply put the channel after your interface.

airmon-ng start wlan0 6



 airmon-ng video:


Wireless Attacks w/ aircrack-ng

One of my teachers asked if I could assemble some videos and lab manuals discussing wireless cracking techniques. I will be posting my writings and videos on my blog. To start out, I decided it was best to go over basic attacks and aircrack-ng usage. After I establish the fundamentals, I plan to dive into different wireless cracking scenarios. I hope you find it useful. Please add comments or ideas for new attacks.

For my videos I will be using Backtrack 5 R1, an Alfa AQUS051NG wireless card, and a Linksys WRT54GL as the victim AP.

Monday, January 30, 2012

Xbox 360 controller mod: rapid fire

With my newly fixed controller I decided to take it a step further and try out a mod. The rapid fire mod is used mostly for CoD and allows a semi-auto weapon to be fired at the rate of a fully automatic weapon.

The mod itself is simple. You need a button, some wire, a solder iron, a drill, and steady hands.



Looking at the board, we will be soldering two points. The point on the left is where we get will get power to our button. The point is where the vibrating component connects and is the one furthest right. Because this is the vibrators power, we can only use the button when the controller vibrates. However this won't be an issue because the controller will vibrate everytime we shoot.

The second point is for the right trigger button. There are 3 points in a row, I want the middle one.


Now that we know where our wires will be going, we need to find a location for our button. I chose to put it on the lower right handle portion of the controller. This made sense because there is a lot of room and it is going to be near our solder points. Since I chose this location however, I cannot have both vibrators in. I kept the smaller one because it vibrates the most. When choosing a location I kept the board in so I know everything will fit at the end.
To make the hole for the button I drilled a hole in the appropriate location. My button came with a nut and washers so it mounted easily to my case.




The next step was to solder the two wires to my button. I kept the wires a little long so they are easier to work with. After that I mounted the button to my case and put the board in to begin soldering.


I cut the wires small so that they didn't get in the way of the other components of the controller. When soldering to the controller be very careful. If you are careless you can ruin the controller. With the solders done and the button attached I can begin putting the controller back together.

Putting the controller together after the mod is really frustrating. The button will fit but you have to force it in. I had to remove some of the internal parts of the case to allow room for the button. After everything was done the controller worked great. Fully functional and the mod was a success.

Xbox 360 controller revive

I got an old, broken xbox 360 controller and time to kill.

After plugging it in, I noticed the buttons are all sticky and the "a" button doesn't even work. The plan is to take it all apart and clean it. Possibly get the "a"button working again?




Trying to remove the outside case is harder than it looks. The screws require a special bit to remove them. However, I was able to get them off with a 2mm flat head screw driver. There are 7 screws all located on the back of the controller. One of them is hidden beneath the barcode sticker where the battery pack lays.




After removing all the screws, the back casing came off easily. I was able to take off the top and bottom pieces. At this point I also removed the two connectors holding the components on the lower left and lower right. These components vibrate the controller and make removing the board easier if they are off.






Removing the board is a little tricky. I was able to pry it loose by pushing in the xbox guide button and removing the front case. The part that struggles the most is getting the anolog sticks to come free. It works best if you pull it off straight.








Remove the rubber cups beneath the buttons and continue to remove the buttons themselves. Everything will come out freely except for the d-pad.











  Removing the d-pad requires a little more work but is simple. On the backside you will notice two screws and two tabs. Remove the two screws with a small philips screw driver. Once the screws are removed you have to push out the tabs. I used to small screwdrives to push the tabs outward, releasing the d-pad.







 With everything completley disassembled I can start cleaning. I soaked all the buttons and the case in a bucket of warm water. With a q-tip and some rubbing alcohol I was able to get all the sticky stuff off the buttons. I used tweezers to get all the hair off of the board...I'm not really sure how it got there though??  Once it was clean I put it together and tested the controller. Everything was working smoothly except for the "a" button.




To troubleshoot I connected the board and tried to locate the problem. After a while, I found out that the rubber cup was the issue. I needed a new rubber cup for the "a" button. I was able to dig up an old ps2 controller and grab a rubber cup from it.
I used a utility blade to cut off the bad rubber cup. The new rubber cup fit perfectly and was working great while I had it apart. When I put it all back together it was a different story. The rubber cup was free to move around so the button would only work if it was aligned correctly. I need a solution to keep the rubber cup in placed.

To solve the issue I tried to tape the two rubber pieces together. This worked but was only temporary and not good enough for me.  Because the rubber cup was from a ps2 controller it was thicker and didn't fit under the xbox button nicely. I put the original ps2 button on it so it stayed snug and in place. The only problem is the ps2 button is significantly shorter than my xbox buttons. On the left you can see how I stacked the two bottons compared to the original xbox button layout. It worked great but was a little too tall so I cut took about an 1/8'' off the "a" button.

After putting it all together, every button worked smoothly and I was ready to game!















Thursday, January 26, 2012

My Blog

I am new to the whole idea of blogging. I started this blog to share my knowledge, and perhaps more importantly, keep an archive of the random projects I take on in info sec. More to come..