Improper Verification of Cryptographic Signature Affecting strongswan package, versions <5.6.0-4.3.2


Severity

Recommended
0.0
medium
0
10

Based on SUSE Linux Enterprise Server security rating.

Threat Intelligence

EPSS
1.24% (78th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-SLES151-STRONGSWAN-2723659
  • published14 Apr 2022
  • disclosed25 Nov 2019

Introduced: 25 Nov 2019

CVE-2018-16151  (opens in a new tab)
CWE-347  (opens in a new tab)

How to fix?

Upgrade SLES:15.1 strongswan to version 5.6.0-4.3.2 or higher.

NVD Description

Note: Versions mentioned in the description apply only to the upstream strongswan package and not the strongswan package as distributed by SLES. See How to fix? for SLES:15.1 relevant fixed versions and status.

In verify_emsa_pkcs1_signature() in gmp_rsa_public_key.c in the gmp plugin in strongSwan 4.x and 5.x before 5.7.0, the RSA implementation based on GMP does not reject excess data after the encoded algorithm OID during PKCS#1 v1.5 signature verification. Similar to the flaw in the same version of strongSwan regarding digestAlgorithm.parameters, a remote attacker can forge signatures when small public exponents are being used, which could lead to impersonation when only an RSA signature is used for IKEv2 authentication.