CVE-2014-9221

These are all security issues fixed in the strongswan-5.3.5-1.1 package on the GA media of openSUSE Tumbleweed.

This strongswan update fixes the following security and non security issues.

• Disallow brainpool elliptic curve groups in fips mode (bnc#856322).
• Applied an upstream fix for a denial-of-service vulnerability, which can be triggered by an IKEv2 Key Exchange payload, that contains the Diffie-Hellman group 1025 (bsc#910491,CVE-2014-9221).
• Adjusted whilelist of approved algorithms in fips mode (bsc#856322).
• Updated strongswan-hmac package description (bsc#856322).
• Disabled explicit gpg validation; osc source_validator does it.
• Guarded fipscheck and hmac package in the spec file for >13.1.
• Added generation of fips hmac hash files using fipshmac utility and a _fipscheck script to verify binaries/libraries/plugings shipped in the strongswan-hmac package. With enabled fips in the kernel, the ipsec script will call it before any action or in a enforced/manual 'ipsec _fipscheck' call. Added config file to load openssl and kernel af-alg plugins, but not all the other modules which provide further/alternative algs. Applied a filter disallowing non-approved algorithms in fips mode. (fate#316931,bnc#856322).
• Fixed file list in the optional (disabled) strongswan-test package.
• Fixed build of the strongswan built-in integrity checksum library and enabled building it only on architectures tested to work.
• Fix to use bug number 897048 instead 856322 in last changes entry.
• Applied an upstream patch reverting to store algorithms in the registration order again as ordering them by identifier caused weaker algorithms to be proposed first by default (bsc#897512).

strongSwan 4.5.x through 5.2.x before 5.2.1 allows remote attackers to cause a denial of service (invalid pointer dereference) via a crafted IKEv2 Key Exchange (KE) message with Diffie-Hellman (DH) group 1025.

Mike Daskalakis discovered that strongSwan incorrectly handled IKEv2 payloads that contained the Diffie-Hellman group 1025. A remote attacker could use this issue to cause the IKE daemon to crash, resulting in a denial of service.