-
Notifications
You must be signed in to change notification settings - Fork 285
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
fix(tools/quorum-all-in-one): address CVE-2021-36159 and CVE-2022-28391 #2240
fix(tools/quorum-all-in-one): address CVE-2021-36159 and CVE-2022-28391 #2240
Conversation
Hello @petermetz , Most of the vulnerabilities are now fixed in quorum-all-in-one but there are still some that are not because most of the remaining vulnerabilities are still new and is still waiting for the new changes to be pulled in and released on their respective package versions. And we tried to ask on the quorum discussions on github as you can see here. (Consensys/quorum#1513). Here are the remaining vulnerabilities for quorum-all-in-one: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aldousalvarez Please fix the container build, right now it's broken.
f47a286
to
fc2b35f
Compare
Fixed the container build and is now passing |
fc2b35f
to
59ed0fe
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@aldousalvarez Thank you, LGTM
59ed0fe
to
77bddb7
Compare
Other, lower severity vulnerabilities are also being addressed by this change but the two big ones are the critical severity ones mentioned in the commit subject. Most of the vulnerabilities are now fixed in quorum-all-in-one but there are still some that are not because most of the remaining vulnerabilities are still new and is still waiting for the new changes to be pulled in and released on their respective package versions. And we tried to ask on the quorum discussions on github as you can see here. (Consensys/quorum#1513). Here are the remaining vulnerabilities for quorum-all-in-one: CVE-2022-3602 CVE-2022-3786 CVE-2022-3602 CVE-2022-3786 CVE-2022-42003 CVE-2022-42004 CVE-2022-45868 CVE-2022-1471 CVE-2022-21698 CVE-2022-27664 CVE-2022-32149 CVE-2022-21698 CVE-2022-27664 CVE-2022-32149 Fixes hyperledger-cacti#2059 Signed-off-by: aldousalvarez <aldousss.alvarez@gmail.com> Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
77bddb7
to
df6be48
Compare
…rledger-cacti#2411 fixes: hyperledger-cacti#2411 related to: hyperledger-cacti#2240 and hyperledger-cacti#2274 Signed-off-by: ruzell22 <ruzell.vince.aquino@accenture.com>
…rledger-cacti#2411 fixes: hyperledger-cacti#2411 related to: hyperledger-cacti#2240 and hyperledger-cacti#2274 Signed-off-by: ruzell22 <ruzell.vince.aquino@accenture.com>
…rledger-cacti#2411 fixes: hyperledger-cacti#2411 related to: hyperledger-cacti#2240 and hyperledger-cacti#2274 Signed-off-by: ruzell22 <ruzell.vince.aquino@accenture.com>
Other, lower severity vulnerabilities are also being addressed by this
change but the two big ones are the critical severity ones mentioned
in the commit subject.
Most of the vulnerabilities are now fixed in quorum-all-in-one but
there are still some that are not because most of the remaining
vulnerabilities are still new and is still waiting for the new changes
to be pulled in and released on their respective package versions.
And we tried to ask on the quorum discussions on github as you can
see here. (Consensys/quorum#1513).
Here are the remaining vulnerabilities for quorum-all-in-one:
CVE-2022-3602
CVE-2022-3786
CVE-2022-3602
CVE-2022-3786
CVE-2022-42003
CVE-2022-42004
CVE-2022-45868
CVE-2022-1471
CVE-2022-21698
CVE-2022-27664
CVE-2022-32149
CVE-2022-21698
CVE-2022-27664
CVE-2022-32149
Fixes #2059
Signed-off-by: aldousalvarez aldousss.alvarez@gmail.com
Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com