ID CVE-2014-2338
Summary IKEv2 in strongSwan 4.0.7 before 5.1.3 allows remote attackers to bypass authentication by rekeying an IKE_SA during (1) initiation or (2) re-authentication, which triggers the IKE_SA state to be set to established.
References
Vulnerable Configurations
  • StrongSwan strongSwan 5.1.2
    cpe:2.3:a:strongswan:strongswan:5.1.2
  • StrongSwan strongSwan 5.1.1
    cpe:2.3:a:strongswan:strongswan:5.1.1
  • StrongSwan strongSwan 5.1.0
    cpe:2.3:a:strongswan:strongswan:5.1.0
  • StrongSwan 5.0.0
    cpe:2.3:a:strongswan:strongswan:5.0.0
  • StrongSwan 5.0.1
    cpe:2.3:a:strongswan:strongswan:5.0.1
  • StrongSwan 5.0.2
    cpe:2.3:a:strongswan:strongswan:5.0.2
  • StrongSwan 5.0.3
    cpe:2.3:a:strongswan:strongswan:5.0.3
  • StrongSwan 5.0.4
    cpe:2.3:a:strongswan:strongswan:5.0.4
  • StrongSwan strongSwan 4.6.0
    cpe:2.3:a:strongswan:strongswan:4.6.0
  • StrongSwan strongSwan 4.6.1
    cpe:2.3:a:strongswan:strongswan:4.6.1
  • StrongSwan strongSwan 4.6.2
    cpe:2.3:a:strongswan:strongswan:4.6.2
  • StrongSwan strongSwan 4.6.3
    cpe:2.3:a:strongswan:strongswan:4.6.3
  • StrongSwan 4.6.4
    cpe:2.3:a:strongswan:strongswan:4.6.4
  • StrongSwan strongSwan 4.5.0
    cpe:2.3:a:strongswan:strongswan:4.5.0
  • StrongSwan strongSwan 4.5.1
    cpe:2.3:a:strongswan:strongswan:4.5.1
  • StrongSwan strongSwan 4.5.2
    cpe:2.3:a:strongswan:strongswan:4.5.2
  • StrongSwan strongSwan 4.5.3
    cpe:2.3:a:strongswan:strongswan:4.5.3
  • StrongSwan 4.4.0
    cpe:2.3:a:strongswan:strongswan:4.4.0
  • StrongSwan strongSwan 4.4.1
    cpe:2.3:a:strongswan:strongswan:4.4.1
  • StrongSwan strongSwan 4.3.0
    cpe:2.3:a:strongswan:strongswan:4.3.0
  • StrongSwan strongSwan 4.3.1
    cpe:2.3:a:strongswan:strongswan:4.3.1
  • StrongSwan strongSwan 4.3.2
    cpe:2.3:a:strongswan:strongswan:4.3.2
  • StrongSwan strongSwan 4.3.3
    cpe:2.3:a:strongswan:strongswan:4.3.3
  • StrongSwan strongSwan 4.3.4
    cpe:2.3:a:strongswan:strongswan:4.3.4
  • StrongSwan 4.3.5
    cpe:2.3:a:strongswan:strongswan:4.3.5
  • StrongSwan 4.3.6
    cpe:2.3:a:strongswan:strongswan:4.3.6
  • StrongSwan 4.3.7
    cpe:2.3:a:strongswan:strongswan:4.3.7
  • StrongSwan strongSwan 4.2.0
    cpe:2.3:a:strongswan:strongswan:4.2.0
  • StrongSwan strongSwan 4.2.1
    cpe:2.3:a:strongswan:strongswan:4.2.1
  • StrongSwan strongSwan 4.2.10
    cpe:2.3:a:strongswan:strongswan:4.2.10
  • StrongSwan strongSwan 4.2.11
    cpe:2.3:a:strongswan:strongswan:4.2.11
  • StrongSwan strongSwan 4.2.12
    cpe:2.3:a:strongswan:strongswan:4.2.12
  • StrongSwan strongSwan 4.2.13
    cpe:2.3:a:strongswan:strongswan:4.2.13
  • StrongSwan strongSwan 4.2.14
    cpe:2.3:a:strongswan:strongswan:4.2.14
  • StrongSwan strongSwan 4.2.15
    cpe:2.3:a:strongswan:strongswan:4.2.15
  • StrongSwan strongSwan 4.2.16
    cpe:2.3:a:strongswan:strongswan:4.2.16
  • StrongSwan strongSwan 4.2.2
    cpe:2.3:a:strongswan:strongswan:4.2.2
  • StrongSwan strongSwan 4.2.3
    cpe:2.3:a:strongswan:strongswan:4.2.3
  • StrongSwan strongSwan 4.2.4
    cpe:2.3:a:strongswan:strongswan:4.2.4
  • StrongSwan strongSwan 4.2.5
    cpe:2.3:a:strongswan:strongswan:4.2.5
  • StrongSwan strongSwan 4.2.6
    cpe:2.3:a:strongswan:strongswan:4.2.6
  • StrongSwan strongSwan 4.2.7
    cpe:2.3:a:strongswan:strongswan:4.2.7
  • StrongSwan strongSwan 4.2.8
    cpe:2.3:a:strongswan:strongswan:4.2.8
  • StrongSwan strongSwan 4.2.9
    cpe:2.3:a:strongswan:strongswan:4.2.9
  • StrongSwan strongSwan 4.1.0
    cpe:2.3:a:strongswan:strongswan:4.1.0
  • StrongSwan strongSwan 4.1.1
    cpe:2.3:a:strongswan:strongswan:4.1.1
  • StrongSwan strongSwan 4.1.10
    cpe:2.3:a:strongswan:strongswan:4.1.10
  • StrongSwan strongSwan 4.1.11
    cpe:2.3:a:strongswan:strongswan:4.1.11
  • StrongSwan strongSwan 4.1.2
    cpe:2.3:a:strongswan:strongswan:4.1.2
  • StrongSwan strongSwan 4.1.3
    cpe:2.3:a:strongswan:strongswan:4.1.3
  • StrongSwan strongSwan 4.1.4
    cpe:2.3:a:strongswan:strongswan:4.1.4
  • StrongSwan strongSwan 4.1.5
    cpe:2.3:a:strongswan:strongswan:4.1.5
  • StrongSwan strongSwan 4.1.6
    cpe:2.3:a:strongswan:strongswan:4.1.6
  • StrongSwan strongSwan 4.1.7
    cpe:2.3:a:strongswan:strongswan:4.1.7
  • StrongSwan strongSwan 4.1.8
    cpe:2.3:a:strongswan:strongswan:4.1.8
  • StrongSwan strongSwan 4.1.9
    cpe:2.3:a:strongswan:strongswan:4.1.9
  • StrongSwan strongSwan 4.0.7
    cpe:2.3:a:strongswan:strongswan:4.0.7
CVSS
Base: 6.4 (as of 17-04-2014 - 10:48)
Impact:
Exploitability:
CWE CWE-287
CAPEC
  • Authentication Abuse
    An attacker obtains unauthorized access to an application, service or device either through knowledge of the inherent weaknesses of an authentication mechanism, or by exploiting a flaw in the authentication scheme's implementation. In such an attack an authentication mechanism is functioning but a carefully controlled sequence of events causes the mechanism to grant access to the attacker. This attack may exploit assumptions made by the target's authentication procedures, such as assumptions regarding trust relationships or assumptions regarding the generation of secret values. This attack differs from Authentication Bypass attacks in that Authentication Abuse allows the attacker to be certified as a valid user through illegitimate means, while Authentication Bypass allows the user to access protected material without ever being certified as an authenticated user. This attack does not rely on prior sessions established by successfully authenticating users, as relied upon for the "Exploitation of Session Variables, Resource IDs and other Trusted Credentials" attack patterns.
  • Exploiting Trust in Client (aka Make the Client Invisible)
    An attack of this type exploits a programs' vulnerabilities in client/server communication channel authentication and data integrity. It leverages the implicit trust a server places in the client, or more importantly, that which the server believes is the client. An attacker executes this type of attack by placing themselves in the communication channel between client and server such that communication directly to the server is possible where the server believes it is communicating only with a valid client. There are numerous variations of this type of attack.
  • Utilizing REST's Trust in the System Resource to Register Man in the Middle
    This attack utilizes a REST(REpresentational State Transfer)-style applications' trust in the system resources and environment to place man in the middle once SSL is terminated. Rest applications premise is that they leverage existing infrastructure to deliver web services functionality. An example of this is a Rest application that uses HTTP Get methods and receives a HTTP response with an XML document. These Rest style web services are deployed on existing infrastructure such as Apache and IIS web servers with no SOAP stack required. Unfortunately from a security standpoint, there frequently is no interoperable identity security mechanism deployed, so Rest developers often fall back to SSL to deliver security. In large data centers, SSL is typically terminated at the edge of the network - at the firewall, load balancer, or router. Once the SSL is terminated the HTTP request is in the clear (unless developers have hashed or encrypted the values, but this is rare). The attacker can utilize a sniffer such as Wireshark to snapshot the credentials, such as username and password that are passed in the clear once SSL is terminated. Once the attacker gathers these credentials, they can submit requests to the web service provider just as authorized user do. There is not typically an authentication on the client side, beyond what is passed in the request itself so once this is compromised, then this is generally sufficient to compromise the service's authentication scheme.
  • Man in the Middle Attack
    This type of attack targets the communication between two components (typically client and server). The attacker places himself in the communication channel between the two components. Whenever one component attempts to communicate with the other (data flow, authentication challenges, etc.), the data first goes to the attacker, who has the opportunity to observe or alter it, and it is then passed on to the other component as if it was never intercepted. This interposition is transparent leaving the two compromised components unaware of the potential corruption or leakage of their communications. The potential for Man-in-the-Middle attacks yields an implicit lack of trust in communication or identify between two components.
Access
VectorComplexityAuthentication
NETWORK LOW NONE
Impact
ConfidentialityIntegrityAvailability
PARTIAL PARTIAL NONE
nessus via4
  • NASL family Debian Local Security Checks
    NASL id DEBIAN_DSA-2903.NASL
    description An authentication bypass vulnerability was found in charon, the daemon handling IKEv2 in strongSwan, an IKE/IPsec suite. The state machine handling the security association (IKE_SA) handled some state transitions incorrectly. An attacker can trigger the vulnerability by rekeying an unestablished IKE_SA during the initiation itself. This will trick the IKE_SA state to'established' without the need to provide any valid credential. Vulnerable setups include those actively initiating IKEv2 IKE_SA (like 'clients' or 'roadwarriors') but also during re-authentication (which can be initiated by the responder). Installations using IKEv1 (pluto daemon in strongSwan 4 and earlier, and IKEv1 code in charon 5.x) is not affected.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 73501
    published 2014-04-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73501
    title Debian DSA-2903-1 : strongswan - security update
  • NASL family SuSE Local Security Checks
    NASL id SUSE_11_STRONGSWAN-140403.NASL
    description The following security issue is fixed by this update : - strongswan has been updated to fix an authentication problem where attackers could have bypassed the IKEv2 authentication. (CVE-2014-2338). (bnc#870572)
    last seen 2019-02-21
    modified 2014-04-21
    plugin id 73555
    published 2014-04-16
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73555
    title SuSE 11.3 Security Update : strongswan (SAT Patch Number 9089)
  • NASL family SuSE Local Security Checks
    NASL id OPENSUSE-2014-384.NASL
    description strongswan was fixed to correct two issues : - Fix for DoS vulnerability by a NULL pointer dereference (CVE-2014-2891). - Fix for a authentication bypass vulnerability in the IKEv2 code (CVE-2014-2338).
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 75367
    published 2014-06-13
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=75367
    title openSUSE Security Update : strongswan (openSUSE-SU-2014:0697-1)
  • NASL family Fedora Local Security Checks
    NASL id FEDORA_2014-5231.NASL
    description This update fixes : - Bug #1081760 - CVE-2014-2338 strongswan: authentication bypass flaw in IKEv2 Note that Tenable Network Security has extracted the preceding description block directly from the Fedora security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.
    last seen 2019-02-21
    modified 2015-10-19
    plugin id 73699
    published 2014-04-25
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73699
    title Fedora 20 : strongswan-5.1.3-1.fc20 (2014-5231)
  • NASL family FreeBSD Local Security Checks
    NASL id FREEBSD_PKG_6FB521B0D38811E3A790000C2980A9F3.NASL
    description strongSwan developers report : Remote attackers are able to bypass authentication by rekeying an IKE_SA during (1) initiation or (2) re-authentication, which triggers the IKE_SA state to be set to established. Only installations that actively initiate or re-authenticate IKEv2 IKE_SAs are affected.
    last seen 2019-02-21
    modified 2018-11-10
    plugin id 73857
    published 2014-05-05
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=73857
    title FreeBSD : strongswan -- Remote Authentication Bypass (6fb521b0-d388-11e3-a790-000c2980a9f3)
  • NASL family Gentoo Local Security Checks
    NASL id GENTOO_GLSA-201412-26.NASL
    description The remote host is affected by the vulnerability described in GLSA-201412-26 (strongSwan: Multiple Vulnerabilities) A NULL pointer dereference and an error in the IKEv2 implementation have been found in strongSwan. Impact : A remote attacker could create a Denial of Service condition or bypass security restrictions. Workaround : There is no known workaround at this time.
    last seen 2019-02-21
    modified 2018-12-05
    plugin id 79979
    published 2014-12-15
    reporter Tenable
    source https://www.tenable.com/plugins/index.php?view=single&id=79979
    title GLSA-201412-26 : strongSwan: Multiple Vulnerabilities
refmap via4
bid 66815
confirm http://www.strongswan.org/blog/2014/04/14/strongswan-authentication-bypass-vulnerability-%28cve-2014-2338%29.html
debian DSA-2903
secunia 57823
suse
  • SUSE-SU-2014:0529
  • openSUSE-SU-2014:0697
  • openSUSE-SU-2014:0700
Last major update 28-11-2016 - 14:10
Published 16-04-2014 - 14:37
Back to Top