Skip to content

Conversation

cpu
Copy link
Member

@cpu cpu commented Jan 29, 2020

This addresses CVE-2020-7919, announced in the Go 1.13.7 security update:

On 32-bit architectures, a malformed input to crypto/x509 or the ASN.1 parsing functions of golang.org/x/crypto/cryptobyte can lead to a panic.

CI doesn't need an explicit update to this Golang point release because we use 1.13.x:

zlint/.travis.yml

Lines 5 to 6 in 77026f6

go:
- "1.13.x"

This addresses CVE-2020-7919[0]:

> On 32-bit architectures, a malformed input to crypto/x509 or the ASN.1
parsing functions of golang.org/x/crypto/cryptobyte can lead to a panic.

[0]: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/golang-announce/Hsw4mHYc470/WJeW5wguEgAJ
@cpu cpu requested a review from zakird January 29, 2020 16:05
@cpu cpu self-assigned this Jan 29, 2020
@zakird zakird merged commit 1107123 into zmap:master Jan 29, 2020
@cpu cpu deleted the cpu-bump-cryptobyte branch January 29, 2020 17:00
pkoro pushed a commit to pkoro/zlint that referenced this pull request Feb 2, 2020
This addresses CVE-2020-7919[0]:

> On 32-bit architectures, a malformed input to crypto/x509 or the ASN.1
parsing functions of golang.org/x/crypto/cryptobyte can lead to a panic.

[0]: https://groups.google.com/forum/?utm_medium=email&utm_source=footer#!msg/golang-announce/Hsw4mHYc470/WJeW5wguEgAJ
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants