RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1849079 - Follow FIPS policy in regards to DH parameters
Summary: Follow FIPS policy in regards to DH parameters
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: gnutls
Version: ---
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: 8.0
Assignee: Daiki Ueno
QA Contact: Alexander Sosedkin
Mirek Jahoda
URL:
Whiteboard:
Depends On:
Blocks: 1868018
TreeView+ depends on / blocked
 
Reported: 2020-06-19 14:58 UTC by Hubert Kario
Modified: 2020-11-04 01:56 UTC (History)
5 users (show)

Fixed In Version: gnutls-3.6.14-4.el8
Doc Type: Enhancement
Doc Text:
.`gnutls` FIPS DH checks now conform with NIST SP 800-56A rev. 3 This update of the `gnutls` packages provides checks required by NIST Special Publication 800-56A Revision 3, sections 5.7.1.1 and 5.7.1.2, step 2. The change is necessary for future FIPS 140-2 certifications. As a result, `gnutls` now accept only 2048-bit or larger parameters from RFC 7919 and RFC 3526 during the Diffie-Hellman key exchange when operating in FIPS mode.
Clone Of:
: 1868018 (view as bug list)
Environment:
Last Closed: 2020-11-04 01:55:30 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gitlab gnutls gnutls merge_requests 1295 0 None None None 2020-06-26 14:56:06 UTC
Red Hat Bugzilla 1810911 1 None None None 2023-06-26 13:37:43 UTC
Red Hat Product Errata RHBA-2020:4526 0 None None None 2020-11-04 01:55:40 UTC

Description Hubert Kario 2020-06-19 14:58:30 UTC
Description of problem:
New FIPS requirements force the clients to accept DH parameters only if they can verify the order of the key-share. In practice that means the clients can accept only parameters from RFC 3526 or RFC 7919 that are 2048 bits or larger.

Version-Release number of selected component (if applicable):
gnutls-3.6.8-10.el8_2

How reproducible:
always

Steps to Reproduce:
1. set system in FIPS mode
2. connect to server that does not use acceptable parameters

Actual results:
connection is successful

Expected results:
connection should be aborted


Additional info:

Comment 1 Hubert Kario 2020-06-19 14:59:58 UTC
The server shouldn't automatically use parameters outside of those well-known ones.

Comment 14 errata-xmlrpc 2020-11-04 01:55:30 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (gnutls bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:4526


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