Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update Infinispan image to 11.0.13.Final #326

Merged
merged 1 commit into from
Dec 17, 2021

Conversation

calohmn
Copy link
Contributor

@calohmn calohmn commented Dec 14, 2021

Update Infinispan to version with updated log4j (CVE-2021-44228). Using the non-native image since there are no native versions of the current Infinispan releases.

@calohmn calohmn added the Hono label Dec 14, 2021
@calohmn calohmn requested a review from ctron as a code owner December 14, 2021 16:08
@calohmn
Copy link
Contributor Author

calohmn commented Dec 15, 2021

The failed test is because of a missing log4j2.xml in the config map (needed by the non-native infinispan server image).

I'm currently checking whether changing the image here is needed at all. It isn't clear yet whether the used native server image is affected by the vulnerability.

@LOorts-Aloxy
Copy link

Infinispan version 11.0.13 is using version 2.15.0 which is still affected by (CVE-2021-45046). Maybe it's best to only update when infinispan updates to use log4j 2.16.0?

Signed-off-by: Carsten Lohmann <carsten.lohmann@bosch.io>
@calohmn
Copy link
Contributor Author

calohmn commented Dec 16, 2021

It seems the native image is not affected by the vulnerability. Nonetheless, I think we can do the update here and then switch again to the native image version which is supposed to be available again with the coming 13.0.4 version (using log4j 2.16.0 then). @sophokles73 WDYT?

@sophokles73
Copy link
Member

It seems the native image is not affected by the vulnerability

What information/analysis is this assessment based on?

If this assessment is correct, then I tend to agree with @LOorts-Aloxy that we could wait for 13.0.4 to be released and then do the upgrade in one go.

@calohmn
Copy link
Contributor Author

calohmn commented Dec 16, 2021

What information/analysis is this assessment based on?

Discussions in Infinispan chat and infinispan/infinispan-images#67.

@calohmn
Copy link
Contributor Author

calohmn commented Dec 17, 2021

No 100% clear statement there though, so merging this to be extra cautious and get the used version here off the radar. We can see this as an intermediate step en route to the 13.0.4 update, to be done once it is available.

@calohmn calohmn merged commit 638ebc2 into eclipse:master Dec 17, 2021
@calohmn calohmn deleted the PR/ispn_update branch December 17, 2021 08:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants