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

busybox: Address CVE-2023-42366 #11025

Merged
merged 2 commits into from
Nov 25, 2024
Merged

busybox: Address CVE-2023-42366 #11025

merged 2 commits into from
Nov 25, 2024

Conversation

Ankita13-code
Copy link
Contributor

@Ankita13-code Ankita13-code commented Nov 12, 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?
Fixes CVE-2023-42366

Change Log
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology

@Ankita13-code Ankita13-code changed the base branch from 3.0-dev to fasttrack/3.0 November 15, 2024 05:37
@Ankita13-code Ankita13-code changed the base branch from fasttrack/3.0 to 3.0-dev November 15, 2024 06:03
@Ankita13-code Ankita13-code changed the title busybox: Address CVE-2023-42364 and CVE-2023-42366 busybox: Address CVE-2023-42366 Nov 18, 2024
@Ankita13-code Ankita13-code marked this pull request as ready for review November 18, 2024 06:55
@Ankita13-code Ankita13-code requested a review from a team as a code owner November 18, 2024 06:55
@Ankita13-code Ankita13-code merged commit 0b8dbc4 into 3.0-dev Nov 25, 2024
13 checks passed
@Ankita13-code Ankita13-code deleted the ankitapareek/busybox-CVE-fixes branch November 25, 2024 14:36
arc9693 pushed a commit that referenced this pull request Dec 12, 2024
@Ankita13-code @arc9693
busybox: Address CVE-2023-42366 (#11025)
26d9838 
Signed-off-by: Ankita Pareek <[email protected]>
Co-authored-by: Ankita Pareek <[email protected]>
durgajagadeesh pushed a commit to durgajagadeesh/azurelinux_djpalli that referenced this pull request Dec 31, 2024
@Ankita13-code @durgajagadeesh
busybox: Address CVE-2023-42366 (microsoft#11025)
25c96f0 
Signed-off-by: Ankita Pareek <[email protected]>
Co-authored-by: Ankita Pareek <[email protected]>
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

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

Successfully merging this pull request may close these issues.
2 participants
@Ankita13-code @jslobodzian