Explore tweets tagged as #Log4Shell
Remember Log4Shell? That wasn't just a Java bug!. Millions of apps still vulnerable to payload injection through serialized data. @three_cube
0
3
11
Think your app is safe? Think again. Insecure deserialization is an OWASP Top-10 web riskβremember Log4Shell? .Millions of applications are still exposed. @three_cube .@_aircorridor
0
4
5
Millions lost. Servers hijacked. All because of overlooked code patterns, you might still have today. @vilojona reveals the unseen traps. Are you truly protected against SQLi, #Log4Shell & deserialization hacks?. Decode it here: #DevSecOps #SQLInjection
0
1
1
Think your code is safe? So did #Tesla. π¨ @vilojona uncovers the top attacks hiding in your code right now - and how a single mistake can cost you everything. Can you spot the flaw before hackers do?. Find out: #Java #DevSecOps #Log4Shell #SQLInjection
0
3
3
How to exploit this π€π€ LOG4SHELL .any tips. #hackerone #BugBounty #bugbountytips #intigriti #bugcrowd #infosec
2
0
35
Dodge WAFs and detection mechanisms by mastering payload obfuscation π₯·. Level up your #BugBounty skills with encoding, variable expression, array parameter and shell-environment techniques, plus a look at how Log4Shell evaded defences π.
1
22
92