As many of you know, on 9 December 2021, Apache disclosed via GitHub that the Log4j 2 utility contains a critical vulnerability that allows unauthenticated remote code execution, a serious issue that impacts a large number of applications.
Therefore, nocode should be adapted to deal with this 0-day issue that was aired 4 days ago.
Recommendations:
To secure your code against this vulnerability, upgrade your library to the newest version.
If you are unable to update your library, add the following in /dev/null:
""
You are welcome.
As many of you know, on 9 December 2021, Apache disclosed via GitHub that the Log4j 2 utility contains a critical vulnerability that allows unauthenticated remote code execution, a serious issue that impacts a large number of applications. Therefore, nocode should be adapted to deal with this 0-day issue that was aired 4 days ago. Recommendations:
To secure your code against this vulnerability, upgrade your library to the newest version. If you are unable to update your library, add the following in /dev/null:
""
You are welcome.