chore: Fix the security issue about sirupsen/logrus

[kevinwangcn]

There is a security concern using the github.com/sirupsen/logrus with version 1.8.1

Supporting Material/References:
sirupsen/logrus#1370

Impact
This happens if you try to log something that is longer than 64kb without newlines through something like cmd.Stdout = logrus.Writer().
This can cause a denial of service in some cases.

What this PR does / why we need it:
The PR is going to bump up the version for this particular module from 1.8.1 to 1.9.3 which has resolved the security issue.

How does this change affect the cardinality of KSM: (increases, decreases or does not change cardinality)

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[linux-foundation-easycla]

• ✅login: kevinwangcn / (ba9eb94)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

This issue is currently awaiting triage.

If kube-state-metrics contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

Welcome @kevinwangcn!

It looks like this is your first PR to kubernetes/kube-state-metrics 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kube-state-metrics has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[CatherineF-dev]

Can you use go get github.com/sirupsen/logrus@v1.9.3 instead of replace?

[kevinwangcn]

Can you use go get github.com/sirupsen/logrus@v1.9.3 instead of replace?

Updated my PR. thanks for the review.

[rexagod]

Is there a CVE for this vulnerability? Does golvulncheck validate that the affected symbols are actually being used in the codebase?

[kevinwangcn]

Is there a CVE for this vulnerability? Does golvulncheck validate that the affected symbols are actually being used in the codebase?

yes, this is going to solve a CVE issue. Attached is the scan report via Twistlock. Please refer to it for more details.
scan-result.csv

[kevinwangcn]

@rexagod @CatherineF-dev Could you please review my PR? Thanks a lot.

[CatherineF-dev]

/lgtm

[mrueg]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CatherineF-dev, kevinwangcn, mrueg

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mrueg]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment