First published: Tue Jun 27 2017(Updated: )
OpenVPN versions before 2.4.3 and before 2.3.17 are vulnerable to denial-of-service and/or possibly sensitive memory leak triggered by man-in-the-middle attacker.
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2017-7520 has a severity rating that is classified as high due to its potential for denial-of-service attacks and sensitive memory leaks.
To mitigate CVE-2017-7520, upgrade OpenVPN to version 2.4.3 or later for stable releases and to version 2.3.17 or later for 2.3.x releases.
Exploitation of CVE-2017-7520 can lead to denial-of-service conditions and could allow attackers to access sensitive data stored in memory.
OpenVPN versions before 2.4.3 and before 2.3.17 are vulnerable according to CVE-2017-7520.
Yes, CVE-2017-7520 can potentially be exploited by a man-in-the-middle attacker, targeting vulnerable OpenVPN versions.