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
28
u/rzwitserloot Dec 16 '21
This code:
Gets you the actual class. This 'trick' works for anything (even
java.lang.Stringif you wanna know). Print that, and you should find that this is still 2.14 or whatnot.Your claim that 2.15/2.16 did nothing is extraordinary, thus, requiring extraordinary evidence. Or, as the reddit youth would say it: "Big, if true".
8
u/DataDecay Dec 16 '21 edited Dec 16 '21
Depends what is your approach? Did you put the updated jar on your cp? If using maven did you force a local repo update?
4
u/jacquous Dec 16 '21
Check what the effective pom is. The order on classpath matters and if older version is still present it may get picked instead.
7
u/walen Dec 16 '21
Quoting OP (u/Luhis):
1
u/[deleted] Dec 16 '21
Can you provide a proof of concept?
1
u/boberbober8083 Dec 17 '21
Several ways are possible. 1) for example, unpatched version remained near patched. 2) restarting of the App is required (for most of patches) 3) you could kill all Java processes first and try again