What is the severity of CVE-2017-7522?

CVE-2017-7522 is classified as a denial-of-service vulnerability affecting older versions of OpenVPN.

How do I fix CVE-2017-7522?

To fix CVE-2017-7522, upgrade OpenVPN to version 2.4.3 or later.

Which versions of OpenVPN are affected by CVE-2017-7522?

CVE-2017-7522 affects OpenVPN versions prior to 2.4.3 and 2.3.17.

Can CVE-2017-7522 be exploited remotely?

Yes, CVE-2017-7522 can be exploited by an authenticated remote attacker.

What type of attack is possible with CVE-2017-7522?

CVE-2017-7522 allows for denial-of-service attacks by sending specially crafted certificates.

Vulnerability/
CVE-2017-7522

medium

6.5

CWE

476 20

27/6/2017

7/7/2017

CVE-2017-7522: Null Pointer Dereference

First published: Tue Jun 27 2017(Updated: )

OpenVPN versions before 2.4.3 and before 2.3.17 are vulnerable to denial-of-service by authenticated remote attacker via sending a certificate with an embedded NULL character.

Credit: secalert@redhat.com

Affected Software	Affected Version	How to fix
OpenVPN Monitor	<=2.3.16
OpenVPN Monitor	=2.4.0
OpenVPN Monitor	=2.4.0-alpha2
OpenVPN Monitor	=2.4.0-beta1
OpenVPN Monitor	=2.4.0-beta2
OpenVPN Monitor	=2.4.0-rc1
OpenVPN Monitor	=2.4.0-rc2
OpenVPN Monitor	=2.4.1
OpenVPN Monitor	=2.4.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2017-7522?
CVE-2017-7522 is classified as a denial-of-service vulnerability affecting older versions of OpenVPN.
How do I fix CVE-2017-7522?
To fix CVE-2017-7522, upgrade OpenVPN to version 2.4.3 or later.
Which versions of OpenVPN are affected by CVE-2017-7522?
CVE-2017-7522 affects OpenVPN versions prior to 2.4.3 and 2.3.17.
Can CVE-2017-7522 be exploited remotely?
Yes, CVE-2017-7522 can be exploited by an authenticated remote attacker.
What type of attack is possible with CVE-2017-7522?
CVE-2017-7522 allows for denial-of-service attacks by sending specially crafted certificates.

agent/weakness
agent/type
agent/last-modified-date
agent/first-publish-date
agent/severity
agent/references
agent/author
agent/description
agent/event
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/openvpn
canonical/openvpn monitor
version/openvpn monitor/2.3.16
version/openvpn monitor/2.4.0
version/openvpn monitor/2.4.0-alpha2
version/openvpn monitor/2.4.0-beta1
version/openvpn monitor/2.4.0-beta2
version/openvpn monitor/2.4.0-rc1
version/openvpn monitor/2.4.0-rc2
version/openvpn monitor/2.4.1
version/openvpn monitor/2.4.2

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.

Frequently Asked Questions

What is the severity of CVE-2017-7522?
CVE-2017-7522 is classified as a denial-of-service vulnerability affecting older versions of OpenVPN.
How do I fix CVE-2017-7522?
To fix CVE-2017-7522, upgrade OpenVPN to version 2.4.3 or later.
Which versions of OpenVPN are affected by CVE-2017-7522?
CVE-2017-7522 affects OpenVPN versions prior to 2.4.3 and 2.3.17.
Can CVE-2017-7522 be exploited remotely?
Yes, CVE-2017-7522 can be exploited by an authenticated remote attacker.
What type of attack is possible with CVE-2017-7522?
CVE-2017-7522 allows for denial-of-service attacks by sending specially crafted certificates.