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

[GHSA-h27c-6xm3-mcqp] Kanister vulnerable to cluster-level privilege escalation #5030

Conversation

hairyhum
Copy link

Updates

  • Affected products
  • CVSS v3
  • CVSS v4

Comments
The issue was fixed in kanisterio/kanister@1f40f03 but it should not apply to golang package to begin with as stated in #5029
Ideally the advisory should be removed alltogether, but if it's easier it should at least be marked as fixed.

@github
Copy link
Collaborator

github commented Nov 22, 2024

Hi there @hairyhum! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.

This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory

@github-actions github-actions bot changed the base branch from main to hairyhum/advisory-improvement-5030 November 22, 2024 00:55
@advisory-database advisory-database bot merged commit 67d23e5 into hairyhum/advisory-improvement-5030 Nov 22, 2024
2 checks passed
@advisory-database
Copy link
Contributor

Hi @hairyhum! Thank you so much for contributing to the GitHub Advisory Database. This database is free, open, and accessible to all, and it's people like you who make it great. Thanks for choosing to help others. We hope you send in more contributions in the future!

@advisory-database advisory-database bot deleted the hairyhum-GHSA-h27c-6xm3-mcqp branch November 22, 2024 23:11
@darakian
Copy link
Contributor

Apologies for tagging this on the go package. I went ahead and got the fixed version listed. We sadly have a technical limitation at the moment around removing advisories from our reviewed set. We're working on that, but its not going to be done soon. I can get this advisory marked as withdrawn as well if you like though that could also spark confusion :(

Let me know what's best 👍

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