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

[grafana] fix cve-2021-25742 #1481

Merged
merged 2 commits into from
Jun 11, 2022
Merged

Conversation

zanac1986
Copy link
Contributor

Signed-off-by: zanac1986 zanhsieh@protonmail.com

Signed-off-by: zanac1986 <zanhsieh@protonmail.com>
Signed-off-by: zanac1986 <zanhsieh@protonmail.com>
@zanhsieh zanhsieh changed the title fix cve-2021-25742 [grafana] fix cve-2021-25742 Jun 11, 2022
@zanhsieh zanhsieh merged commit 7cdf73f into grafana:main Jun 11, 2022
@afirth
Copy link
Contributor

afirth commented Jun 28, 2022

Hello,

This configuration is only valid on the ingress-nginx configmap, but you seem to have applied it to the grafana configmap. Is there another meaning of this annotation in grafana-land? Otherwise, I'm pretty sure you can't "fix" this here. I assume you got here from this linter but this linter is wrong. It only applies to the ingress-nginx configmap - not all configmaps in the cluster (that would be a K8s vulnerability, not an ingress-nginx one). Suggest to revert. I will open an issue too.

Thanks for all the hard work maintaining!

zanhsieh added a commit that referenced this pull request Jun 29, 2022
@zanac1986 zanac1986 deleted the fix-cve-2021-25742 branch October 16, 2022 01:36
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.

3 participants