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

Fix CVE 2024 24786 for prometheus #10673

Closed
wants to merge 1 commit into from

Conversation

bhagyapathak
Copy link
Contributor

@bhagyapathak bhagyapathak commented Oct 9, 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 (./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

Fix CVE 2024 24786 for prometheus

Change Log
Does this affect the toolchain?

NO

Associated issues
  • #xxxx
Links to CVEs
Test Methodology

--------------- Local Build Successful -------------------
INFO[0000][scheduler] Testing: prometheus-2.37.0-16.cm2.src.rpm
INFO[0000][scheduler] Building: prometheus-2.37.0-16.cm2.src.rpm
INFO[0164][scheduler] Built: prometheus-2.37.0-16.cm2.src.rpm -> [/home/bhapathak/azlinux/out/RPMS/x86_64/prometheus-2.37.0-16.cm2.x86_64.rpm /home/bhapathak/azlinux/out/RPMS/x86_64/prometheus-debuginfo-2.37.0-16.cm2.x86_64.rpm /home/bhapathak/azlinux/out/RPMS/x86_64/prometheus-docs-2.37.0-16.cm2.x86_64.rpm]
INFO[0164][scheduler] 0 currently active build(s): [].
INFO[0164][scheduler] 1 currently active test(s): [prometheus-2.37.0-16.cm2.src.rpm].
INFO[0596][scheduler] Tested: prometheus-2.37.0-16.cm2.src.rpm
INFO[0596][scheduler] 0 currently active build(s): [].
INFO[0596][scheduler] 0 currently active test(s): [].
INFO[0596][scheduler] All packages built
INFO[0597][scheduler] ---------------------------
INFO[0597][scheduler] --------- Summary ---------
INFO[0597][scheduler] ---------------------------
INFO[0597][scheduler] Number of prebuilt SRPMs: 0
INFO[0597][scheduler] Number of prebuilt delta SRPMs: 0
INFO[0597][scheduler] Number of skipped SRPMs tests: 0
INFO[0597][scheduler] Number of built SRPMs: 1
INFO[0597][scheduler] Number of passed SRPMs tests: 1
INFO[0597][scheduler] Number of unresolved dependencies: 0
INFO[0597][scheduler] Number of blocked SRPMs: 0
INFO[0597][scheduler] Number of blocked SRPMs tests: 0
INFO[0597][scheduler] Number of failed SRPMs: 0
INFO[0597][scheduler] Number of failed SRPMs tests: 0
INFO[0597][scheduler] Number of toolchain RPM conflicts: 0
INFO[0597][scheduler] Number of toolchain SRPM conflicts: 0
INFO[0597][scheduler] Built SRPMs:
INFO[0597][scheduler] --> prometheus-2.37.0-16.cm2.src.rpm
INFO[0597][scheduler] Passed SRPMs tests:

@bhagyapathak bhagyapathak requested a review from a team as a code owner October 9, 2024 09:38
Copy link
Contributor

@Sumynwa Sumynwa left a comment

Choose a reason for hiding this comment

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

LGTM

Copy link
Contributor

@jslobodzian jslobodzian left a comment

Choose a reason for hiding this comment

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

Copy link
Contributor

@jslobodzian jslobodzian left a comment

Choose a reason for hiding this comment

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

please retarget at fasttrack 2.0 unless this will be abandoned in favor of the prometheus upgrade

@bhagyapathak
Copy link
Contributor Author

Retargeting following PR for fasttrack/2.0

  1. Bump prometheus to 2.37.9 to fix CVE 2022 41717 #10685
  2. Fix CVE 2024 24786 for prometheus #10673

under new PR #10730

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

Successfully merging this pull request may close these issues.

3 participants