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

Need golang version to be updated to 1.18.5 to resolve high level security issues #1878

Closed
muhanator opened this issue Aug 24, 2022 · 1 comment · Fixed by #1925
Closed
Assignees

Comments

@muhanator
Copy link

muhanator commented Aug 24, 2022

Which version of the AzCopy was used?

latest version: @azure-tools/azcopy-linux:10.16.0

Which platform are you using? (ex: Windows, Mac, Linux)

Linux

What command did you run?

We have a node.js based microservice which uses @azure-tools/azcopy-node as dependency (in our package.json)
image

@azure-tools/azcopy-node uses "@azure-tools/azcopy-linux" as a dependency (in our package-lock.json)
image

What problem was encountered?

attached is security scan:
Docker_ccss-4.1.0-gl1200247_Security_Export.pdf

We see 16 high level security issues detected in our security scans because we use @azure-tools/azcopy-linux:10.16.0, which uses golang:1.17.9.
image

How can we reproduce the problem in the simplest way?

Use the npm package @azure-tools/azcopy-linux:10.16.0 from https://www.npmjs.com/package/resolve in your node.js project, build it as a docker image, run a xray security scan (scanning tool used in our case) and you will see multiple high level security issue due to the use of golang:1.17.9 (which is used in @azure-tools/azcopy-linux:10.16.0)

Have you found a mitigation/solution?

Upgrading the golang version to 1.18.5 should resolve the issue, should be a similar fix to 1883a4b

@adreed-msft
Copy link
Member

@zezha-msft I'll submit a PR to upgrade our target Go version.

@JasonYeMSFT FYI

@adreed-msft adreed-msft self-assigned this Sep 22, 2022
@nakulkar-msft nakulkar-msft linked a pull request Nov 17, 2022 that will close this issue
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.

3 participants