Skip to content

Conversation

@chncaption
Copy link

What happened?

There are 1 security vulnerabilities found in golang.org/x/sys v0.0.0-20220503163025-988cb79eb6c6

What did I do?

Upgrade golang.org/x/sys from v0.0.0-20220503163025-988cb79eb6c6 to 0.1.0 for vulnerability fix

What did you expect to happen?

Ideally, no insecure libs should be used.

How can we automate the detection of these types of issues?

By using the GitHub Actions configurations provided by murphysec, we can conduct automatic code security checks in our CI pipeline.

The specification of the pull request

PR Specification from OSCS

@chncaption chncaption requested a review from a team as a code owner September 11, 2023 13:00
@chncaption chncaption requested review from banks and removed request for a team September 11, 2023 13:00
@ncabatoff
Copy link
Contributor

Hi @chncaption,

I'm curious why you've chosen such an old version of x/sys to move to? I see that it's the newest version available newer than that we have now, but it probably makes sense to use the newest one available. Would you mind updating the PR please?

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 this pull request may close these issues.

2 participants