Explore tweets tagged as #log4Shell
🔥 #APTs in 2025 still abuse ProxyShell, Log4Shell, & Fortinet flaws. ⚠️ Patch or become a breach headline. 📖 Full Q1 2025 findings: #ThreatIntel #CyberAttack #StaySecure #APTs #CyberDefense #ZeroTrust #Cybersecurity #Kaspersky #Securelist #Linux
1
3
9
Our JFrog Senior Solution Engineers break down how to protect your applications this December and beyond. Learn key steps to safeguard your code and keep the on-call pager silent: #Log4J #CyberSecurity #Log4Shell #DevSecOps
0
0
0
🌐 Server-Side Bugs That Pay Big. • SSRF (internal request abuse).• SSTI (template injection).• XXE (XML Entity Injection).• Log4Shell-style payloads.• Blind bugs with Burp Collaborator. 💣 Quiet bugs, massive impact. #BugBounty #SSRF #EthicalHacking #bugbountytip.
1
11
96
When you see java.exe spawning weird child processes, it’s time to investigate. I will be doing a write-up of analyzing a Log4Shell payload via a memory dump!
Crafty from @hackthebox_eu is about exploiting a Minecraft server. I'll use an open source client to send a Log4Shell payload, and get a shell. Then I'll find admin creds in a custom plugin. In Beyond Root, I'll explore the web.config file.
0
14
96
Three years later, #Log4Shell is still a wake-up call. Thankfully JFrog experts, Richard Clark and Gabe Martino, demonstrate how you can create a Curation policy by leveraging the JFrog integration with @github's CoPilot. Get a refresher on the risks and actions you can take
0
0
1
I remember when Log4shell came out I used a canary as my attempted username in a game client and got a callback. Reported, had it patched in <24hrs and even though there was no formal bug bounty program they gave me some swag and a game. Always interesting to see this stuff 👏.
I use Log4shell canaries in my passwords and I have one per website. It’s been crazy interesting the sites that I have gotten pings for and where the pings are from. I think it’s cool. It would be a fun talk to put together and a good story to tell but not useful….
1
3
20