-
Notifications
You must be signed in to change notification settings - Fork 357
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
fix(deps): updated vulnerable dependencies #1567
Conversation
Signed-off-by: rootxrishabh <[email protected]>
@rootxrishabh can you try by removing these k8s.io replace directives across KubeArmor's and other go.mod files? I think it should fix the current build failure. 🤔 Lines 22 to 24 in 2142379
|
@DelusionalOptimist I'll get it done. |
Signed-off-by: rootxrishabh <[email protected]>
@DelusionalOptimist There are some build errors, fixing them might require dependency updates. If yes, should we upgrade dependencies across Kubearmor? |
Kubearmor Controller uses configurations such as MetricsBindAddress and port which were present in current package |
Signed-off-by: rootxrishabh <[email protected]>
Signed-off-by: rootxrishabh <[email protected]>
libbpf-based vulnerabilities are still present as the patch is yet to be released across all releases. |
Shifting to an older release makes sense as of now. |
@nyrahul failing snyk tests require maintainers access, could you please take a look? |
Sure, we can handle these later as per need. 👍 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
All other updates look good. 👍
cc @daemon1024 |
I believe the libbpf vulnerability is due it existing as a submodule right? |
protobuf/go.mod
Outdated
golang.org/x/net v0.10.0 // indirect | ||
golang.org/x/sys v0.8.0 // indirect | ||
golang.org/x/text v0.9.0 // indirect | ||
golang.org/x/net v0.17.0 // indirect |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://security.snyk.io/vuln/SNYK-GOLANG-GOLANGORGXCRYPTOSSH-6130669
golang.org/x/[email protected] › golang.org/x/[email protected]
Snyk failure cause
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgraded to golang.org/x/[email protected] uses golang.org/x/crypto v0.18.0, still snyk fails. Am I missing something?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Upgraded to golang.org/x/[email protected] uses golang.org/x/crypto v0.18.0, still snyk fails. Am I missing something?
Solved!
Could you provide a bit more insight on security/snyk (nyrahul)
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
https://security.snyk.io/vuln/SNYK-GOLANG-GITHUBCOMGOJOSEGOJOSE-6070736
Snyk failure cause
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@Aryan-sharma11 I test all our go.mod files using snyk CLI. Other than golang.org/x/net/[email protected]
(low risk vuln, fix yet to implemented upstream) I can't find any vulnerability. Also, github.com/go-jose/go-jose is a transitive dependency to a package. Can we ignore this?
Signed-off-by: Rudraksh Pareek <[email protected]>
Signed-off-by: Rudraksh Pareek <[email protected]>
Signed-off-by: Rudraksh Pareek <[email protected]>
Signed-off-by: Rudraksh Pareek <[email protected]>
Signed-off-by: Rudraksh Pareek <[email protected]>
Signed-off-by: Rudraksh Pareek <[email protected]>
Signed-off-by: Rudraksh Pareek <[email protected]>
4173b3c
to
bf74f1f
Compare
Signed-off-by: rootxrishabh <[email protected]> standardized controller-runtime version Signed-off-by: rootxrishabh <[email protected]> x/net updated Signed-off-by: rootxrishabh <[email protected]> Tested snyk locally Signed-off-by: rootxrishabh <[email protected]> test changes reverted Signed-off-by: rootxrishabh <[email protected]> controller-runtime version reverted Signed-off-by: rootxrishabh <[email protected]> version reverted to 1.20 Signed-off-by: rootxrishabh <[email protected]> test go.mod updated Signed-off-by: rootxrishabh <[email protected]> test go.mod updated Signed-off-by: rootxrishabh <[email protected]> Errors fixed Signed-off-by: rootxrishabh <[email protected]>
Signed-off-by: rootxrishabh <[email protected]>
bf74f1f
to
13992dd
Compare
Signed-off-by: Rudraksh Pareek <[email protected]>
…ptimist/feat/extended-vm-support feat(*): extended VM support
We did not have fallback logic to read from procfs in case of operation File/Network Enabled the fallback logic for file/network telemetry Signed-off-by: daemon1024 <[email protected]>
fix(monitor): Missing Source in Telemetry
Signed-off-by: rootxrishabh <[email protected]>
…KubeArmor into updateDependencies Signed-off-by: rootxrishabh <[email protected]>
Purpose of PR?:
This PR updates all the vulnerable dependencies alerted by the OSSF scorecard.
Fixes #
#1532
Does this PR introduce a breaking change?
No
If the changes in this PR are manually verified, list down the scenarios covered::
Additional information for reviewer? :
Mention if this PR is part of any design or a continuation of previous PRs
Checklist:
<type>(<scope>): <subject>