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

[Medium] cmake: Fix CVE-2024-7264 and CVE-2024-9681 #12020

Open
wants to merge 2 commits into
base: fasttrack/3.0
Choose a base branch
from

Conversation

jykanase
Copy link
Contributor

@jykanase jykanase commented Jan 22, 2025

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

cmake: Fix CVE-2024-7264 and CVE-2024-9681

Change Log

Added following patches:

Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology
  • Pipeline build id: xxxx

@jykanase jykanase requested a review from a team as a code owner January 22, 2025 06:48
@jykanase jykanase force-pushed the topic_cmake branch 2 times, most recently from 1d33642 to adde4c9 Compare January 22, 2025 06:50
@jykanase jykanase changed the title cmake: Fix CVE-2024-9681.patch and CVE-2024-9681.patch [Medium] cmake: Fix CVE-2024-9681.patch and CVE-2024-9681.patch Jan 22, 2025
@jykanase jykanase changed the title [Medium] cmake: Fix CVE-2024-9681.patch and CVE-2024-9681.patch [Medium] cmake: Fix CVE-2024-9681 and CVE-2024-9681 Jan 22, 2025
@jykanase jykanase changed the title [Medium] cmake: Fix CVE-2024-9681 and CVE-2024-9681 [Medium] cmake: Fix CVE-2024-7264 and CVE-2024-9681 Jan 22, 2025
@@ -15,6 +15,9 @@ Patch1: CVE-2024-6197.patch
Patch2: CVE-2024-6874.patch
Patch3: CVE-2024-8096.patch
Patch4: CVE-2024-11053.patch
Patch5: clean-up-GTime2str.patch
Copy link
Contributor

Choose a reason for hiding this comment

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

@jykanase what is patch5 doing? Is it related to a CVE fix or just some additional change that was brought over?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants