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

libcontainers-common: address CVE-2022-2879, CVE-2023-45288, CVE-2024-1753, CVE-2024-3727 & CVE-2024-37298 #9737

Merged
merged 8 commits into from
Jul 11, 2024

Conversation

mfrw
Copy link
Member

@mfrw mfrw commented Jul 10, 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
  • If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
  • Ready to merge

Summary

What does the PR accomplish, why was it needed?

Change Log
  • libcontainers-common: switch to patch command instead of %patch macro in %build section
Does this affect the toolchain?

NO

Associated issues
  • NA
Links to CVEs
Test Methodology
  • Local build with RUN_CHECK=y
  • Pipeline build id: PR-9737
  • Pripeline build post review/rebase: PR-9737

@mfrw mfrw added security 3.0-dev PRs Destined for AzureLinux 3.0 labels Jul 10, 2024
@mfrw mfrw marked this pull request as ready for review July 10, 2024 04:16
@mfrw mfrw requested a review from a team as a code owner July 10, 2024 04:16
mfrw added 7 commits July 11, 2024 08:25
Signed-off-by: Muhammad Falak R Wani <[email protected]>
Signed-off-by: Muhammad Falak R Wani <[email protected]>
Signed-off-by: Muhammad Falak R Wani <[email protected]>
Signed-off-by: Muhammad Falak R Wani <[email protected]>
Signed-off-by: Muhammad Falak R Wani <[email protected]>
… in %build section

Signed-off-by: Muhammad Falak R Wani <[email protected]>
@mfrw mfrw force-pushed the mfrw/libcontainers-common-cves-3.0 branch from f3e2a89 to 19f5523 Compare July 11, 2024 03:02
@mfrw mfrw requested a review from PawelWMS July 11, 2024 16:33
Copy link
Contributor

@PawelWMS PawelWMS left a comment

Choose a reason for hiding this comment

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

One more small request but looks good in general.

@mfrw mfrw merged commit 0618629 into 3.0-dev Jul 11, 2024
12 checks passed
@mfrw mfrw deleted the mfrw/libcontainers-common-cves-3.0 branch July 11, 2024 23:57
Xiaohong-Deng pushed a commit to Xiaohong-Deng/azurelinux that referenced this pull request Nov 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3.0-dev PRs Destined for AzureLinux 3.0 security
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants