First published: Tue Jun 07 2016(Updated: )
It was reported that gnutls 3.4.12 uses an environment variable (GNUTLS_KEYLOGFILE) to write the keys of the running sessions. This variable is obtained insecurely via getenv(), meaning that any set-uid program using gnutls can be used to overwrite any file on the filesystem. Upstream patch: <a href="https://gitlab.com/gnutls/gnutls/compare/fb2a6baef79f4aadfd95e657fe5a18da20a1410e...86076c9b17b9a32b348cafb8b724f57f7da64d58">https://gitlab.com/gnutls/gnutls/compare/fb2a6baef79f4aadfd95e657fe5a18da20a1410e...86076c9b17b9a32b348cafb8b724f57f7da64d58</a> External References: <a href="http://gnutls.org/security.html#GNUTLS-SA-2016-1">http://gnutls.org/security.html#GNUTLS-SA-2016-1</a>
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/gnutls | <3.4.13 | 3.4.13 |
GnuTLS | =3.4.12 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2016-4456 has a medium severity level due to potential unauthorized file access.
To fix CVE-2016-4456, upgrade the gnutls package to version 3.4.13 or later.
The impact of CVE-2016-4456 enables a set-uid program using gnutls to overwrite any file on the filesystem.
CVE-2016-4456 affects gnutls version 3.4.12 and earlier.
Yes, CVE-2016-4456 specifically affects the gnutls software package.