Replies: 1 comment
|
We've been discussing this internally and it didn't seem necessary, but I don't see why we couldn't. So I requested a CVE through GitHub. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
In order to avoid confusion when a future security advisory for Go uses CVE-2020-295[9,10,11] I recommend we issue a unique CVE for this issue. As a CNA Red Hat is able to issue a CVE for this issue as it potential affects a Red Hat product. Would you like us to issue a CVE for this issue?
All reactions