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

update golang 1.12.9 to 1.12.10.There is a CVE for Go and this vulnerability is fixed in 1.12.10 #7799

Closed
tanjunchen opened this issue Oct 16, 2019 · 1 comment · Fixed by #7811

Comments

@tanjunchen
Copy link
Member

1. What kops version are you running? The command kops version, will display
this information.

2. What Kubernetes version are you running? kubectl version will print the
version if a cluster is running or provide the Kubernetes version specified as
a kops flag.

3. What cloud provider are you using?

4. What commands did you run? What is the simplest way to reproduce this issue?

5. What happened after the commands executed?

6. What did you expect to happen?

7. Please provide your cluster manifest. Execute
kops get --name my.example.com -o yaml to display your cluster manifest.
You may want to remove your cluster name and other sensitive information.

8. Please run the commands with most verbose logging by adding the -v 10 flag.
Paste the logs into this report, or in a gist and provide the gist link here.

9. Anything else do we need to know?
There is a CVE for Go and this vulnerability is fixed in 1.12.10. We should update it.
See: https://nvd.nist.gov/vuln/detail/CVE-2019-16276

See issue golang/go#34540
Seems this is fixed in 1.12.10. I suggest we should update to 1.12.10 first

@tanjunchen tanjunchen changed the title update golang 1.12.9 to 1.12.10 update golang 1.12.9 to 1.12.10 There is a CVE for Go and this vulnerability is fixed in 1.12.10 Oct 16, 2019
@tanjunchen tanjunchen changed the title update golang 1.12.9 to 1.12.10 There is a CVE for Go and this vulnerability is fixed in 1.12.10 update golang 1.12.9 to 1.12.10.There is a CVE for Go and this vulnerability is fixed in 1.12.10 Oct 16, 2019
@tanjunchen
Copy link
Member Author

@chenrui333 @justinsb what do you think?

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

Successfully merging a pull request may close this issue.

1 participant