CVE-2019-17596

Public Exploit

Description

Go before 1.12.11 and 1.3.x before 1.13.2 can panic upon an attempt to process network traffic containing an invalid DSA public key. There are several attack scenarios, such as traffic from a client to a server that verifies client certificates.

Category

7.5
CVSS
Severity: High
CVSS 3.1 •
CVSS 2.0 •
EPSS 5.92% Top 10%
Vendor Advisory debian.org Vendor Advisory fedoraproject.org Vendor Advisory fedoraproject.org Vendor Advisory opensuse.org Vendor Advisory opensuse.org Vendor Advisory redhat.com Vendor Advisory redhat.com
Affected: n/a n/a
Published at:
Updated at:

References

Link Tags
https://groups.google.com/d/msg/golang-announce/lVEm7llp0w0/VbafyRkgCgAJ third party advisory release notes
https://github.com/golang/go/issues/34960 patch exploit third party advisory issue tracking
https://www.debian.org/security/2019/dsa-4551 third party advisory vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/5VS3HPSE25ZSGS4RSOTADC67YNOHIGVV/ vendor advisory
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/WVOWGM7IQGRO7DS2MCUMYZRQ4TYOZNAS/ vendor advisory
http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00043.html vendor advisory mailing list third party advisory
http://lists.opensuse.org/opensuse-security-announce/2019-11/msg00044.html vendor advisory mailing list third party advisory
https://security.netapp.com/advisory/ntap-20191122-0005/ third party advisory
https://access.redhat.com/errata/RHSA-2020:0101 third party advisory vendor advisory
https://access.redhat.com/errata/RHSA-2020:0329 third party advisory vendor advisory
https://lists.debian.org/debian-lts-announce/2021/03/msg00014.html third party advisory mailing list
https://lists.debian.org/debian-lts-announce/2021/03/msg00015.html third party advisory mailing list
https://www.arista.com/en/support/advisories-notices/security-advisories/10134-security-advisory-46 third party advisory

Frequently Asked Questions

What is the severity of CVE-2019-17596?
CVE-2019-17596 has been scored as a high severity vulnerability.
How to fix CVE-2019-17596?
To fix CVE-2019-17596, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2019-17596 being actively exploited in the wild?
It is possible that CVE-2019-17596 is being exploited or will be exploited in a near future based on public information. According to its EPSS score, there is a ~6% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.