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

x/vulndb: suggestion regarding GO-2022-0646 #3285

Open
jcmackie opened this issue Nov 22, 2024 · 0 comments
Open

x/vulndb: suggestion regarding GO-2022-0646 #3285

jcmackie opened this issue Nov 22, 2024 · 0 comments

Comments

@jcmackie
Copy link

Report ID

GO-2022-0646

Suggestion/Comment

Hello team,

I wanted to let you know that we've recently become aware that aws-sdk-go is still vulnerable to CVE-2020-8911.

CVE-2020-8911 is listed as an alias of GO-2022-0646, which I think might not be true as they are different vulnerabilities, I believe.

You can see where some other sites classify even the latest version of this library as still vulnerable:
https://nvd.nist.gov/vuln/detail/cve-2020-8911

Up to (excluding) 2.0

https://www.cve.org/CVERecord?id=CVE-2020-8911

affected from stable through V1

We have even confirmed with AWS themselves that the V1 clients which are still part of the SDK are still vulnerable to this issue.
They have decided to keep them in the library and accessible for compatibility reasons.

If you can update the status for your VULN DB for this library, that will make it easier for teams and projects to understand the risk, and hopefully encourage them to upgrade to V2.

Regards,
James Mackie

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant