2.6
CWE
200
Advisory Published
Updated

CVE-2015-4171: Infoleak

First published: Wed Jun 10 2015(Updated: )

strongSwan 4.3.0 through 5.x before 5.3.2 and strongSwan VPN Client before 1.4.6, when using EAP or pre-shared keys for authenticating an IKEv2 connection, does not enforce server authentication restrictions until the entire authentication process is complete, which allows remote servers to obtain credentials by using a valid certificate and then reading the responses.

Credit: cve@mitre.org

Affected SoftwareAffected VersionHow to fix
strongSwan VPN Client for Android<=1.4.5
Ubuntu=14.04
Ubuntu=14.10
Ubuntu=15.04
Debian Linux=8.0
strongSwan=4.3.0
strongSwan=4.3.1
strongSwan=4.3.2
strongSwan=4.3.3
strongSwan=4.3.4
strongSwan=4.3.5
strongSwan=4.3.6
strongSwan=4.3.7
strongSwan=4.4.0
strongSwan=4.4.1
strongSwan=4.5.0
strongSwan=4.5.1
strongSwan=4.5.2
strongSwan=4.5.3
strongSwan=4.6.0
strongSwan=4.6.1
strongSwan=4.6.2
strongSwan=4.6.3
strongSwan=4.6.4
strongSwan=5.0.0
strongSwan=5.0.1
strongSwan=5.0.2
strongSwan=5.0.3
strongSwan=5.0.4
strongSwan=5.1.0
strongSwan=5.1.1
strongSwan=5.1.2
strongSwan=5.1.3
strongSwan=5.2.0
strongSwan=5.2.1
strongSwan=5.2.2
strongSwan=5.2.3
strongSwan=5.3.0
strongSwan=5.3.1

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-2015-4171?

    CVE-2015-4171 has a medium severity rating due to its potential to allow remote servers to bypass authentication restrictions.

  • How do I fix CVE-2015-4171?

    To fix CVE-2015-4171, update to strongSwan versions 5.3.2 or later and strongSwan VPN Client 1.4.6 or later.

  • Which versions are affected by CVE-2015-4171?

    CVE-2015-4171 affects strongSwan versions 4.3.0 to 5.x before 5.3.2 and strongSwan VPN Client versions before 1.4.6.

  • What is the primary impact of CVE-2015-4171?

    The primary impact of CVE-2015-4171 is the inability to enforce server authentication restrictions during the IKEv2 authentication process.

  • Is CVE-2015-4171 exploitable in all configurations?

    CVE-2015-4171 is specifically exploitable when using EAP or pre-shared keys for IKEv2 connection 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