Hello, we are a team researching the dependency management mechanism of Golang. During our analysis, we came across your project and noticed that it contains a vulnerability (CVE-2022-27191, CVE-2022-29526).
In your project, the golang.org/x/crypto package is being used at version golang.org/x/crypto v0.0.0-20201124201722-c8d3bf9c5392, but the patched version is 0.0.0-20220314234659-1baeb1ce4c0b. To fix the vulnerability, we recommend modifying the go.mod file to update the version to 0.0.0-20220314234659-1baeb1ce4c0b or higher.
the golang.org/x/sys package is being used at version golang.org/x/sys v0.0.0-20200223170610-d5e6a3e2c0ae, but the patched version is v0.1.0. To fix the vulnerability, we recommend modifying the go.mod file to update the version to v0.1.0 or higher.
Hello, we are a team researching the dependency management mechanism of Golang. During our analysis, we came across your project and noticed that it contains a vulnerability (CVE-2022-27191, CVE-2022-29526). In your project, the golang.org/x/crypto package is being used at version golang.org/x/crypto v0.0.0-20201124201722-c8d3bf9c5392, but the patched version is 0.0.0-20220314234659-1baeb1ce4c0b. To fix the vulnerability, we recommend modifying the go.mod file to update the version to 0.0.0-20220314234659-1baeb1ce4c0b or higher.
the golang.org/x/sys package is being used at version golang.org/x/sys v0.0.0-20200223170610-d5e6a3e2c0ae, but the patched version is v0.1.0. To fix the vulnerability, we recommend modifying the go.mod file to update the version to v0.1.0 or higher.
Thank you for your attention to this matter.