Skip to content

python3: Address CVE-2024-11168 with a formatted patch #11110

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
Merged
merged 1 commit into from
Nov 18, 2024
Merged

python3: Address CVE-2024-11168 with a formatted patch #11110

merged 1 commit into from
Nov 18, 2024

Conversation

Ankita13-code
Copy link
Contributor

@Ankita13-code Ankita13-code commented Nov 18, 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?
This PR formats the upstream patch for CVE-2024-11168 in order to remove the whitespaces and offsets for a clear build

Change Log
  • Add the formatted patch instead of the previous one. The upstream patch can be found here
Does this affect the toolchain?

YES

Associated issues
  • #xxxx
Links to CVEs
Test Methodology

@Ankita13-code
python3: Format the patch to remove whitespaces and offsets
57e2a1c 
Signed-off-by: ankita <ankitapareek@microsoft.com>
@Ankita13-code Ankita13-code changed the base branch from 3.0 to fasttrack/2.0 November 18, 2024 09:52
@Ankita13-code Ankita13-code marked this pull request as ready for review November 18, 2024 10:17
@Ankita13-code Ankita13-code requested a review from a team as a code owner November 18, 2024 10:17
@jslobodzian jslobodzian merged commit 8ec6d94 into fasttrack/2.0 Nov 18, 2024
14 checks passed
@jslobodzian jslobodzian deleted the ankitapareek/2.0-python-CVE-fix branch November 18, 2024 19:54
CBL-Mariner-Bot pushed a commit that referenced this pull request Nov 18, 2024
@Ankita13-code @CBL-Mariner-Bot
python3: Address CVE-2024-11168 with a formatted patch (#11110)
596a67b 
Signed-off-by: ankita <ankitapareek@microsoft.com>
Co-authored-by: ankita <ankitapareek@microsoft.com>
(cherry picked from commit 8ec6d94)
@CBL-Mariner-Bot CBL-Mariner-Bot mentioned this pull request Nov 18, 2024
Closed
@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=678160&view=results

jslobodzian pushed a commit that referenced this pull request Nov 23, 2024
@Ankita13-code @jslobodzian
python3: Address CVE-2024-11168 with a formatted patch (#11110)
febc095 
Signed-off-by: ankita <ankitapareek@microsoft.com>
Co-authored-by: ankita <ankitapareek@microsoft.com>
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 security
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
3 participants
@Ankita13-code @CBL-Mariner-Bot @jslobodzian