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

Bump x/oauth2 and x/crypto to resolve CVE-2025-22868 + CVE-2025-22869 in Alloy #2933

Open
1 of 3 tasks
rgoltz opened this issue Mar 9, 2025 · 0 comments · May be fixed by #2934
Open
1 of 3 tasks

Bump x/oauth2 and x/crypto to resolve CVE-2025-22868 + CVE-2025-22869 in Alloy #2933

rgoltz opened this issue Mar 9, 2025 · 0 comments · May be fixed by #2934
Labels
enhancement New feature or request

Comments

@rgoltz
Copy link

rgoltz commented Mar 9, 2025

Request

Let's keep the Grafana Alloy Go-modules and -packages up-to-date. The current latest Docker-Image tag v1.7.1 using an older of golang.org/x/crypto and golang.org/x/oauth2.
Hence, picking up fixes for CVE-2025-22868 and CVE-2025-22869:

Use case

  • Upgrade golang.org/x/crypto to v0.35.0 or above.
  • Upgrade golang.org/x/oauth2 to v0.27.0 or above.
  • I'll create a PR to upgrade this both modules.

Those dependency updates just aim to silence some (SBOM-based) scanners.
@rgoltz rgoltz added the enhancement New feature or request label Mar 9, 2025
@rgoltz rgoltz linked a pull request Mar 9, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: bump golang.org/x/crypto and golang.org/x/oauth2 rgoltz/alloy
1 participant
@rgoltz