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

Multiple High / Critical vulnerabilities in Go stdlib #32

Closed
bpfoster opened this issue Jun 26, 2024 · 1 comment
Closed

Multiple High / Critical vulnerabilities in Go stdlib #32

bpfoster opened this issue Jun 26, 2024 · 1 comment
Assignees

Comments

@bpfoster
Copy link

What steps will reproduce the bug?

Scans of the most recent wait-for-port release are showing multiple vulnerabilities in the version of go that was used to build the binary.

All can be resolved by updating to the latest go 1.21 version (1.21.11)

What is the expected behavior?

No high impact vulnerabilities reported in scanning of artifacts.

What do you see instead?

Above mentioned vulnerabilities

Additional information

No response

@bpfoster
Copy link
Author

bpfoster commented Jul 2, 2024

Closing this issue as these are all resolved in the v1.0.8 release from today which upgraded to go 1.22.4.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants