Hacking Articles Tips Tricks Videos Tutorials
468 subscribers
65.8K photos
15 videos
157 files
132K links
Exploit
Pentesting
Hacking
Red Team
Blue Team
Kali Linux
Bug Bounty
Black Hat
Cyber security etc

@Hacking_Video
@Hacking_attack
Download Telegram
A simple pure-Python network packet sniffer. Packets are disassembled as they arrive at a given network interface controller and their information is displayed on the screen. This application maintains no dependencies on third-party modules and can be run by any Python 3.x interpreter.
Installation

GNU / Linux
Simply clone this repository with git clone and execute the packet_sniffer.py file as described in the following Usage (https://github.com/EONRaider/Packet-Sniffer#usage) section. user@host:~/DIR$ git clone https://github.com/EONRaider/Packet-Sniffer.git

Other Systems
This project is dependent on PF_PACKET - a stateful packet filter not found on Windows or Mac OS X. For demonstration purposes, you can try out this package in a Docker container. Although it will not have full access to localhost on your machine, you can still sniff on the Docker subnet and at least get the module running. Use this command to build and run from the project directory: docker build -t sniff . && docker run --network host sniff
Note that the entry command is simply python packet_sniffer.py, so feel free to use the full functionality of the module by overriding the default command. Remember that we tagged the container (https://www.kitploit.com/search/label/Container) with the name "sniff" before, so we can pass command-line arguments to the sniffer in the following manner: docker run --network host sniff [your command goes here]
echo "Now let's print help"
docker run --network host sniff python packet_sniffer.py --help
Usage of --network host is not supported on OS X or Windows so this container won't be fully functional - but you will see packets traveling within the docker subnet.
Usage
packet_sniffer.py [-h] [-i INTERFACE] [-d]

A pure-Python network packet sniffer.

optional arguments:
-h, --help show this help message and exit
-i INTERFACE, --interface INTERFACE
Interface from which packets will be captured (captures
from all available interfaces by default).
-d, --displaydata Output packet data during capture.

Running the Application
Objective Initiate the capture of packets on all available interfaces Execution sudo python3 packet_sniffer.py Outcome Refer to sample output below Sample output: ] Packet #476 at 17:45:13: [+] MAC ......ae:45:39:30:8f:5a -> dc:d9:ae:71:c8:b9 [+] IPv4 ..........192.168.1.65 -> 140.82.113.3 | PROTO: TCP TTL: 64 [+] TCP ..................40820 -> 443 | Flags: 0x010 > ACK [>] Packet #477 at 17:45:14: [+] MAC ......dc:d9:ae:71:c8:b9 -> ae:45:39:30:8f:5a [+] IPv4 ..........140.82.113.3 -> 192.168.1.65 | PROTO: TCP TTL: 49 [+] TCP ....................443 -> 40820 | Flags: 0x010 > ACK [>] Packet #478 at 17:45:18: [+] MAC ......dc:d9:ae:71:c8:b9 -> ae:45:39:30:8f:5a [+] ARP Who has 192.168.1.65 ? -> Tell 192.168.1.254 [>] Packet #479 at 17:45:18: [+] MAC ......ae:45:39:30:8f:5a -> dc:d9:ae:71:c8:b9 [+] ARP ...........192.168.1.65 -> Is at ae:45:39:30:8f:5a ">[>] Packet #476 at 17:45:13:
[+] MAC ......ae:45:39:30:8f:5a -> dc:d9:ae:71:c8:b9
[+] IPv4 ..........192.168.1.65 -> 140.82.113.3 | PROTO: TCP TTL: 64
[+] TCP ..................40820 -> 443 | Flags: 0x010 > ACK
[>] Packet #477 at 17:45:14:
[+] MAC ......dc:d9:ae:71:c8:b9 -> ae:45:39:30:8f:5a
[+] IPv4 ..........140.82.113.3 -> 192.168.1.65 | PROTO: TCP TTL: 49
[+] TCP ....................443 -> 40820 | Flags: 0x010 > ACK
[>] Packet #478 at 17:45:18:
[+] MAC ......dc:d9:ae:71:c8:b9 -> ae:45:39:30:8f:5a
[+] ARP Who has 192.168.1.65 ? -> Tell 192.168.1.254
[>] Packet #479 at 17:45:18:
[+] MAC ......ae:45:39:30:8f:5a -> dc:d9:ae:71:c8:b9
[+] ARP ...........192.168.1.65 -> Is at ae:45:39:30:8f:5a

Legal Disclaimer

___________________________
@hacking_Attack
@Hacking_Video
The use of code contained in this repository, either in part or in its totality, for engaging targets without prior mutual consent is illegal. It is the end user's responsibility to obey all applicable local, state and federal laws. Developers assume no liability and are not responsible for misuses or damages caused by any code contained in this repository in any event that, accidentally or otherwise, it comes to be utilized by a threat agent or unauthorized entity as a means to compromise the security, privacy, confidentiality, integrity, and/or availability of systems and their associated resources by leveraging the exploitation (https://www.kitploit.com/search/label/Exploitation) of known or unknown vulnerabilities (https://www.kitploit.com/search/label/vulnerabilities) present in said systems, including, but not limited to, the implementation of security controls, human- or electronically-enabled. The use of this code is only endorsed by the developers in those circumstances directly related to educational environments or authorized penetration testing (https://www.kitploit.com/search/label/Penetration%20Testing) engagements whose declared purpose is that of finding and mitigating vulnerabilities in systems, limiting their exposure to compromises and exploits (https://www.kitploit.com/search/label/Exploits) employed by malicious agents as defined in their respective threat models.

Download Packet-Sniffer (https://github.com/EONRaider/Packet-Sniffer)

___________________________
@hacking_Attack
@Hacking_Video
Exploitation of file’s download parameters to create potential risk of malware delivery: $200 bug!

Hi Everyone,Continue reading on Medium »
Read more...
Business Logic Errors - A Logic Destruction

Summary :Continue reading on Medium »
Read more...
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking Articles|Raj Chandel's Blog
TheNotebook HackTheBox Walkthrough

We’ll look at another one of HackTheBox machines today, called “TheNotebook.” It is a medium difficulty box targeting commonly found threat of using insecure JWT token implementation. A user is able to gain access to the system by forging this token and adding desired values. We’d own the root user by targeting it. Here is the methodology. Penetration Testing Methodology· NmapExploitation· Forging the JWT token with admin rights and self-generated private keyPrivilege Escalation· Recovering SSH private key from an old backup directoryCVE-2019-5736)

· Gaining root accessReconMachine’s IP was 10.129.211.197. The first step was to run nmap’s aggressive scan to look for open ports. As you can see a port 80 was found to be open.nmap -A  10.129.211.197https://blogger.googleusercontent.com/img/a/AVvXsEhxStGsjlqoMdg-fqQAmSSYabLKUUB9WK0xjmsnCcz4Olhw2YiFzSgatbKkR5xOP_nrszkGgwv8HwCkODldvhGafKXbu1VuEQH5r2jD9dmeM_3tdWq8mx6AkfTD4AyBjOK29y1jsozULsC75S92ZNEvnXnKX1hOBIkHxzFyWfWNA9QYQyAbHvOjkMrxoQ=s16000 The website opens up a note management tool. There was a register link too.ExploitationSo, we’ll generate a private key, host it on our local server, and change the JWT header to my own key’s location and try if the website fetches and authenticates using our key.openssl genrsa -out privKey.key 2048https://blogger.googleusercontent.com/img/a/AVvXsEiKERiNvpDJYi_lkt_ByiJjfSgLcDTk4f31yDqOV-xI5NycZ2Y5VPDStdO1s7owotkJQl8bczUrzbFbiETOBafn9hY-M7xqrs0B-pANDBQr3l3i3zm2FW0oS01eRW0HGJYuyRMR-Dq9ujfMwtluCI23UdUzADJrHxjhjT3vqy5VyKJMyg37fPBgfsvvFw=s16000 We’d change the fields in our JWT header now and paste our own key in the field below for the token to verify the signature and successfully authenticate using my key.___________________________
@hacking_Attack
@Hacking_Video