fix(SEC): Fixing CVE-2021-31525

[sanjayk-github-dev]

Problem

CVE-2021-31525

Solution

Fixing CVE-2021-31525 by bumping version

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

Sanjay Kshetramade seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[skrdgraph]

this will probably fix other CVEs as well.

[sanjayk-github-dev]

@skrdgraph I changed this to address CVE-2021-31525. However go mod tidy made additional changes.

[skrdgraph]

yes this is true, the current sec-CVE count is at 70 (before merging this PR). The other fixes that came in through go mod tidy will be addressing other CVEs for sure. We can look at the CVE count after this merge. We are expecting the number to drop to 69, but if it goes further below - it simply means we have fixed more CVEs with this single PR.

[meghalims]

Looks good 👍 .
Please sign the CLA

[sanjayk-github-dev]

Looks good 👍 . Please sign the CLA

@meghalims I have signed the CLA, but it takes a day to reflect per @skrdgraph .

[meghalims]

Looks good 👍 . Please sign the CLA

@meghalims I have signed the CLA, but it takes a day to reflect per @skrdgraph .

Ahh yes. Thanks Sanjay