First published: Tue Feb 25 2014(Updated: )
It was discovered that GnuTLS X.509 certificate verification code failed to properly handle certain errors that can occur during the certificate verification. When such errors are encountered, GnuTLS would report successful verification of the certificate, even though verification should end with failure. A specially-crafted certificate can be accepted by GnuTLS as valid even if it wasn't issued by any trusted Certificate Authority. This can be used to perform man-in-the-middle attacks against applications using GnuTLS.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/gnutls | <3.1.22 | 3.1.22 |
redhat/gnutls | <3.2.12 | 3.2.12 |
GNU GnuTLS | <=3.2.11 | |
GNU GnuTLS | =3.2.0 | |
GNU GnuTLS | =3.2.1 | |
GNU GnuTLS | =3.2.2 | |
GNU GnuTLS | =3.2.3 | |
GNU GnuTLS | =3.2.4 | |
GNU GnuTLS | =3.2.5 | |
GNU GnuTLS | =3.2.6 | |
GNU GnuTLS | =3.2.7 | |
GNU GnuTLS | =3.2.8 | |
GNU GnuTLS | =3.2.8.1 | |
GNU GnuTLS | =3.2.9 | |
GNU GnuTLS | =3.2.10 | |
GNU GnuTLS | <=3.1.21 | |
GNU GnuTLS | =3.1.0 | |
GNU GnuTLS | =3.1.1 | |
GNU GnuTLS | =3.1.2 | |
GNU GnuTLS | =3.1.3 | |
GNU GnuTLS | =3.1.4 | |
GNU GnuTLS | =3.1.5 | |
GNU GnuTLS | =3.1.6 | |
GNU GnuTLS | =3.1.7 | |
GNU GnuTLS | =3.1.8 | |
GNU GnuTLS | =3.1.9 | |
GNU GnuTLS | =3.1.10 | |
GNU GnuTLS | =3.1.11 | |
GNU GnuTLS | =3.1.12 | |
GNU GnuTLS | =3.1.13 | |
GNU GnuTLS | =3.1.14 | |
GNU GnuTLS | =3.1.15 | |
GNU GnuTLS | =3.1.16 | |
GNU GnuTLS | =3.1.17 | |
GNU GnuTLS | =3.1.18 | |
GNU GnuTLS | =3.1.19 | |
GNU GnuTLS | =3.1.20 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.