It was discovered in gnutls before version 3.6.7 upstream that there is an uninitialized pointer access in gnutls versions 3.6.3 or later which can be triggered by certain post-handshake messages.
The product does not initialize critical variables, which causes the execution environment to use unexpected values.
The product accesses or uses a pointer that has not been initialized.
Link | Tags |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-3836 | issue tracking third party advisory |
https://gitlab.com/gnutls/gnutls/issues/704 | issue tracking exploit third party advisory |
https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/A3ETBUFBB4G7AITAOUYPGXVMBGVXKUAN/ | vendor advisory |
https://security.gentoo.org/glsa/201904-14 | third party advisory vendor advisory |
https://security.netapp.com/advisory/ntap-20190502-0005/ | third party advisory |
http://lists.opensuse.org/opensuse-security-announce/2019-05/msg00017.html | mailing list third party advisory vendor advisory |
https://usn.ubuntu.com/3999-1/ | vendor advisory |
https://access.redhat.com/errata/RHSA-2019:3600 | vendor advisory |