Closed hairyhum closed 6 days ago
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
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!
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 👍
I can get this advisory marked as withdrawn
Sure. Let's do that.
Done and done 👍 https://github.com/advisories/GHSA-h27c-6xm3-mcqp
Updates
Comments The issue was fixed in https://github.com/kanisterio/kanister/commit/1f40f03d8432e8dc80fe248d306c1e201808ec59 but it should not apply to golang package to begin with as stated in https://github.com/github/advisory-database/issues/5029 Ideally the advisory should be removed alltogether, but if it's easier it should at least be marked as fixed.