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 1878151 - 1536bit group from RFC3526 is allowed in FIPS mode when in policy DH-MIN is set to be lower than 1536
Summary: 1536bit group from RFC3526 is allowed in FIPS mode when in policy DH-MIN is s...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: nss
Version: 8.4
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: 8.0
Assignee: Bob Relyea
QA Contact: Ivan Nikolchev
URL:
Whiteboard:
Depends On:
Blocks: 1896432
TreeView+ depends on / blocked
 
Reported: 2020-09-11 13:30 UTC by Ivan Nikolchev
Modified: 2021-06-15 15:12 UTC (History)
2 users (show)

Fixed In Version: nss-3.53.1-12.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 1896432 (view as bug list)
Environment:
Last Closed: 2021-05-26 15:13:01 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Ivan Nikolchev 2020-09-11 13:30:10 UTC
Description of problem:
1536bit group from RFC3526 is not allowed in FIPS mode according to 'SP800-56A rev 3'

NSS should not allow this group regardless of what DH-MIN is set in the policy.

Version-Release number of selected component (if applicable):

nss-3.53.1-11

How reproducible:
Always

Steps to Reproduce:
We have reproducer in /CoreOS/nss/Sanity/Well-known-DH-parameters

1. Run the test on rhel8 machine in fips mode, but before executing the test change DH-MIN to be lower than 1536 in the policy.


Actual results:
'Testing rfc3526-group-5-1536.pem' fails because the DH group is allowed and the connection is successful.


Expected results:
2. The DH group is not allowed and NSS aborts the connection.


Additional info:

Comment 5 Bob Relyea 2020-11-10 00:11:48 UTC
We need zstream+ for this bug, thanks.

Comment 8 CongLi 2021-05-26 06:12:44 UTC
Hi,

Since the issue described in this bug should be resolved (VERIFIED), could you please close this bug with resolution 'CURRENTRELEASE' if this bug got fixed ?

If the fix for this is not released yet, check if this will ever get fixed. In case of a negative answer then please change it as WONTFIX.

If there's anything else to be done on this BZ, if it's still active, not released yet and we actually intend to release it, then please ignore my message.

Please note: for those bugs which are not included in errata, please add 'TestOnly' keyword, and those bugs with 'TestOnly' keyword will be closed automatically after GA.
TestOnly: Use this when there is no code delivery involved, or for use when code is already upstream and will be incorporated automatically to the next release for testing purposes only.

Thank you.


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