medium
4
CWE
310
Advisory Published
Updated

CVE-2013-1619

First published: Mon Feb 04 2013(Updated: )

A flaw in how TLS/DTLS, when CBC-mode encryption is used, communicates was reported. This vulnerability can allow for a Man-in-the-Middle attacker to recover plaintext from a TLS/DTLS connection, when CBC-mode encryption is used. This flaw is in the TLS specification, and not a bug in a specific implementation (as such, it affects nearly all implementations). As such, it affects all TLS and DTLS implementations that are compliant with TLS 1.1 or 1.2, or with DTLS 1.0 or 1.2. It also applies to implementations of SSL 3.0 and TLS 1.0 that incorporate countermeasures to deal with previous padding oracle attacks. All TLS/DTLS ciphersuites that include CBC-mode encryption are potentially vulnerable. The paper indicates that with OpenSSL, a full plaintext recovery attack is possible, and with GnuTLS, a partial plaintext recovery is possible (recovering up to 4 bits of the last byte in any block of plaintext). To perform a successful attack, when TLS is used, a large number of TLS sessions are required (target plaintext must be sent repeatedly in the same position in the plaintext stream across the sessions). For DTLS, a successful attack can be carried out in a single session. The attacker must also be located close to the machine being attacked. Further details are noted in the paper: <a href="http://www.isg.rhul.ac.uk/tls/TLStiming.pdf">http://www.isg.rhul.ac.uk/tls/TLStiming.pdf</a> External References: <a href="http://www.isg.rhul.ac.uk/tls/">http://www.isg.rhul.ac.uk/tls/</a> <a href="http://www.gnutls.org/security.html#GNUTLS-SA-2013-1">http://www.gnutls.org/security.html#GNUTLS-SA-2013-1</a> Patches: 2.12.x: <a href="https://gitorious.org/gnutls/gnutls/commit/458c67cf98740e7b12404f6c30e0d5317d56fd30">https://gitorious.org/gnutls/gnutls/commit/458c67cf98740e7b12404f6c30e0d5317d56fd30</a> <a href="https://gitorious.org/gnutls/gnutls/commit/93b7fcfa3297a9123630704668b2946f602b910e">https://gitorious.org/gnutls/gnutls/commit/93b7fcfa3297a9123630704668b2946f602b910e</a> 3.0.x: <a href="https://gitorious.org/gnutls/gnutls/commit/8dc2822966f64dd9cf7dde9c7aacd80d49d3ffe5">https://gitorious.org/gnutls/gnutls/commit/8dc2822966f64dd9cf7dde9c7aacd80d49d3ffe5</a> 3.2.x / master: <a href="https://gitorious.org/gnutls/gnutls/commit/328ee22c1b3951e060c7124c7cb1cee592c59bc0">https://gitorious.org/gnutls/gnutls/commit/328ee22c1b3951e060c7124c7cb1cee592c59bc0</a>

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
redhat/gnutls<0:1.4.1-10.el5_9.1
0:1.4.1-10.el5_9.1
redhat/gnutls<0:2.8.5-10.el6_4.1
0:2.8.5-10.el6_4.1
redhat/rhev-hypervisor6<0:6.4-20130306.2.el6_4
0:6.4-20130306.2.el6_4
redhat/gnutls<2.12.23
2.12.23
redhat/gnutls<3.0.28
3.0.28
redhat/gnutls<3.1.7
3.1.7
GnuTLS=2.0.0
GnuTLS=2.0.1
GnuTLS=2.0.2
GnuTLS=2.0.3
GnuTLS=2.0.4
GnuTLS=2.1.0
GnuTLS=2.1.1
GnuTLS=2.1.2
GnuTLS=2.1.3
GnuTLS=2.1.4
GnuTLS=2.1.5
GnuTLS=2.1.6
GnuTLS=2.1.7
GnuTLS=2.1.8
GnuTLS=2.2.0
GnuTLS=2.2.1
GnuTLS=2.2.2
GnuTLS=2.2.3
GnuTLS=2.2.4
GnuTLS=2.2.5
GnuTLS=2.3.0
GnuTLS=2.3.1
GnuTLS=2.3.2
GnuTLS=2.3.3
GnuTLS=2.3.4
GnuTLS=2.3.5
GnuTLS=2.3.6
GnuTLS=2.3.7
GnuTLS=2.3.8
GnuTLS=2.3.9
GnuTLS=2.3.10
GnuTLS=2.3.11
GnuTLS=2.4.0
GnuTLS=2.4.1
GnuTLS=2.4.2
GnuTLS=2.4.3
GnuTLS=2.5.0
GnuTLS=2.6.0
GnuTLS=2.6.1
GnuTLS=2.6.2
GnuTLS=2.6.3
GnuTLS=2.6.4
GnuTLS=2.6.5
GnuTLS=2.6.6
GnuTLS=2.7.4
GnuTLS=2.8.0
GnuTLS=2.8.1
GnuTLS=2.8.2
GnuTLS=2.8.3
GnuTLS=2.8.4
GnuTLS=2.8.5
GnuTLS=2.8.6
GnuTLS=2.10.0
GnuTLS=2.10.1
GnuTLS=2.10.2
GnuTLS=2.10.3
GnuTLS=2.10.4
GnuTLS=2.10.5
GnuTLS=2.12.0
GnuTLS=2.12.1
GnuTLS=2.12.2
GnuTLS=2.12.3
GnuTLS=2.12.4
GnuTLS=2.12.5
GnuTLS=2.12.6
GnuTLS=2.12.6.1
GnuTLS=2.12.7
GnuTLS=2.12.8
GnuTLS=2.12.9
GnuTLS=2.12.10
GnuTLS=2.12.11
GnuTLS=2.12.12
GnuTLS=2.12.13
GnuTLS=2.12.14
GnuTLS=2.12.15
GnuTLS=2.12.16
GnuTLS=2.12.17
GnuTLS=2.12.18
GnuTLS=2.12.19
GnuTLS=2.12.20
GnuTLS=2.12.21
GnuTLS=2.12.22
GnuTLS=3.0
GnuTLS=3.0.0
GnuTLS=3.0.1
GnuTLS=3.0.2
GnuTLS=3.0.3
GnuTLS=3.0.4
GnuTLS=3.0.5
GnuTLS=3.0.6
GnuTLS=3.0.7
GnuTLS=3.0.8
GnuTLS=3.0.9
GnuTLS=3.0.10
GnuTLS=3.0.11
GnuTLS=3.0.12
GnuTLS=3.0.13
GnuTLS=3.0.14
GnuTLS=3.0.15
GnuTLS=3.0.16
GnuTLS=3.0.17
GnuTLS=3.0.18
GnuTLS=3.0.19
GnuTLS=3.0.20
GnuTLS=3.0.21
GnuTLS=3.0.22
GnuTLS=3.0.23
GnuTLS=3.0.24
GnuTLS=3.0.25
GnuTLS=3.0.26
GnuTLS=3.0.27
GnuTLS=3.1.0
GnuTLS=3.1.1
GnuTLS=3.1.2
GnuTLS=3.1.3
GnuTLS=3.1.4
GnuTLS=3.1.5
GnuTLS=3.1.6

Remedy

https://gitorious.org/gnutls/gnutls/commit/328ee22c1b3951e060c7124c7cb1cee592c59bc0

Remedy

https://gitorious.org/gnutls/gnutls/commit/b8391806cd79095fe566f2401d8c7ad85a64b198

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Read MoreStart Free Trial

Reference Links

Parent vulnerabilities

(Appears in the following advisories)

Frequently Asked Questions

  • What is the severity of CVE-2013-1619?

    CVE-2013-1619 has a medium severity rating, indicating it could allow a Man-in-the-Middle attacker to exploit TLS/DTLS connections.

  • How do I fix CVE-2013-1619?

    To fix CVE-2013-1619, update to GnuTLS versions 2.12.23, 3.0.28, or later versions that have patched this vulnerability.

  • Which software is affected by CVE-2013-1619?

    CVE-2013-1619 affects multiple versions of GnuTLS, particularly those before 2.12.23 and 3.0.28.

  • What type of attack can exploit vulnerabilities in CVE-2013-1619?

    CVE-2013-1619 can be exploited through Man-in-the-Middle attacks that recover plaintext data from TLS/DTLS connections.

  • Is there a workaround for CVE-2013-1619 until I can update?

    There is no permanent workaround for CVE-2013-1619 other than upgrading to a secure version of GnuTLS.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2025 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203