CVE-2013-2944: Medium severity strongSwan Strongswan vulnerability

Published May 2, 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.

Affected Software

17 affected components

strongSwan Strongswan=4.3.5

strongSwan Strongswan=4.3.6

strongSwan Strongswan=4.3.7

strongSwan Strongswan=4.4.0

strongSwan Strongswan=4.4.1

strongSwan Strongswan=4.5.0

strongSwan Strongswan=4.5.1

strongSwan Strongswan=4.5.2

strongSwan Strongswan=4.5.3

strongSwan Strongswan=4.6.0

strongSwan Strongswan=4.6.1

strongSwan Strongswan=4.6.2

strongSwan Strongswan=4.6.3

strongSwan Strongswan=4.6.4

strongSwan Strongswan=5.0.0

strongSwan Strongswan=5.0.1

strongSwan Strongswan=5.0.2

Remediation

Patch Available

http://download.strongswan.org/patches/10_openssl_ecdsa_signature_patch/strongswan-4.3.5-5.0.3_openssl_ecdsa_signature.patch

Event History

May 2, 2013

CVE Published

via MITRE·02:00 PM

Data Sourced

via MITRE·02:00 PM

Description

Frequently Asked Questions

What is the severity of CVE-2013-2944?

The severity of CVE-2013-2944 is classified as high due to the potential for remote authentication bypass.

Who is affected by CVE-2013-2944?

CVE-2013-2944 affects strongSwan versions 4.3.5 through 5.0.3 when using the OpenSSL plugin for ECDSA signature verification.

How do I fix CVE-2013-2944?

To fix CVE-2013-2944, upgrade strongSwan to a version later than 5.0.3 that includes the relevant security patches.

What are the consequences of CVE-2013-2944?

The consequences of CVE-2013-2944 allow remote attackers to authenticate as other users, compromising user accounts.

Is CVE-2013-2944 exploitable in the wild?

Yes, CVE-2013-2944 may be exploitable in the wild if the affected versions of strongSwan are deployed without mitigation.