Book Image

Learn Ethical Hacking from Scratch

By : Zaid Sabih
5 (1)
Book Image

Learn Ethical Hacking from Scratch

5 (1)
By: Zaid Sabih

Overview of this book

This book starts with the basics of ethical hacking, how to practice hacking safely and legally, and how to install and interact with Kali Linux and the Linux terminal. You will explore network hacking, where you will see how to test the security of wired and wireless networks. You’ll also learn how to crack the password for any Wi-Fi network (whether it uses WEP, WPA, or WPA2) and spy on the connected devices. Moving on, you will discover how to gain access to remote computer systems using client-side and server-side attacks. You will also get the hang of post-exploitation techniques, including remotely controlling and interacting with the systems that you compromised. Towards the end of the book, you will be able to pick up web application hacking techniques. You'll see how to discover, exploit, and prevent a number of website vulnerabilities, such as XSS and SQL injections. The attacks covered are practical techniques that work against real systems and are purely for educational purposes. At the end of each section, you will learn how to detect, prevent, and secure systems from these attacks.
Table of Contents (24 chapters)
22
Discovering Vulnerabilities Automatically Using OWASP ZAP

Local file inclusion vulnerabilities

Local file exploits or vulnerabilities allow us to read any file that is within the same server as the vulnerability; even if the file exists outside the /var/www directory, we'll be able to read the information within it.

A vulnerability is critical because we can read any files, such as important files or password files. Also, if there are a number of websites on the same server and we managed to find a website that we're not targeting, then we might be able to access files related to the website that we're targeting and then further exploit the website from there.

We are going to exploit the vulnerability through the URL. So, usually in our code execution examples, we write the code in the textbox. Sometimes, we might find the code vulnerability in the URL, which will have keywords such as cmd.

The same old process continues...