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

[2.0] tar: Fix CVE-2022-48303 and CVE-2023-39804 #11136

Merged
merged 3 commits into from
Nov 20, 2024
Merged

[2.0] tar: Fix CVE-2022-48303 and CVE-2023-39804 #11136

merged 3 commits into from
Nov 20, 2024

Conversation

KavyaSree2610
Copy link
Contributor

@KavyaSree2610 KavyaSree2610 commented Nov 19, 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?

Change Log
Does this affect the toolchain?

YES/NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology

@KavyaSree2610 KavyaSree2610 marked this pull request as ready for review November 19, 2024 09:21
@KavyaSree2610 KavyaSree2610 requested a review from a team as a code owner November 19, 2024 09:21
@KavyaSree2610 KavyaSree2610 changed the title Fix CVE-2022-48303 for tar : 2.0 Fix CVE-2022-48303and CVE-2023-39804 for tar : 2.0 Nov 19, 2024
@anphel31 anphel31 changed the title Fix CVE-2022-48303and CVE-2023-39804 for tar : 2.0 [2.0] tar: Fix CVE-2022-48303 and CVE-2023-39804 Nov 20, 2024
@jslobodzian jslobodzian merged commit 54910c1 into fasttrack/2.0 Nov 20, 2024
10 checks passed
@jslobodzian jslobodzian deleted the kkaitepalli/CVE-2022-48303 branch November 20, 2024 19:46
CBL-Mariner-Bot pushed a commit that referenced this pull request Nov 20, 2024
@KavyaSree2610 @CBL-Mariner-Bot
[2.0] tar: Fix CVE-2022-48303 and CVE-2023-39804 (#11136)
d150a7e 
Co-authored-by: kavyasree <[email protected]>
Co-authored-by: jslobodzian <[email protected]>
(cherry picked from commit 54910c1)
@CBL-Mariner-Bot CBL-Mariner-Bot mentioned this pull request Nov 20, 2024
Merged
@CBL-Mariner-Bot
Copy link
Collaborator

Auto cherry-pick results:

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=679522&view=results

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

@anphel31 anphel31 anphel31 approved these changes

@jslobodzian jslobodzian jslobodzian approved these changes

Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@KavyaSree2610 @CBL-Mariner-Bot @jslobodzian @anphel31