Apache Log4j (few versions) did not protect from uncontrolled recursion from self-referential lookups. When the logging configuration uses a non-default Pattern Layout with a Context Lookup (for example, $${ctx:loginld}), attackers with control over Thread Context Map (MDC) input data can craft malicious input data that contains a recursive lookup, resulting in a Stack OverflowError that will terminate the process. Further, the log4j security vulnerability allows attackers to execute malicious code remotely on a target computer. Meaning, bad actors (hackers) can easily steal data, install malware, or simply take control of a system via the Internet. Assume one of your cloud server, a critical resource serving to most of your clients is running the vulnerable version of Log4j. Design a solution to mitigate the situation and verify the same before any infection.