Closed hmgowda closed 3 months ago
@shaj13 do you have plans on addressing this issue? or if I open a PR with a fix for this issue, would it get accepted? Would really appreciated your inputs on this.
@shaj13 do you have plans on addressing this issue? or if I open a PR with a fix for this issue, would it get accepted? Would really appreciated your inputs on this.
Yes, I am aware of the issue and currently, there are no plans for a fix. However, if you open a PR with a fix, it would be welcomed and reviewed. Just for context, what strategy are you using? I assume it's JWT. Is it in a production environment?
We are using JWT strategy in one of our open sourced components for JWT based authentication and authorization. I will open a PR for this in that case, would go version upgrade along with it also be welcomed?
@hmgowda Yes, but that would be a significant change, as it would require a refactor and updates to the CI/CD pipeline as well.
@shaj13 I have a PR for this issue https://github.com/shaj13/go-guardian/pull/132 Would appreciate your review and see if this can be merged into master.
Thanks @hmgowda, Fixe is included in v2.11.6.
PR #132
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
Yes
What version of Go-Guardian are you using ?
What did you do?
Github security scan (dependabot) and checkmarx has reported a CVE in this library that is introduced through gopkg.in/square/go-jose.v2 v2.5.1.
CVE information can be found here : https://github.com/advisories/GHSA-c5q2-7r4c-mv6g The version of go-jose library need to updated. The path with the fix is available in github.com/go-jose/go-jose/v4 4.0.1 onwards.
What did you expect to see?
No Vulnerabilities.
What did you see instead?
Saw CVE-2024-28180 https://github.com/advisories/GHSA-c5q2-7r4c-mv6g