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

fix(deps): updated vulnerable dependencies #1567

Closed
wants to merge 20 commits into from

Conversation

rootxrishabh
Copy link
Member

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:

  • Bug fix. Fixes #
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update
  • PR Title follows the convention of <type>(<scope>): <subject>
  • Commit has unit tests
  • Commit has integration tests

@DelusionalOptimist
Copy link
Member

@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. 🤔

k8s.io/api => k8s.io/api v0.26.4
k8s.io/apimachinery => k8s.io/apimachinery v0.26.4
k8s.io/client-go => k8s.io/client-go v0.26.4

@rootxrishabh
Copy link
Member Author

@DelusionalOptimist I'll get it done.

@rootxrishabh
Copy link
Member Author

@DelusionalOptimist There are some build errors, fixing them might require dependency updates. If yes, should we upgrade dependencies across Kubearmor?

@rootxrishabh
Copy link
Member Author

Kubearmor Controller uses configurations such as MetricsBindAddress and port which were present in current package controller-runtime:0.14.x but have been removed in latest. Should we explore to reconfigure the controller or stick to old release?

Signed-off-by: rootxrishabh <[email protected]>
Signed-off-by: rootxrishabh <[email protected]>
@rootxrishabh
Copy link
Member Author

libbpf-based vulnerabilities are still present as the patch is yet to be released across all releases.

@rootxrishabh
Copy link
Member Author

Kubearmor Controller uses configurations such as MetricsBindAddress and port which were present in current package controller-runtime:0.14.x but have been removed in latest. Should we explore to reconfigure the controller or stick to old release?

Shifting to an older release makes sense as of now.

@rootxrishabh
Copy link
Member Author

@nyrahul failing snyk tests require maintainers access, could you please take a look?

@DelusionalOptimist
Copy link
Member

Kubearmor Controller uses configurations such as MetricsBindAddress and port which were present in current package controller-runtime:0.14.x but have been removed in latest. Should we explore to reconfigure the controller or stick to old release?

Shifting to an older release makes sense as of now.

Sure, we can handle these later as per need. 👍

Copy link
Member

@DelusionalOptimist DelusionalOptimist left a 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. 👍

pkg/KubeArmorController/go.mod Outdated Show resolved Hide resolved
@DelusionalOptimist
Copy link
Member

libbpf-based vulnerabilities are still present as the patch is yet to be released across all releases.

cc @daemon1024

@daemon1024
Copy link
Member

daemon1024 commented Jan 12, 2024

I believe the libbpf vulnerability is due it existing as a submodule right?
I have created this issue to track that #1580
Even if the fix is released, it won't be a simple update for us.

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
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

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?

Copy link
Member Author

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) ?

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Member Author

@rootxrishabh rootxrishabh Jan 19, 2024

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?

@rootxrishabh rootxrishabh linked an issue Jan 16, 2024 that may be closed by this pull request
15 tasks
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]>
DelusionalOptimist and others added 6 commits January 22, 2024 11:38
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]>
Signed-off-by: rootxrishabh <[email protected]>
@rootxrishabh rootxrishabh deleted the updateDependencies branch January 24, 2024 19:13
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.

Improve Scorecard Score for Kubearmor
4 participants