CWE
NVD-CWE-Other
Advisory Published
Updated

CVE-2005-2531

First published: Wed Aug 24 2005(Updated: )

OpenVPN before 2.0.1, when running with "verb 0" and without TLS authentication, does not properly flush the OpenSSL error queue when a client fails certificate authentication to the server and causes the error to be processed by the wrong client, which allows remote attackers to cause a denial of service (client disconnection) via a large number of failed authentication attempts.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
OpenVPN Monitor=2.0
OpenVPN Monitor=2.0.1_rc1
OpenVPN Monitor=2.0.1_rc2
OpenVPN Monitor=2.0.1_rc3
OpenVPN Monitor=2.0.1_rc4
OpenVPN Monitor=2.0.1_rc5
OpenVPN Monitor=2.0.1_rc6
OpenVPN Monitor=2.0.1_rc7
OpenVPN Monitor=2.0_beta1
OpenVPN Monitor=2.0_beta2
OpenVPN Monitor=2.0_beta3
OpenVPN Monitor=2.0_beta4
OpenVPN Monitor=2.0_beta5
OpenVPN Monitor=2.0_beta6
OpenVPN Monitor=2.0_beta7
OpenVPN Monitor=2.0_beta8
OpenVPN Monitor=2.0_beta9
OpenVPN Monitor=2.0_beta10
OpenVPN Monitor=2.0_beta11
OpenVPN Monitor=2.0_beta12
OpenVPN Monitor=2.0_beta13
OpenVPN Monitor=2.0_beta15
OpenVPN Monitor=2.0_beta16
OpenVPN Monitor=2.0_beta17
OpenVPN Monitor=2.0_beta18
OpenVPN Monitor=2.0_beta19
OpenVPN Monitor=2.0_beta20
OpenVPN Monitor=2.0_beta28
OpenVPN Monitor=2.0_rc1
OpenVPN Monitor=2.0_rc2
OpenVPN Monitor=2.0_rc3
OpenVPN Monitor=2.0_rc4
OpenVPN Monitor=2.0_rc5
OpenVPN Monitor=2.0_rc6
OpenVPN Monitor=2.0_rc7
OpenVPN Monitor=2.0_rc8
OpenVPN Monitor=2.0_rc9
OpenVPN Monitor=2.0_rc10
OpenVPN Monitor=2.0_rc11
OpenVPN Monitor=2.0_rc12
OpenVPN Monitor=2.0_rc13
OpenVPN Monitor=2.0_rc14
OpenVPN Monitor=2.0_rc15
OpenVPN Monitor=2.0_rc16
OpenVPN Monitor=2.0_rc17
OpenVPN Monitor=2.0_rc18
OpenVPN Monitor=2.0_rc19
OpenVPN Monitor=2.0_rc20
OpenVPN Monitor=2.0_rc21
OpenVPN Monitor=2.0_test1
OpenVPN Monitor=2.0_test2
OpenVPN Monitor=2.0_test3
OpenVPN Monitor=2.0_test5
OpenVPN Monitor=2.0_test6
OpenVPN Monitor=2.0_test7
OpenVPN Monitor=2.0_test8
OpenVPN Monitor=2.0_test9
OpenVPN Monitor=2.0_test10
OpenVPN Monitor=2.0_test11
OpenVPN Monitor=2.0_test12
OpenVPN Monitor=2.0_test14
OpenVPN Monitor=2.0_test15
OpenVPN Monitor=2.0_test16
OpenVPN Monitor=2.0_test17
OpenVPN Monitor=2.0_test18
OpenVPN Monitor=2.0_test19
OpenVPN Monitor=2.0_test20
OpenVPN Monitor=2.0_test21
OpenVPN Monitor=2.0_test22
OpenVPN Monitor=2.0_test23
OpenVPN Monitor=2.0_test24
OpenVPN Monitor=2.0_test26
OpenVPN Monitor=2.0_test27
OpenVPN Monitor=2.0_test29

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.

Frequently Asked Questions

  • What is the severity of CVE-2005-2531?

    The severity of CVE-2005-2531 is considered high due to the potential for denial of service attacks.

  • How do I fix CVE-2005-2531?

    To fix CVE-2005-2531, upgrade OpenVPN to version 2.0.1 or later.

  • What versions are affected by CVE-2005-2531?

    CVE-2005-2531 affects OpenVPN versions 2.0 beta, rc, and test releases up to 2.0.1.

  • What causes the vulnerability in CVE-2005-2531?

    The vulnerability in CVE-2005-2531 is caused by improper flushing of the OpenSSL error queue when client certificate authentication fails.

  • Who can exploit CVE-2005-2531?

    Remote attackers can exploit CVE-2005-2531 to cause denial of service by targeting clients without proper TLS authentication.

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