Package "libgnutls28-dev"
| Name: |
libgnutls28-dev
|
Description: |
GNU TLS library - development files
|
| Latest version: |
3.5.18-1ubuntu1.6 |
| Release: |
bionic (18.04) |
| Level: |
security |
| Repository: |
main |
| Head package: |
gnutls28 |
| Homepage: |
http://www.gnutls.org/ |
Links
Download "libgnutls28-dev"
Other versions of "libgnutls28-dev" in Bionic
Changelog
|
gnutls28 (3.5.18-1ubuntu1.6) bionic-security; urgency=medium
* SECURITY UPDATE: Null pointer dereference in MD_UPDATE
- debian/patches/CVE-2021-4209.patch: avoid calling _update with
zero-length input in lib/nettle/mac.c.
- CVE-2021-4209
* SECURITY UPDATE: Double free in verification of pkcs7 signatures
- debian/patches/CVE-2022-2509.patch: fix double free during
gnutls_pkcs7_verify in lib/x509/pkcs7.c,
tests/pkcs7-verify-double-free.c, tests/Makefile.am.
- CVE-2022-2509
-- Marc Deslauriers <email address hidden> Tue, 02 Aug 2022 08:58:39 -0400
|
| Source diff to previous version |
| CVE-2022-2509 |
A vulnerability found in gnutls. This security flaw happens because of a double free error occurs during verification of pkcs7 signatures in gnutls_p |
|
|
gnutls28 (3.5.18-1ubuntu1.3) bionic-security; urgency=medium
* SECURITY UPDATE: Allow re-enabling SHA1 for certificate signing with a
priority string (LP: #1860656)
- debian/patches/allow_broken_priority_string.patch: introduce the
%VERIFY_ALLOW_BROKEN priority string option.
- debian/patches/allow_sha1_priority_string.patch: introduce the
%VERIFY_ALLOW_SIGN_WITH_SHA1 priority string option.
-- Marc Deslauriers <email address hidden> Thu, 23 Jan 2020 08:39:38 -0500
|
| Source diff to previous version |
| 1860656 |
SHA1 security update regression prohibits connectivity |
|
|
gnutls28 (3.5.18-1ubuntu1.2) bionic-security; urgency=medium
* SECURITY UPDATE: Mark SHA1 as insecure for certificate signing
- debian/patches/insecuresha1-*.patch: backport upstream patches to
allow marking SHA1 as insecure, but only for certificate signing.
- debian/libgnutls30.symbols: added new symbol.
-- Marc Deslauriers <email address hidden> Wed, 08 Jan 2020 10:39:00 -0500
|
| Source diff to previous version |
|
gnutls28 (3.5.18-1ubuntu1.1) bionic-security; urgency=medium
* SECURITY UPDATE: Lucky-13 issues
- debian/patches/CVE-2018-1084x-1.patch: correctly account the length
field in SHA384 HMAC in lib/algorithms/mac.c, lib/cipher.c.
- debian/patches/CVE-2018-1084x-2.patch: always hash the same amount of
blocks that would have been on minimum pad in lib/cipher.c.
- debian/patches/CVE-2018-1084x-3.patch: require minimum padding under
SSL3.0 in lib/cipher.c.
- debian/patches/CVE-2018-1084x-4.patch: hmac-sha384 and sha256
ciphersuites were removed from defaults in lib/priority.c,
tests/dtls1-2-mtu-check.c, tests/priorities.c.
- debian/patches/CVE-2018-1084x-5.patch: fix test for SHA512 in
tests/pkcs12_encode.c.
- CVE-2018-10844
- CVE-2018-10845
- CVE-2018-10846
* SECURITY UPDATE: double free in cert verification API
- debian/patches/CVE-2019-3829-1.patch: automatically NULLify after
gnutls_free() in lib/includes/gnutls/gnutls.h.in.
- debian/patches/CVE-2019-3829-2.patch: fix some casts in
lib/extensions.c.
- debian/patches/CVE-2019-3829-3.patch: fix dereference of NULL pointer
in lib/x509/x509.c.
- CVE-2019-3829
-- Marc Deslauriers <email address hidden> Tue, 28 May 2019 13:18:12 -0400
|
| CVE-2018-1084 |
corosync before version 2.4.4 is vulnerable to an integer overflow in exec/totemcrypto.c. |
| CVE-2018-10844 |
It was found that the GnuTLS implementation of HMAC-SHA-256 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to |
| CVE-2018-10845 |
It was found that the GnuTLS implementation of HMAC-SHA-384 was vulnerable to a Lucky thirteen style attack. Remote attackers could use this flaw to |
| CVE-2018-10846 |
A cache-based side channel in GnuTLS implementation that leads to plain text recovery in cross-VM attack setting was found. An attacker could use a c |
| CVE-2019-3829 |
A vulnerability was found in gnutls versions from 3.5.8 before 3.6.7. A memory corruption (double free) vulnerability in the certificate verification |
|
About
-
Send Feedback to @ubuntu_updates
