First published: Wed Feb 12 2014(Updated: )
It was reported [1] that a version 1 intermediate certificate would be considered as a CA certificate by GnuTLS by default. This certificate verification behaviour deviates from the documented behaviour. Upstream notes that this only affects individuals or organizations who have a CA that issues X.509 version 1 certificates in their trusted list. This has been fixed upstream [2] in version 3.1.21 and 3.2.11. At a quick look at the code of GnuTLS 2.8.5, it is affected. 1.4.1 looks affected to me as well. [1] <a href="http://www.gnutls.org/security.html">http://www.gnutls.org/security.html</a> [2] <a href="https://www.gitorious.org/gnutls/gnutls/commit/b1abfe3d18">https://www.gitorious.org/gnutls/gnutls/commit/b1abfe3d18</a>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/gnutls | <3.1.21 | 3.1.21 |
redhat/gnutls | <3.2.11 | 3.2.11 |
GNU GnuTLS | <=3.1.20 | |
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.2.10 | |
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.