Hotfix for log4j 1.2.7 security vulnerability (CVE-2019-17571) #4468
-
Hello. Kafka is still using log4j 1.2.7, in turn with its security vulnerability. I have been working on this problem and recently started to provide a preview patch and custom distribution for Apache Kafka 2.7.0. Some Kafka users consulted me that if they can use this preview with strimzi kafka operator. It seems like it is using some docker image, but I can't guess how to provide a custom docker image for it. Could anyone guide me? As a note, here is a examplar custom docker image of it (dongjinleekr/kafka:2.13-2.7.0-log4j2-0) compatible with wurstmeister/kafka-docker. I hope there is any way to provide similar one. |
Beta Was this translation helpful? Give feedback.
Replies: 4 comments 6 replies
-
Strimzi does not work with any Kafka container image. It has its own images which are not the same as lets say Confluent platform or Wurstmeister. The general way how to use a custom Kafka build would be to change the URL and checksum in this file to point to your distribution and build the whole Strimzi project. That said, I'm not sure how well it would or would not work. The operator has built in logic around logging configuration which expects Log4j 1 right now and I have no idea how well it would or would not work if your version has now Log4j2. Maybe @sknot-rh would know? He did most of the work around logging. PS: We are definitely following the progress around Log4j 2 ... thanks for working on it. |
Beta Was this translation helpful? Give feedback.
-
Since this preview is backward-compatible, it perfectly works with log4j configuration unless it uses a feature removed in log4j2. log4j2 mode is activated only if the user specifies Of course, there may be unexpected consequences, and this preview aims to prepare the update and detect implicit bugs beforehand. It seems like activating this preview build is available by only changing the download URL and md5 checksum. Although I am preparing the 2.6.0 patch and preview guide now, here is the download link and md5 checksum for who needs this feature right now. Thanks for the answer, and praise the Strimzi team! 😄
|
Beta Was this translation helpful? Give feedback.
-
Here is the guide: https://home.apache.org/~dongjin/post/apache-kafka-log4j2-support/ |
Beta Was this translation helpful? Give feedback.
-
Long time no see. Previews & custom patches for [2.6.1, 2.8.0] have been released. (3.0.0 based preview will be released as soon as the official 3.0.0 is released.) Please refer here to download them. |
Beta Was this translation helpful? Give feedback.
Strimzi does not work with any Kafka container image. It has its own images which are not the same as lets say Confluent platform or Wurstmeister. The general way how to use a custom Kafka build would be to change the URL and checksum in this file to point to your distribution and build the whole Strimzi project.
That said, I'm not sure how well it would or would not work. The operator has built in logic around logging configuration which expects Log4j 1 right now and I have no idea how well it would or would not work if your version has now Log4j2. Maybe @sknot-rh would know? He did most of the work around logging.
PS: We are definitely following the progress around Log4j 2 ... thanks fo…