-
Notifications
You must be signed in to change notification settings - Fork 103
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
[SECURITY] Upgrade log4j to 2.17.1 as a vulnerability workaround #445
Comments
azagniotov
added a commit
that referenced
this issue
Dec 30, 2021
azagniotov
added a commit
that referenced
this issue
Dec 30, 2021
Applied retroactive fix for tag: https://github.com/azagniotov/stubby4j/releases/tag/v7.3.3 and rebuilt stubby4j Docker image tags:
|
Applied retroactive fix for tag: https://github.com/azagniotov/stubby4j/releases/tag/v7.4.0 and rebuilt stubby4j Docker image tags:
|
Applied retroactive fix for tag: https://github.com/azagniotov/stubby4j/releases/tag/v7.5.0 and rebuilt stubby4j Docker image tags: v7.5.0
|
azagniotov
added a commit
that referenced
this issue
Jan 2, 2022
azagniotov
added a commit
that referenced
this issue
Jan 2, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This ticket is related to #416 and #433 and is to capture PRs made as a result of changes advised by the Apache Foundation in https://logging.apache.org/log4j/2.x/security.html#log4j-2.17.1 as part of workaround to the recently discovered vulnerabilities in log4j
v2.x.x
. This ticket enhances the #267To address:
The text was updated successfully, but these errors were encountered: