Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1457121 - (CVE-2017-9022) CVE-2017-9022 strongswan: Insufficient validation of RSA public keys passed to the gmp plugin
CVE-2017-9022 strongswan: Insufficient validation of RSA public keys passed t...
Status: CLOSED NOTABUG
Product: Security Response
Classification: Other
Component: vulnerability (Show other bugs)
unspecified
All Linux
medium Severity medium
: ---
: ---
Assigned To: Red Hat Product Security
impact=moderate,public=20170530,repor...
: Security
Depends On: 1457123 1457124
Blocks: 1457125
  Show dependency treegraph
 
Reported: 2017-05-31 03:43 EDT by Andrej Nemec
Modified: 2017-07-05 10:48 EDT (History)
3 users (show)

See Also:
Fixed In Version: strongswan 5.5.3
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2017-07-05 10:48:23 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Andrej Nemec 2017-05-31 03:43:14 EDT
It was found that RSA public keys passed to the gmp plugin aren't validated sufficiently before attempting signature verification, so that invalid input might lead to a floating point exception and crash of the process. A certificate with an appropriately prepared public key sent by a peer could be used for a denial-of-service attack.

External References:

https://www.strongswan.org/blog/2017/05/30/strongswan-vulnerability-(cve-2017-9022).html
Comment 1 Andrej Nemec 2017-05-31 03:45:27 EDT
Created strongswan tracking bugs for this issue:

Affects: epel-all [bug 1457123]
Affects: fedora-all [bug 1457124]
Comment 2 Stefan Cornelius 2017-07-05 10:48:32 EDT
Statement:

This issue did not affect the versions of strongimcv as shipped with Red Hat Enterprise Linux 7, as they did not include support for the gmp plugin.

Note You need to log in before you can comment on or make changes to this bug.