STORM-3810: bumping log4j.version to 2.17.0 and disruptor.version to 3.4.4 (CVE-2021-44228, CVE-2021-45046) #3427
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Pac72 yeah I think this is good. thanks |
|
@Pac72 - can you upgrade to 2.17.0? |
Pac72
changed the title
|
@agresch - sure, done (y) |
|
@agresch Any idea when will the Storm version with this change be released? |
|
No, my team is currently busy on internal projects. |
openstack-mirroring
pushed a commit
to openstack/kolla
that referenced
this pull request
Jan 21, 2022
The Log4j version was bumped on GitHub [1] but it is still pending inclusion in a release of Apache Storm. Apply the alternative mitigation recommended by Log4j [2] of removing the JndiLookup class from the classpath. [1] apache/storm#3427 [2] https://logging.apache.org/log4j/2.x/security.html Change-Id: Ib3ecd73f9e39e320acb2c5f0962b8af9b1a817e9
openstack-mirroring
pushed a commit
to openstack/openstack
that referenced
this pull request
Jan 21, 2022
* Update kolla from branch 'master'
to d7dde0265383e2498cfec9420b1a35d1f754b47f
- Merge "Mitigate two Log4j vulnerabilities in Apache Storm"
- Mitigate two Log4j vulnerabilities in Apache Storm
The Log4j version was bumped on GitHub [1] but it is still pending
inclusion in a release of Apache Storm.
Apply the alternative mitigation recommended by Log4j [2] of removing
the JndiLookup class from the classpath.
[1] apache/storm#3427
[2] https://logging.apache.org/log4j/2.x/security.html
Change-Id: Ib3ecd73f9e39e320acb2c5f0962b8af9b1a817e9
openstack-mirroring
pushed a commit
to openstack/kolla
that referenced
this pull request
Jan 25, 2022
The Log4j version was bumped on GitHub [1] but it is still pending inclusion in a release of Apache Storm. Apply the alternative mitigation recommended by Log4j [2] of removing the JndiLookup class from the classpath. [1] apache/storm#3427 [2] https://logging.apache.org/log4j/2.x/security.html Change-Id: Ib3ecd73f9e39e320acb2c5f0962b8af9b1a817e9 (cherry picked from commit 448e4f5)
openstack-mirroring
pushed a commit
to openstack/kolla
that referenced
this pull request
Jan 25, 2022
The Log4j version was bumped on GitHub [1] but it is still pending inclusion in a release of Apache Storm. Apply the alternative mitigation recommended by Log4j [2] of removing the JndiLookup class from the classpath. [1] apache/storm#3427 [2] https://logging.apache.org/log4j/2.x/security.html Change-Id: Ib3ecd73f9e39e320acb2c5f0962b8af9b1a817e9 (cherry picked from commit 448e4f5)
openstack-mirroring
pushed a commit
to openstack/kolla
that referenced
this pull request
Jan 25, 2022
The Log4j version was bumped on GitHub [1] but it is still pending inclusion in a release of Apache Storm. Apply the alternative mitigation recommended by Log4j [2] of removing the JndiLookup class from the classpath. [1] apache/storm#3427 [2] https://logging.apache.org/log4j/2.x/security.html Change-Id: Ib3ecd73f9e39e320acb2c5f0962b8af9b1a817e9 (cherry picked from commit 448e4f5)
openstack-mirroring
pushed a commit
to openstack/kolla
that referenced
this pull request
Jan 25, 2022
The Log4j version was bumped on GitHub [1] but it is still pending inclusion in a release of Apache Storm. Apply the alternative mitigation recommended by Log4j [2] of removing the JndiLookup class from the classpath. [1] apache/storm#3427 [2] https://logging.apache.org/log4j/2.x/security.html Change-Id: Ib3ecd73f9e39e320acb2c5f0962b8af9b1a817e9 (cherry picked from commit 448e4f5)
openstack-mirroring
pushed a commit
to openstack/kolla
that referenced
this pull request
Feb 10, 2022
The Log4j version was bumped on GitHub [1] but it is still pending inclusion in a release of Apache Storm. Apply the alternative mitigation recommended by Log4j [2] of removing the JndiLookup class from the classpath. [1] apache/storm#3427 [2] https://logging.apache.org/log4j/2.x/security.html Change-Id: Ib3ecd73f9e39e320acb2c5f0962b8af9b1a817e9 (cherry picked from commit 448e4f5)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixing CVE-2021-44228 for 1.x-branch
Similarly to #3426, bumping log4j.version to 2.16.0 and consequently disruptor.version to 3.4.4 on 1.x-branch