CVE-2013-0169: Low severity OpenSSL OpenSSL vulnerability

Published Feb 4, 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.

Current status of fixes in various implementations:

OpenSSL has a patch in development NSS has a patch in development GnuTLS is fixed in versions 2.12.23, 3.0.28, and 3.1.7 PolarSSL is fixed in version 1.2.5 BouncyCastle has a patch that will be included in the forthcoming 1.48 version

Full paper:

http://www.isg.rhul.ac.uk/tls/TLStiming.pdf

External References:

http://www.isg.rhul.ac.uk/tls/ http://www.openssl.org/news/secadv20130205.txt https://polarssl.org/tech-updates/releases/polarssl-1.2.5-released

Other sources

The TLS protocol 1.1 and 1.2 and the DTLS protocol 1.0 and 1.2, as used in OpenSSL, OpenJDK, PolarSSL, and other products, do not properly consider timing side-channel attacks on a MAC check requirement during the processing of malformed CBC padding, which allows remote attackers to conduct distinguishing attacks and plaintext-recovery attacks via statistical analysis of timing data for crafted packets, aka the "Lucky Thirteen" issue.

Affected Software

98 affected componentsFixes available
redhat/java<1.6.0-openjdk-1:1.6.0.0-1.35.1.11.8.el5_9
1.6.0-openjdk-1:1.6.0.0-1.35.1.11.8.el5_9
redhat/java<1.7.0-openjdk-1:1.7.0.9-2.3.7.1.el5_9
1.7.0-openjdk-1:1.7.0.9-2.3.7.1.el5_9
redhat/openssl<0:0.9.8e-26.el5_9.1
0:0.9.8e-26.el5_9.1
redhat/java<1.6.0-openjdk-1:1.6.0.0-1.56.1.11.8.el6_3
1.6.0-openjdk-1:1.6.0.0-1.56.1.11.8.el6_3
redhat/java<1.7.0-openjdk-1:1.7.0.9-2.3.7.1.el6_3
1.7.0-openjdk-1:1.7.0.9-2.3.7.1.el6_3
redhat/openssl<0:1.0.0-27.el6_4.2
0:1.0.0-27.el6_4.2
redhat/java<1.6.0-ibm-1:1.6.0.14.0-1jpp.1.el6_4
1.6.0-ibm-1:1.6.0.14.0-1jpp.1.el6_4
redhat/rhev-hypervisor6<0:6.4-20130306.2.el6_4
0:6.4-20130306.2.el6_4
redhat/java<1.6.0-sun-1:1.6.0.41-1jpp.1.el5_9
1.6.0-sun-1:1.6.0.41-1jpp.1.el5_9
redhat/java<1.7.0-oracle-1:1.7.0.15-1jpp.1.el5_9
1.7.0-oracle-1:1.7.0.15-1jpp.1.el5_9
redhat/java<1.7.0-ibm-1:1.7.0.4.2-1jpp.1.el5_9
1.7.0-ibm-1:1.7.0.4.2-1jpp.1.el5_9
redhat/java<1.6.0-ibm-1:1.6.0.13.2-1jpp.1.el5_9
1.6.0-ibm-1:1.6.0.13.2-1jpp.1.el5_9
redhat/java<1.5.0-ibm-1:1.5.0.16.2-1jpp.1.el5_9
1.5.0-ibm-1:1.5.0.16.2-1jpp.1.el5_9
redhat/java<1.6.0-sun-1:1.6.0.41-1jpp.1.el6_3
1.6.0-sun-1:1.6.0.41-1jpp.1.el6_3
redhat/java<1.7.0-oracle-1:1.7.0.15-1jpp.1.el6_3
1.7.0-oracle-1:1.7.0.15-1jpp.1.el6_3
redhat/java<1.7.0-ibm-1:1.7.0.4.2-1jpp.1.el6_4
1.7.0-ibm-1:1.7.0.4.2-1jpp.1.el6_4
redhat/java<1.6.0-ibm-1:1.6.0.13.2-1jpp.1.el6_4
1.6.0-ibm-1:1.6.0.13.2-1jpp.1.el6_4
redhat/java<1.5.0-ibm-1:1.5.0.16.2-1jpp.1.el6_4
1.5.0-ibm-1:1.5.0.16.2-1jpp.1.el6_4
redhat/openssl<1.0.1
1.0.1
redhat/openssl<0.9.8
0.9.8
redhat/polarssl<1.2.5
1.2.5
redhat/icedtea6<1.11.8
1.11.8
redhat/icedtea6<1.12.3
1.12.3
redhat/icedtea7<2.1.6
2.1.6
redhat/icedtea7<2.2.6
2.2.6
redhat/icedtea7<2.3.7
2.3.7
OpenSSL OpenSSL>=0.9.8<=0.9.8x
OpenSSL OpenSSL>=1.0.0<=1.0.0j
OpenSSL OpenSSL>=1.0.1<=1.0.1d
ORACLE OpenJDK=1.6.0
ORACLE OpenJDK=1.6.0-update1
ORACLE OpenJDK=1.6.0-update10
ORACLE OpenJDK=1.6.0-update11
ORACLE OpenJDK=1.6.0-update12
ORACLE OpenJDK=1.6.0-update13
ORACLE OpenJDK=1.6.0-update14
ORACLE OpenJDK=1.6.0-update15
ORACLE OpenJDK=1.6.0-update16
ORACLE OpenJDK=1.6.0-update17
ORACLE OpenJDK=1.6.0-update18
ORACLE OpenJDK=1.6.0-update19
ORACLE OpenJDK=1.6.0-update2
ORACLE OpenJDK=1.6.0-update20
ORACLE OpenJDK=1.6.0-update21
ORACLE OpenJDK=1.6.0-update22
ORACLE OpenJDK=1.6.0-update23
ORACLE OpenJDK=1.6.0-update24
ORACLE OpenJDK=1.6.0-update25
ORACLE OpenJDK=1.6.0-update26
ORACLE OpenJDK=1.6.0-update27
ORACLE OpenJDK=1.6.0-update29
ORACLE OpenJDK=1.6.0-update3
ORACLE OpenJDK=1.6.0-update30
ORACLE OpenJDK=1.6.0-update31
ORACLE OpenJDK=1.6.0-update32
ORACLE OpenJDK=1.6.0-update33
ORACLE OpenJDK=1.6.0-update34
ORACLE OpenJDK=1.6.0-update35
ORACLE OpenJDK=1.6.0-update37
ORACLE OpenJDK=1.6.0-update38
ORACLE OpenJDK=1.6.0-update4
ORACLE OpenJDK=1.6.0-update5
ORACLE OpenJDK=1.6.0-update6
ORACLE OpenJDK=1.6.0-update7
ORACLE OpenJDK=1.7.0
ORACLE OpenJDK=1.7.0-update1
ORACLE OpenJDK=1.7.0-update10
ORACLE OpenJDK=1.7.0-update11
ORACLE OpenJDK=1.7.0-update13
ORACLE OpenJDK=1.7.0-update2
ORACLE OpenJDK=1.7.0-update3
ORACLE OpenJDK=1.7.0-update4
ORACLE OpenJDK=1.7.0-update5
ORACLE OpenJDK=1.7.0-update6
ORACLE OpenJDK=1.7.0-update7
ORACLE OpenJDK=1.7.0-update9
PolarSSL PolarSSL=0.10.0
PolarSSL PolarSSL=0.10.1
PolarSSL PolarSSL=0.11.0
PolarSSL PolarSSL=0.11.1
PolarSSL PolarSSL=0.12.0
PolarSSL PolarSSL=0.12.1
PolarSSL PolarSSL=0.13.1
PolarSSL PolarSSL=0.14.0
PolarSSL PolarSSL=0.14.2
PolarSSL PolarSSL=0.14.3
PolarSSL PolarSSL=0.99-pre1
PolarSSL PolarSSL=0.99-pre3
PolarSSL PolarSSL=0.99-pre4
PolarSSL PolarSSL=0.99-pre5
PolarSSL PolarSSL=1.0.0
PolarSSL PolarSSL=1.1.0
PolarSSL PolarSSL=1.1.0-rc0
PolarSSL PolarSSL=1.1.0-rc1
PolarSSL PolarSSL=1.1.1
PolarSSL PolarSSL=1.1.2
PolarSSL PolarSSL=1.1.3
PolarSSL PolarSSL=1.1.4

Remediation

Information

On OpenShift Container Platform 3.11 it's possible to edit the list of cipher suites offered by the router when performing 'edge', or 're-encrypt' TLS modes. Please follow the documentation [1], and [2] to remove the vulnerable CBC ciphers use the modern, or intermediate cipher suites outlined by Mozilla instead [3]. In 'passthrough' mode TLS termination occurs in the application so that is another way to mitigate the vulnerability. [1] https://docs.openshift.com/container-platform/3.11/install_config/router/customized_haproxy_router.html#obtaining-router-configuration-template [2] https://docs.openshift.com/container-platform/3.11/install_config/router/customized_haproxy_router.html#using-configmap-replace-template [3] https://wiki.mozilla.org/Security/Server_Side_TLS

Event History

Feb 4, 2013
CVE Published
12:00 AM
Data Sourced
via Red Hat·07:16 PM
DescriptionSeverityAffected Software
Feb 8, 2013
CVE Published
via MITRE·07:00 PM
Data Sourced
via MITRE·07:00 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2013-0169?

CVE-2013-0169 is a critical vulnerability that allows a Man-in-the-Middle attacker to recover plaintext data from a TLS/DTLS connection.

2

How do I fix CVE-2013-0169?

To fix CVE-2013-0169, update to the recommended versions of affected software such as OpenJDK or OpenSSL as specified in the remediation guidelines.

3

Which software is affected by CVE-2013-0169?

CVE-2013-0169 affects various versions of OpenJDK and OpenSSL configured with CBC-mode encryption.

4

What types of attacks can exploit CVE-2013-0169?

CVE-2013-0169 can be exploited in Man-in-the-Middle attacks targeting insecure TLS/DTLS connections.

5

How was CVE-2013-0169 discovered?

CVE-2013-0169 was identified as a flaw in the TLS specification related to CBC-mode encryption.

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.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203