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

Fix vulnerability reported by Prisma Cloud on module github.com/emicklei/go-restful/v3 #36319

Open
mmtevelde opened this issue Jan 14, 2025 · 3 comments · May be fixed by #36318
Open

Fix vulnerability reported by Prisma Cloud on module github.com/emicklei/go-restful/v3 #36319

mmtevelde opened this issue Jan 14, 2025 · 3 comments · May be fixed by #36318
Labels
enhancement new new issue not yet triaged

Comments

@mmtevelde
Copy link

Terraform Version

Terraform v1.10.4
on darwin_arm64

Use Cases

Prisma Cloud container vulnerability scanning reports a vulnerability on the indirect dependency github.com/emicklei/go-restful/v3 used in internal/backend/remote-state/kubernetes
For reference: within the Prisma Cloud ecosystem, this vulnerability is referred to as PRISMA-2022-0227, rated 7.5 - High. The vulnerability is fixed in versions v.3.10.0 and upwards of github.com/emicklei/go-restful/v3.
A similar question was asked on HashiCorp Discuss here. To illustrate, a similar issue was raised on Kubernetes kubernetes/kubernetes#120604.

Attempted Solutions

#36318

Proposal

#36318

References

No response

@mmtevelde mmtevelde added enhancement new new issue not yet triaged labels Jan 14, 2025
@crw
Copy link
Contributor

crw commented Jan 14, 2025

Thanks for filing this information. Vulnerability scanners tend to flag false positives in terms of code paths with vulnerabilities that are not used by the actual product. In these cases, the dependency in question will be updated the next time there is a functional need to do so. In the case of backends not maintained by the core team, as in this case, it may take some time as the backends tend not to be the highest priority for those teams. Thanks again for your interest!

@jbardin
Copy link
Member

jbardin commented Jan 14, 2025

It may also help to reference the actual CVE in order to evaluate the vulnerability, as the internal PRISMA-2022-0227 reference is not something that appears to be publicly available.

@mmtevelde
Copy link
Author

It may also help to reference the actual CVE in order to evaluate the vulnerability, as the internal PRISMA-2022-0227 reference is not something that appears to be publicly available.

FYI you are correct that a CVE was never issued. This is the huntr page associated with the issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement new new issue not yet triaged
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants