First published: Thu May 02 2013(Updated: )
strongSwan 4.3.5 through 5.0.3, when using the OpenSSL plugin for ECDSA signature verification, allows remote attackers to authenticate as other users via an invalid signature.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
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 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of CVE-2013-2944 is classified as high due to the potential for remote authentication bypass.
CVE-2013-2944 affects strongSwan versions 4.3.5 through 5.0.3 when using the OpenSSL plugin for ECDSA signature verification.
To fix CVE-2013-2944, upgrade strongSwan to a version later than 5.0.3 that includes the relevant security patches.
The consequences of CVE-2013-2944 allow remote attackers to authenticate as other users, compromising user accounts.
Yes, CVE-2013-2944 may be exploitable in the wild if the affected versions of strongSwan are deployed without mitigation.