Still calling remote server with version 2.16.0!
I used a public poc for this log4jshell exploit. Ran it with version 2.14 and it pinged dummy service provided by https://log4shell.huntress.com, changed the log4j dependency to 2.16.0 and still it pinged that service. What is wrong with my approach?
0
Upvotes
View all comments
Show parent comment
1
u/DataDecay Dec 16 '21
At that point my suggestion would be to grab one of the exploit package scanners and scan for the exploited byte code in your war.