Skip to content

Apply patches to fix CVE-2021-3602, CVE-2022-27651, CVE-2022-2995, CVE-2023-42821#8818

Merged
jslobodzian merged 6 commits intomainfrom
cameronbaird/crio-cves
Apr 25, 2024
Merged

Apply patches to fix CVE-2021-3602, CVE-2022-27651, CVE-2022-2995, CVE-2023-42821#8818
jslobodzian merged 6 commits intomainfrom
cameronbaird/crio-cves

Conversation

@Camelron
Copy link
Copy Markdown
Contributor

@Camelron Camelron commented Apr 16, 2024

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 (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/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

Patch cri-o CVEs

Change Log

CVE-2021-3602
CVE-2021-44716
CVE-2022-21698
CVE-2022-27651
CVE-2022-29526
CVE-2022-2995
CVE-2023-42821
CVE-2023-44487
CVE-2024-28180
CVE-2024-21626

Does this affect the toolchain?

NO

Test Methodology

@microsoft-github-policy-service microsoft-github-policy-service Bot added the main PR Destined for main label Apr 16, 2024
@Camelron Camelron force-pushed the cameronbaird/crio-cves branch from bf9a7c2 to fa24694 Compare April 16, 2024 22:45
@Camelron Camelron marked this pull request as ready for review April 19, 2024 17:21
@Camelron Camelron requested a review from a team as a code owner April 19, 2024 17:21
Comment thread SPECS/cri-o/cri-o.spec Outdated
@mfrw mfrw added the security label Apr 23, 2024
Co-authored-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
Copy link
Copy Markdown
Member

@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.

LGTM with a suggestion

Comment thread SPECS/cri-o/cri-o.spec Outdated
Co-authored-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
@jslobodzian jslobodzian merged commit f55af6f into main Apr 25, 2024
@jslobodzian jslobodzian deleted the cameronbaird/crio-cves branch April 25, 2024 15:23
amritakohli pushed a commit that referenced this pull request May 2, 2024
…E-2023-42821 (#8818)

Co-authored-by: dallasd1 <dadelan@microsoft.com>
Co-authored-by: Dallas Delaney <106280731+dallasd1@users.noreply.github.com>
Co-authored-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
Co-authored-by: jslobodzian <joslobo@microsoft.com>
bfjelds pushed a commit that referenced this pull request May 13, 2024
…E-2023-42821 (#8818)

Co-authored-by: dallasd1 <dadelan@microsoft.com>
Co-authored-by: Dallas Delaney <106280731+dallasd1@users.noreply.github.com>
Co-authored-by: Muhammad Falak R Wani <falakreyaz@gmail.com>
Co-authored-by: jslobodzian <joslobo@microsoft.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

main PR Destined for main security

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants