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

fix: GHSA-8qv2-5vq6-g2g7 webpki CPU denial of service in certificate path #2917

Conversation

petermetz
Copy link
Contributor

  1. Upgraded tonic, prost and tokio to the latest and greatest of versions
    which was necessary because one of their transitive dependencies being
    affected by the GHSA-8qv2-5vq6-g2g7 vulnerability.
  2. These upgrades also forced our hand in terms of bumping up the
    rust edition from 2018 to 2021 and upgrading the rust compiler to v1.74.

Depends on #2916 (which upgrades
the rust compiler in the dev container)

Signed-off-by: Peter Somogyvari peter.somogyvari@accenture.com


Pull Request Requirements

  • Rebased onto upstream/main branch and squashed into single commit to help maintainers review it more efficient and to avoid spaghetti git commit graphs that obfuscate which commit did exactly what change, when and, why.
  • Have git sign off at the end of commit message to avoid being marked red. You can add -s flag when using git commit command. You may refer to this link for more information.
  • Follow the Commit Linting specification. You may refer to this link for more information.

Character Limit

  • Pull Request Title and Commit Subject must not exceed 72 characters (including spaces and special characters).
  • Commit Message per line must not exceed 80 characters (including spaces and special characters).

A Must Read for Beginners
For rebasing and squashing, here's a must read guide for beginners.

@sandeepnRES
Copy link
Contributor

@petermetz build for relay is failing. Can we hold the PR merge, I'll try to fix this in this PR itself.

@sandeepnRES sandeepnRES force-pushed the fix-ghsa8qv25vq6g2g7_webpki_cpu_denial_of_service_in_certificate_path branch 2 times, most recently from e36e5ba to d989691 Compare December 14, 2023 09:32
@sandeepnRES sandeepnRES disabled auto-merge December 14, 2023 09:33
@sandeepnRES sandeepnRES force-pushed the fix-ghsa8qv25vq6g2g7_webpki_cpu_denial_of_service_in_certificate_path branch from d989691 to b50bd82 Compare December 14, 2023 11:44
Copy link
Contributor

@jagpreetsinghsasan jagpreetsinghsasan left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Copy link

This PR/issue depends on:

…path

1. Upgraded tonic, prost and tokio to the latest and greatest of versions
which was necessary  because one of their transitive dependencies being
affected by the GHSA-8qv2-5vq6-g2g7 vulnerability.
2. These upgrades also forced our hand in terms of bumping up the
rust edition from 2018 to 2021 and upgrading the rust compiler to v1.74.
3. fix(relay): update the code for tonic 0.10.2
4. fix(relay): upgrade rust docker image tag to 1.69.0

Depends on hyperledger-cacti#2916 (which upgrades
the rust compiler in the dev container)

Co-authored by: Sandeep Nishad <sandeep.nishad1@ibm.com>

Signed-off-by: Peter Somogyvari <peter.somogyvari@accenture.com>
Signed-off-by: Sandeep Nishad <sandeep.nishad1@ibm.com>
@sandeepnRES sandeepnRES enabled auto-merge (rebase) December 19, 2023 19:10
@sandeepnRES sandeepnRES force-pushed the fix-ghsa8qv25vq6g2g7_webpki_cpu_denial_of_service_in_certificate_path branch from b50bd82 to ed5267e Compare December 19, 2023 19:10
@sandeepnRES sandeepnRES merged commit e24458f into hyperledger-cacti:main Dec 19, 2023
43 of 63 checks passed
@petermetz petermetz deleted the fix-ghsa8qv25vq6g2g7_webpki_cpu_denial_of_service_in_certificate_path branch December 21, 2023 07:45
@petermetz
Copy link
Contributor Author

@petermetz build for relay is failing. Can we hold the PR merge, I'll try to fix this in this PR itself.

@sandeepnRES Yes, of course, sorry for the slow response! I know it doesn't matter now that it's all been resolved ,but wanted to make sure I say it that it would've been totally fine to hold it because of a dependency like that.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants