supplied directly by the client, without escaping. Therefore, it is possible for malicious clients to insert control-characters in the log files, so care must be taken in dealing with raw logs.
What is the preferred solution of this problem?
Hahahaha WHAT
Don't cat logs I guess
Sounds familiar 🤔 log4j?
use Nginx? Do they state same in the docs?
log4j vulnerability was about recursive evaluation of templated log strings. This is simpler - client puts something weird in user agent or requested URL and this messes with your terminal or software you use to parse logs.
If I were to change software every time it did something incorrectly, I'd run out of software very quickly 😅
Обсуждают сегодня