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.

Sign up for GitHub

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

Jump to bottom

gh: address CVE-2022-32149 #10334

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

gh: address CVE-2022-32149 #10334

wants to merge 1 commit into from
+71 −1

Conversation

mfrw
Copy link
Member

@mfrw mfrw commented Sep 4, 2024 •
edited
Loading

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

  • The toolchain has been rebuilt successfully (or no changes were made to it)
  • The toolchain/worker package manifests are up-to-date
  • Any updated packages successfully build (or no packages were changed)
  • Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
  • Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
  • All package sources are available
  • cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
  • LICENSE-MAP files are up-to-date (./LICENSES-AND-NOTICES/SPECS/data/licenses.json, ./LICENSES-AND-NOTICES/SPECS/LICENSES-MAP.md, ./LICENSES-AND-NOTICES/SPECS/LICENSE-EXCEPTIONS.PHOTON)
  • All source files have up-to-date hashes in the *.signatures.json files
  • sudo make go-tidy-all and sudo make go-test-coverage pass
  • Documentation has been updated to match any changes to the build system
  • Ready to merge
Summary

What does the PR accomplish, why was it needed?
gh: address CVE-2022-32149

Change Log
  • gh: address CVE-2022-32149
  • Fix changelog which was corrupted due to a merge conflict
Does this affect the toolchain?

NO

Associated issues
  • NA
Links to CVEs
Test Methodology

@mfrw mfrw added the security label Sep 4, 2024
@mfrw mfrw marked this pull request as ready for review September 4, 2024 07:30
@mfrw mfrw requested a review from a team as a code owner September 4, 2024 07:30
@mfrw
gh: address CVE-2022-32149
12e51bc 
Signed-off-by: Muhammad Falak R Wani <[email protected]>
mfrw
mfrw commented Sep 19, 2024
View reviewed changes
Copy link
Member Author

@mfrw mfrw left a comment

Choose a reason for hiding this comment

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

rebased to address merge conflict

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@jslobodzian jslobodzian jslobodzian approved these changes

@tobiasb-ms tobiasb-ms tobiasb-ms approved these changes

At least 1 approving review is required to merge this pull request.

Assignees
No one assigned
Labels
main PR Destined for main Packaging security
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@mfrw @jslobodzian @tobiasb-ms