Welcome back everybody and in this tutorial I will show you some of the basics of Burp Suite. How to intercept packets, how to view packets, how to view responses and so on and so on. This is also a great way for you to learn more about the packets themselves and learn more how an HTTP for example, GET requests or POST requests look like and when you will be seeing them.
If you find anything helpful in this post or funny, will you please leave a like because you will feel great helping other people find it?
So let’s first of all run our Burp Suite. So for that, just type in your terminal Burp Suite or you can run it through the applications right here. It will open up in the exact same way.
As we can see right here we get the message again. So just click ‘Okay’.
Here you just go on ‘Temporary project’, ‘Next’ and then ‘Start Burp’.
Every time you open the Burp Suite you will notice that under the proxy settings right here, the intercept is always on by the default.
So that would mean that if I go onto my Firefox for example, and try to load for example, twitter.com, it will never load it until I forward the packet or turn the intercept off.
So it is useful if you want to watch the packet. So we can see the first packet how it looks. So I requested this page with the protocol HTTP/1.1 the host is firefox.com and the user agent is Mozilla 5.0.
These is just my information since this is an HTTP request I am sending to the server. So we can forward it, but you will notice that there will be another packet.
So basically there will be a lot of packets that you will need to forward in order to get to the website. As we can see, even though I forward the first packet it is not still on the website itself. So let me just forward all of the packets.
Once you do not get any packet anymore, you should be loading the page.
As we can see there are lots of them since this is a big website.
In the previous video, we did the same with the virtual machine and you saw that I only needed to forward one packet in order to get to the page of my virtual machine.
But for now I had to forward several of them and right now I should have Twitter loaded.
As we can see it is not loading anymore. I forwarded all the packets and I received all of the responses from the server. Now, in order to check that you can go under ‘HTTP history’ and you will see right here all of the domains, all of the websites that you visited in the process of connecting.
Now, there are a bunch of these detect portals. You will always have them. You just want to find the website that you’re searching for and when you find that, you can see the response to all of your requests.
So here we have twitter.com which is the page that we searched for and here we can see the first request that we sent.
In order to check out the response on that request that we sent, you just click here on ‘Response’ and this is the response of the server.
And as we talked before, it is consisted of the head and body. So we have the head and with a bunch of set cookie options.
So basically this is just a body. Right here starts the body which is the HTML code.
But let me just find the set cookie option. Here it is.
So basically this is the option that I was talking about in the HTTP response video. This is the cookie that Twitter set for us in order to track our session.
So as we can see the option set – cookie and this is our cookie right here.
Now, there are a bunch of the things in the cookie as well as paths, domain, secure which means HTTP only, set cookie, max age, expires. It basically even says when does the cookie expire. So it expires on Monday 18th February 2019 which means it expires today on this time.
So that’s one of the things that we covered here. We can also have the status code which is 200 OK.
We successfully loaded the page so we got the status code 200. We can go down here and here start the HTML code of the page itself. So this is what we load.
It is basically a huge code so we don’t need to watch it since the website is quite big.
So that’s how you can check the request and the response of a certain packet.
You can go onto the POST. Here we have a POST request.
You can check the response right here. Here is the request.
Now, there are some of the options that we do not care about. For example, this is not really that important to us.
Now, what is important is let us turn the intercept on once again. Let’s say for example, I want to log in. Now, we said that the packet that we send with our username and password will be a POST request. So once I type here the username and the password, we should be sending the POST request to the website.
So let us try that. If I just type here anything and press here log in, you will notice that it is loading since we turned the intercept on.
But right here we have the packet that we want to send as a POST request. Here we can see the basic HTTP headers structure and here we can see user name or email four Ws and password five Ws. So we can see our packet from here.
If I forward it, it will send to server the username and email with this username and this password right here.
Now, if you for example turn the intercept off or forward this packet and forward a bunch of other packets, it will give us an error that ‘This account doesn’t exist’.
So you might be needing to forward a couple of packets. So we forwarded them all and it says ‘The username and password you entered did not match our records. Please double-check and try again.’
Now, let’s try to change that in the Burp Suite. Let’s change the packet itself. So let us just go back one page. We should go to the log in page once again.
Now, also I forgot to mention that using Burp Suite your internet might be slower and you will be loading pages a little bit slower than usually, but it is not a big deal.
Let’s just go twitter.com. Now, let us turn the intercept on once again and let us send again the same username and same password which is five Ws.
And if I click here ‘Log in’, it will continue loading since our intercept is off. Here is our packet and here let me try to change the username into four Bs.
As you can see four Bs and if I try to forward this packet and forward all of the other packets, it will still give us the wrong username and wrong password. But it will show that the username wasn’t four Ws it was four Bs.
As you can see right here without any interaction with the page itself through the web browser, we managed to change the username through our Burp Suite.
So that is another useful thing to know. It will be used later on in order for us to brute force websites. For example, you just add a password list and you change the packets as you forward them and it tries every different password instead of the password that you specified.
So we can turn the intercept off right now. And as I said before in order to check the websites that you visited, you can go to the ‘HTTP history’ or on to the ‘Target’. And here you can also see the websites that you visited.
Now, there are a lot of other options that I will show you later on. For now it is enough for you to understand that there is a request and response that you can check out in Burp Suite and also you can change the structure of packets. You can also delete some of the things. You can also change usernames and passwords.
For example, we go back to the login page and turn intercept on. Then if I just type here something once again, it doesn’t matter what the username and password is, we can see it is stuck.
And here the POST request with the username four Ws and password five Ws we can change for example, the user agent.
Now, if we delete this, we will no longer be sending our information to the server. We will not send basically what version of web browsers we are running and what operating system we are running. So it is good if you do not want the server to know some of the information about you.
So if you forward the packet, you will get some of the others. Forward them all.
So once it finishes, we get the same error.
But if we go right here and we go to the ‘HTTP history’ we basically just want to find the POST requests. And as you can see right here the difference between these two, this one was the previous one,
and this one was the one we sent right now,
is that the first one has the user agent which basically says that we are using Mozilla 5.0 Linux and the second one is the same request with the same username and same password, but we deleted the information about ourself.
So the server will no longer be getting the information about our browser and our operating system which is another layer of anonymity for you.
So that’s about it for this tutorial. These were just some of the basics and me showing some of the things for this program. We will continue in the next lectures and I hope I see you there bye.
Final Words From Jerry Banfield
Thank you very much for finishing this entire video. We are honored you’ve spent this time here. We’ve got a complete course I imagine you will love and enjoy named Master Ethical Hacking in 2019.
Already it’s got six different ethical hacking courses in it we imagine you will love and enjoy from several different instructors showing you the very best of ethical hacking.
You can get this forever bundle meaning when you buy it today, you get all the rest of the courses added for life. I intend to add at least 20 courses to this bundle over its lifetime, new courses every year.
This course in particular is Master Ethical Hacking in 2019. You just watched a video from it for free which we’ve given you to both sell you the course and to give you a part of the course that we hope is helpful for whatever you are doing.
When you buy the course, you also get to have answers to questions from ethical hackers that can help you with anything from the basics into the advanced challenges you run into.
I find as a student answers to questions from an instructor are the very most valuable part of a course. You get two different places, a Facebook group and a Discord Server to get answers to your questions.
Thank you very much for being here with us, we trust if you look around in the description on this video, you might even find resources that are more helpful to you than just buying the course by itself.
There may even be some specials and some deals in the descriptions you might really appreciate.
Thank you very much for watching this video. I’m Jerry Banfield, the founder of Uthena.
Our purpose is to give you the very best professional education possible on the most in-demand subjects both on Uthena and on YouTube.
We love you.
Thanks for watching this and I imagine I’ll see you again soon especially if you subscribe then you will be able to see more of these videos easy.
Where to Follow Jerry Banfield.
Will you please join us as a subscriber on YouTube and as a follower on Facebook by liking the page, because you made it this far in I’m imagining you will love continuing to see more of the same kind of videos from me each day.