-
Notifications
You must be signed in to change notification settings - Fork 3.5k
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
vendor: golang.org/x/text v0.3.3 (CVE-2020-14040) #4328
Conversation
full diff: golang/text@19e5161...v0.3.3 includes a fix for [CVE-2020-14040][1] [1]: https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2020-14040 Signed-off-by: Sebastiaan van Stijn <[email protected]>
perhaps needs to be back ported to 1.2.x and 1.3.x |
Build succeeded.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
@estesp ok to add this to 1.3 (possibly 1.2) backports you think? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
How might this CVE affect 1.2.x or 1.3.x. The fix seems related to handling utf16. If this bug is manifesting in the network code, is there more details about it and how I think more justification is needed before backporting, especially to 1.2 with such a large diff. |
Similar thoughts from me in the 1.2 backport PR: #4331 (comment) |
full diff: golang/text@19e5161...v0.3.3
includes a fix for CVE-2020-14040