CVE-2013-2061: Infoleak

Published May 6, 2013
·
Updated

According to the upstream security report [1] the following flaw was found in OpenVPN 2.3.0 and earlier:

OpenVPN 2.3.0 and earlier running in UDP mode are subject to chosen ciphertext injection due to a non-constant-time HMAC comparison function. Plaintext recovery may be possible using a padding oracle attack on the CBC mode cipher implementation of the crypto library, optimistically at a rate of about one character per 3 hours. PolarSSL seems vulnerable to such an attack; the vulnerability of OpenSSL has not been verified or tested.

OpenVPN servers are typically configured to silently drop packets with the wrong HMAC. For this reason measuring the processing time of the packets is not trivial without a MITM position. In practice, the attack likely needs some target-specific information to be effective.

The severity of this vulnerability can be considered low. Only if OpenVPN is configured to use a null-cipher, arbitrary plain-text can be injected which can completely open up this attack vector.

A fix has been committed to git [2]; this is corrected in OpenVPN 2.3.1 and later.

[1] https://community.openvpn.net/openvpn/wiki/SecurityAnnouncement-f375aa67cc [2] https://github.com/OpenVPN/openvpn/commit/11d21349a4e7e38a025849479b36ace7c2eec2ee

Other sources

The openvpndecrypt function in crypto.c in OpenVPN 2.3.0 and earlier, when running in UDP mode, allows remote attackers to obtain sensitive information via a timing attack involving an HMAC comparison function that does not run in constant time and a padding oracle attack on the CBC mode cipher.

MITRE

Affected Software

17 affected componentsFixes available
redhat/openvpn<2.3.1
2.3.1
OpenVPN OpenVPN<=2.3.0
OpenVPN OpenVPN=1.2.0
OpenVPN OpenVPN=1.2.1
OpenVPN OpenVPN=1.3.0
OpenVPN OpenVPN=1.3.1
OpenVPN OpenVPN=1.3.2
OpenVPN OpenVPN=1.4.0
OpenVPN OpenVPN=1.4.1
OpenVPN OpenVPN=1.4.2
OpenVPN OpenVPN=1.4.3
OpenVPN OpenVPN=1.5.0
OpenVPN OpenVPN=1.6.0
OpenVPN OpenVPN=2.1.0
OpenVPN OpenVPN=2.2.0
OpenVPN OpenVPN Access Server=2.0.0
openSUSE openSUSE=11.4

Event History

Nov 15, 2013
CVE Published
via MITRE·06:16 PM
Data Sourced
via MITRE·06:16 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-2061?

CVE-2013-2061 is classified as a high severity vulnerability due to its potential for chosen ciphertext attack.

2

How do I fix CVE-2013-2061?

To fix CVE-2013-2061, upgrade to OpenVPN version 2.3.1 or later.

3

What versions of OpenVPN are affected by CVE-2013-2061?

CVE-2013-2061 affects OpenVPN versions 2.3.0 and earlier.

4

What type of attack does CVE-2013-2061 enable?

CVE-2013-2061 enables chosen ciphertext injection attacks in OpenVPN running in UDP mode.

5

Is OpenVPN running in TCP mode vulnerable to CVE-2013-2061?

No, OpenVPN running in TCP mode is not affected by CVE-2013-2061.

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