Log4Shell announcement (CVE-2021-44228) #1238
Replies: 2 comments 5 replies
-
Hi Haarolean, |
Beta Was this translation helpful? Give feedback.
2 replies
-
Hello, any news with this topic |
Beta Was this translation helpful? Give feedback.
3 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
UPD: There have been discovered more log4j related CVEs, thereby we decided to get rid of log4j completely. The changes are present in
master
branch already, please consider pullingmaster
labeled image instead oflatest
. We'll publish a release containing these changed soon.As you might already know there's a vulnerability issue has been discovered within Log4j, called Log4Shell (CVE-2021-44228), which we use.
If you're using the app docker-way, you're not affected, since the jdk/jre we use for our image sets
log4j2.formatMsgNoLookups
totrue
.if you do build manually, via either jar or own docker image, consider running the app with
-Dlog4j2.formatMsgNoLookups=true
.Beta Was this translation helpful? Give feedback.
All reactions