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
Hacking Articles Tips Tricks Videos Tutorials
Photo
Hacking Articles|Raj Chandel's Blog
Bounty hunter HackTheBox Walkthrough

Bounty hunter is a CTF Linux machine with an Easy difficulty rating on the Hack the Box platform. So let's get started and take a deep dive into disassembling this machine utilizing the methods outlined below. Pentesting Methodology● nmapExploitation● burp suitePrivilege Escalation● sshLevel: EasyTo begin, we'll perform nmap scan to look for open ports. As can be seen, two ports are open:22.80 is used to run the http service.nmap -sC -sV 10.129.95.166portal."vulnerable. ___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
Hacking Articles|Raj Chandel's Blog Bounty hunter HackTheBox Walkthrough Bounty hunter is a CTF Linux machine with an Easy difficulty rating on the Hack the Box platform. So let's get started and take a deep dive into disassembling this machine utilizing…
db.php file, nothing intruding was discovered.dirb http://10.129.95.166 -X .phpIt signifies that there is a database file available in which all of the data will be stored.ExploitationWe will now begin our exploitation procedure with the burp suite. Try to capture its data by submitting a request for a more in-depth investigation. As a result, we used similar strategies on the beta version of the Bounty Report submission page.dbserver = "localhost"https://blogger.googleusercontent.com/img/a/AVvXsEjInj-7vYOrJo1AqARhb4NB2EjGu-RT4Mno6bkmTSo1YhHe-CReG5sbFI9tmWTxzWFmcy1Pv01pSHzY1KLunoXzeBVoXePHxAyYndd1bWur52vFbE9EL0AFq72QpRcZ2MhgiDiME9eDhSCtC7oBxQ_NtNeeXfoPEbiibjkDkc0-SdYNZ23awnus3YOB8g=s16000 /etc/passwdfile using this mechanism must obtain its encoded value in order to request this file from the target machine.development.___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
db.php file, nothing intruding was discovered.dirb http://10.129.95.166 -X .phpIt signifies that there is a database file available in which all of the data will be stored.ExploitationWe will now begin our exploitation procedure with the burp suite. Try to…
iCy-m23hkwDzGn8KmsPU9zgSho232Y3BPBpK7zNv-1nAT8A-Pss2IvEDLVGCs_duYdztfx9glQwc6Ox0abCbpT76k4SKfBWs1xaCahWFK84bWDXg9hbg=s16000 Privilege EscalationWe have credentials, and we know that ssh is operating on port 22. Now is the optimal moment to begin the privilege escalation process using an ssh login with the password which we got earlier.ssh development@10.129.95.166We successfully logged into the development and immediately we checked its id to verify its details. Searching for a little bit we found the user flag.cat user.txthttps://blogger.googleusercontent.com/img/a/AVvXsEi12-lTXyxuz4WFFLIhTt9ZPfyyzDQLT7BjxotbJWcwMckNLR8heq7wSAKK4p5kiZLrzsGvqdE9xQUI3dvEjAre9NNDf0DtcRNgo6dswePFu_2hnngGLlo9W2TgIUGnHK2TfeGxhGeJIvoiSNN-0Mn2G5mI9vz1-eUFbauEmohKC7lylYQrlwxQ9hllaQ=s16000 sudo -lSo, we reviewed this file to analyse it, and we got some points, but nothing exciting came out of it.file.md).cat file.mdfile.md).sudo /usr/bin/python3.8 /opt/skytrain_inc/ticketValidator.pyYippee!! We found the root. We immediately went to the root directory and received our well-deserved root flag.Author: Shubham Sharma is a passionate Cybersecurity Researcher, contact LinkedInand Twitter.___________________________
@hacking_Attack
@Hacking_Video
Hacking Articles Tips Tricks Videos Tutorials
Photo
Black Hat Ethical Hacking
Log4j 2.17.1 out now, fixes new remote code execution bug

https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/Untitled-design-2-1.png Log4j 2.17.1 out now, fixes new remote code execution bugPost Views: 200 https://www.blackhatethicalhacking.com/wp-content/uploads/2021/08/BECOME-A-PATRON-AND-UNLOCK-EXCLUSIVE-VIDEOS-1.png Reading Time: 1 Minute
Apache has released another Log4j version, 2.17.1 fixing a newly discovered remote code execution (RCE) vulnerability in 2.17.0, tracked as CVE-2021-44832.
Prior to today, 2.17.0 was the most recent version of Log4j and deemed the safest release to upgrade to, but that advice has now evolved. Fifth Log4j CVE in under a monthMass exploitation of the original Log4Shell vulnerability (CVE-2021-44228) by threat actors began around December 9th, when a PoC exploit for it surfaced on GitHub.

Given Log4j’s vast usage in the majority of Java applications, Log4Shell soon turned into a nightmare for enterprises and governments worldwide.

While the critical risk posed by the original Log4Shell exploit is paramount, milder variants of the vulnerability emerged in Log4j versions, including 2.15 and 2.16—previously believed to be fully patched.

BleepingComputer earlier reported on four different CVEs impacting Log4j and one discovered in the ‘logback’ framework. After the discovery of a DoS flaw in version 2.16, the advice had swiftly shifted towards upgrading to version 2.17.0, deemed the safest of all.

But now a fifth vulnerability—an RCE flaw, tracked as CVE-2021-44832 has been discovered in 2.17.0, with a patch applied to the newest release 2.17.1 which is out.

Rated ‘Moderate’ in severity and assigned a 6.6 score on the CVSS scale, the vulnerability stems from the lack of additional controls on JDNI access in log4j.

“JDBC Appender should use JndiManager when accessing JNDI. JNDI access should be controlled via a system property,” states the issue description seen by BleepingComputer.
See Also: Complete Offensive Security and Ethical Hacking Course
“Related to CVE-2021-44832 where an attacker with permission to modify the logging configuration file can construct a malicious configuration using a JDBC Appender with a data source referencing a JNDI URI which can execute remote code.”

Checkmarx security researcher Yaniv Nizry claimed credit for reporting the vulnerability to Apache:
Stay tuned for a blogpost 😉 pic.twitter.com/D56WpVsuF3

— Yaniv Nizry (@YNizry) December 28, 2021
Nizry’s tweet quickly exploded in traffic, attracting remarks and memes from security experts and ‘victims’ of the ongoing log4j-patching fatigue.

“I hope this is a joke, I hope so much… #log4j,” tweeted one user in response.

“We are LONG past the point where the only responsible thing to do is put up a giant flashing neon sign that reads ‘LOG4J CANNOT BE FIXED, DO NOT USE IT FOR ANYTHING.'” taunted another.

Security expert Kevin Beaumont labeled the instance another “failed Log4j disclosure in motion” during the holidays.
See Also: Hackers start pushing malware in worldwide Log4Shell attacks Disclosed too soon?At the time of Nizry’s tweet, BleepingComputer did not see an official advisory or memo indicating the presence of an RCE bug in log4j 2.17.

The tweet itself contained no details about the vulnerability or how it could be exploited but, within minutes, led a pack of security pros and netizens to start investigating the claim.

Disclosing security vulnerabilities prematurely can lure threat actors to conduct malicious scanning and exploitation activities, as evident from the Log4Shell exploit leak of December 9th.


Marc Rogers, VP of cybersecurity at Okta first disclosed the vul[...]

___________________________
@hacking_Attack
@Hacking_Video