News for hackers. Stuff that matters.
Re:CISA Director on Log4j Vulnerability by PeterisP on Sunday December 12, 2021 @09:56AM (#29530105)
The devil is in the details. As a random example, you might have a process where all the pre-WAF requests (or explicitly the requests blocked by WAF) get forwarded to a log analysis system that itself uses log4j and is vulnerable, allowing the attacker to gain RCE in your monitoring infrastructure.

Also, blocking any request containing "{" is tricky - like, that's so generic that it's time-consuming to verify that it won't break anything, and it's very likely that JSON is used somewhere in that application traffic, so you can't simply do that.

Re:CISA Director on Log4j Vulnerability by Thorrez on Sunday December 12, 2021 @10:05PM (#29536131)
You could also have a log analysis system that displays logs in the browser and has an XSS vulnerability. So that bypass isn't unique to log4j.

> JSON

You could probably write a more advanced check than just "{" that would let most JSON through while still blocking the attack.