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

replace go-jose.v2 with newer version because it is vulnerable to CVE-2024-28180 #134

Open
gunturaf opened this issue Jun 5, 2024 · 1 comment

Comments

@gunturaf
Copy link

gunturaf commented Jun 5, 2024

Based on the advisory in this link, the go-jose.v2 is vulnerable:
GHSA-c5q2-7r4c-mv6g

I tried to fix in my local clone of krakend-jose, but it seems that the underlying dependency of go-auth0 also needs to be updated.

I might be able to send MRs for both of the repositories affected, but in this issue I just want to let you folks know that this vuln might be blocking some organizations that uses trivy in their CI/CD pipeline.

@alombarte
Copy link
Member

Thanks @gunturaf. Generally speaking, trivy is an excellent tool but it also gives a lot of false positives, so blocking your pipelines because of it IMHO is a drastic measure and not an advisable strategy.

That being said, KrakenD does not support JWE, and while this vulnerability is on the JOSE package, it does not affect KrakenD. Feel free to open MR for review, but I must warn you that the go-auth0 will be "challenging".

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

No branches or pull requests

2 participants