medium
4.3
CWE
310
Advisory Published
Updated

CVE-2013-1623

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. External References: <a href="http://www.isg.rhul.ac.uk/tls/">http://www.isg.rhul.ac.uk/tls/</a> <a href="http://www.isg.rhul.ac.uk/tls/TLStiming.pdf">http://www.isg.rhul.ac.uk/tls/TLStiming.pdf</a>

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
yaSSL<=2.4.6
yaSSL=0.2.0
yaSSL=0.3.0
yaSSL=0.4.0
yaSSL=0.5.0
yaSSL=0.5.5
yaSSL=0.6.0
yaSSL=0.6.2
yaSSL=0.6.3
yaSSL=0.8.0
yaSSL=0.9.0
yaSSL=0.9.6
yaSSL=0.9.8
yaSSL=0.9.9
yaSSL=1.0.0-rc1
yaSSL=1.0.0-rc2
yaSSL=1.0.0-rc3
yaSSL=1.0.2
yaSSL=1.0.3
yaSSL=1.0.6
yaSSL=1.1.0
yaSSL=1.2.0
yaSSL=1.3.0
yaSSL=1.4.0
yaSSL=1.5.0
yaSSL=1.5.4
yaSSL=1.5.6
yaSSL=1.6.0
yaSSL=1.6.5
yaSSL=1.8.0
yaSSL=1.9.0
yaSSL=2.0.0-rc1
yaSSL=2.0.0-rc2
yaSSL=2.0.0-rc3
yaSSL=2.0.2
yaSSL=2.0.6
yaSSL=2.0.8
yaSSL=2.2.0
yaSSL=2.3.0
yaSSL=2.4.0

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

Frequently Asked Questions

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

    CVE-2013-1623 is considered to have a high severity due to its potential to allow a Man-in-the-Middle attack.

  • How do I fix CVE-2013-1623?

    To remediate CVE-2013-1623, upgrade yaSSL to a version that addresses this vulnerability.

  • What systems are affected by CVE-2013-1623?

    CVE-2013-1623 affects various versions of yaSSL, including multiple version numbers up to 2.4.6.

  • What type of attack does CVE-2013-1623 enable?

    CVE-2013-1623 enables a Man-in-the-Middle attack allowing recovery of plaintext data from a TLS/DTLS connection.

  • Is CVE-2013-1623 a client-side or server-side vulnerability?

    CVE-2013-1623 can be exploited on both the client-side and the server-side due to how TLS/DTLS is implemented.

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