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(deps): update module github.com/cilium/cilium to v1.16.6 [security] #1844

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Aug 15, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/cilium/cilium v1.16.5 -> v1.16.6 age adoption passing confidence

GitHub Vulnerability Alerts

CVE-2025-23047

Impact

For users who deploy Hubble UI using either Cilium CLI or via the Cilium Helm chart, an insecure default Access-Control-Allow-Origin header value could lead to sensitive data exposure. A user with access to a Hubble UI instance affected by this issue could leak configuration details about the Kubernetes cluster which Hubble UI is monitoring, including node names, IP addresses, and other metadata about workloads and the cluster networking configuration. In order for this vulnerability to be exploited, a victim would have to first visit a malicious page.

Patches

This issue was patched in cilium/cilium@a3489f1

This issue affects:

  • Cilium between v1.14.0 and v1.14.18 inclusive
  • Cilium between v1.15.0 and v1.15.12 inclusive
  • Cilium between v1.16.0 and v1.16.5 inclusive

This issue is patched in:

  • Cilium v1.14.19
  • Cilium v1.15.13
  • Cilium v1.16.6

Workarounds

Users who deploy Hubble UI using the Cilium Helm chart directly can remove the CORS headers from the Helm template as shown in the patch.

Acknowledgements

The Cilium community has worked together with members of Isovalent to prepare these mitigations. Special thanks to @​ciffelia for reporting this issue and to @​geakstr for the fix.

For more information

If you have any questions or comments about this advisory, please reach out on Slack.

If you think you have found a vulnerability affecting Cilium, we strongly encourage you to report it to our security mailing list at [email protected]. This is a private mailing list for the Cilium security team, and your report will be treated as top priority.


Release Notes

cilium/cilium (github.com/cilium/cilium)

v1.16.6: 1.16.6

Compare Source

Summary of Changes

Major Changes:

Minor Changes:

Bugfixes:

CI Changes:

Misc Changes:

Other Changes:

Docker Manifests

cilium

quay.io/cilium/cilium:v1.16.6@​sha256:1e0896b1c4c188b4812c7e0bed7ec3f5631388ca88325c1391a0ef9172c448da
quay.io/cilium/cilium:stable@sha256:1e0896b1c4c188b4812c7e0bed7ec3f5631388ca88325c1391a0ef9172c448da

clustermesh-apiserver

quay.io/cilium/clustermesh-apiserver:v1.16.6@​sha256:ab2070ea48a52a55d961b81b7b5fbac7d40a3f428be9b1b6b9071d47f194456a
quay.io/cilium/clustermesh-apiserver:stable@sha256:ab2070ea48a52a55d961b81b7b5fbac7d40a3f428be9b1b6b9071d47f194456a

docker-plugin

quay.io/cilium/docker-plugin:v1.16.6@​sha256:f8f5833a60900b0264fd8982b11329e130c1a326afe2e4653e9f2d2e3fb2af66
quay.io/cilium/docker-plugin:stable@sha256:f8f5833a60900b0264fd8982b11329e130c1a326afe2e4653e9f2d2e3fb2af66

hubble-relay

quay.io/cilium/hubble-relay:v1.16.6@​sha256:ca8dcaa5a81a37743b1397ba2221d16d5d63e4a47607584f1bf50a3b0882bf3b
quay.io/cilium/hubble-relay:stable@sha256:ca8dcaa5a81a37743b1397ba2221d16d5d63e4a47607584f1bf50a3b0882bf3b

operator-alibabacloud

quay.io/cilium/operator-alibabacloud:v1.16.6@​sha256:0e3c7fbcb6bde9a247cd2dd3d25230e2859d40d2eb58aba6265a2aab216775a9
quay.io/cilium/operator-alibabacloud:stable@sha256:0e3c7fbcb6bde9a247cd2dd3d25230e2859d40d2eb58aba6265a2aab216775a9

operator-aws

quay.io/cilium/operator-aws:v1.16.6@​sha256:d11ee1cfa3465defe2df7ec1c6e8a77bcaf280b44d2c61aa7496c58b29550f6d
quay.io/cilium/operator-aws:stable@sha256:d11ee1cfa3465defe2df7ec1c6e8a77bcaf280b44d2c61aa7496c58b29550f6d

operator-azure

quay.io/cilium/operator-azure:v1.16.6@​sha256:0a05d7aea760923897aabd715213ab11a706051673d41fab3874a37f897c1bdd
quay.io/cilium/operator-azure:stable@sha256:0a05d7aea760923897aabd715213ab11a706051673d41fab3874a37f897c1bdd

operator-generic

quay.io/cilium/operator-generic:v1.16.6@​sha256:13d32071d5a52c069fb7c35959a56009c6914439adc73e99e098917646d154fc
quay.io/cilium/operator-generic:stable@sha256:13d32071d5a52c069fb7c35959a56009c6914439adc73e99e098917646d154fc

operator

quay.io/cilium/operator:v1.16.6@​sha256:09ab2878e103fa32a00fd1fe4469f7042cfb053627b44c82fa03a04a820c0b46
quay.io/cilium/operator:stable@sha256:09ab2878e103fa32a00fd1fe4469f7042cfb053627b44c82fa03a04a820c0b46


Configuration

📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 3 times, most recently from 5243393 to b9de45f Compare August 21, 2024 10:07
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 64008ff to d223c73 Compare August 29, 2024 10:06
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 5 times, most recently from cbb34ad to 8153671 Compare September 8, 2024 02:54
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from e4a63d8 to f969d43 Compare September 9, 2024 14:58
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 23b1c7c to d25612b Compare September 20, 2024 07:55
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 27f2299 to 8f6e223 Compare October 16, 2024 04:57
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 3 times, most recently from a6fe1b5 to c6186ec Compare October 21, 2024 20:31
@renovate renovate bot changed the title fix(deps): update module github.com/cilium/cilium to v1.14.14 [security] fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] Oct 21, 2024
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 4 times, most recently from 2ccaf97 to d540971 Compare October 30, 2024 10:28
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 1886b51 to 8b60283 Compare November 7, 2024 06:06
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 4 times, most recently from 8b3c465 to d7ea150 Compare December 2, 2024 07:09
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 5 times, most recently from a3bb9d8 to dfbc269 Compare January 9, 2025 10:59
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from b3a8eaa to e964dbc Compare January 10, 2025 11:41
@renovate renovate bot changed the title fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] Update module github.com/cilium/cilium to v1.14.16 [SECURITY] Jan 10, 2025
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 7 times, most recently from 7358858 to 33b412b Compare January 17, 2025 15:31
@renovate renovate bot changed the title Update module github.com/cilium/cilium to v1.14.16 [SECURITY] fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] Jan 17, 2025
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from 82bab8a to 8d43611 Compare January 20, 2025 07:01
@renovate renovate bot changed the title fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] - autoclosed Jan 20, 2025
@renovate renovate bot closed this Jan 20, 2025
@renovate renovate bot deleted the renovate/go-github.com-cilium-cilium-vulnerability branch January 20, 2025 15:52
@renovate renovate bot changed the title fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] - autoclosed fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] Jan 23, 2025
@renovate renovate bot reopened this Jan 23, 2025
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from 9f7100c to 8d43611 Compare January 23, 2025 20:34
@renovate renovate bot changed the title fix(deps): update module github.com/cilium/cilium to v1.14.16 [security] fix(deps): update module github.com/cilium/cilium to v1.16.6 [security] Jan 23, 2025
Copy link
Contributor Author

renovate bot commented Jan 23, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: KubeArmor/go.sum
Command failed: install-tool golang 1.22.11

@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch 2 times, most recently from cf38b3d to fb18e12 Compare January 24, 2025 05:41
@renovate renovate bot force-pushed the renovate/go-github.com-cilium-cilium-vulnerability branch from fb18e12 to 4e457d7 Compare January 25, 2025 07:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants