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 1921920 - suds Reader classes break when FIPS is enabled
Summary: suds Reader classes break when FIPS is enabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: python-suds
Version: 8.3
Hardware: All
OS: Linux
high
high
Target Milestone: rc
: 8.4
Assignee: Oyvind Albrigtsen
QA Contact: cluster-qe@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1942384 2059752 2059753
TreeView+ depends on / blocked
 
Reported: 2021-01-28 20:51 UTC by Reid Wahl
Modified: 2024-06-14 00:05 UTC (History)
12 users (show)

Fixed In Version: python-suds-0.7-0.11.94664ddd46a6.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2059752 2059753 (view as bug list)
Environment:
Last Closed: 2022-05-10 14:34:37 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github suds-community suds pull 72 0 None Merged Use usedforsecurity=False for md5() calls to make suds work on FIPS enabled systems 2022-04-13 12:18:38 UTC
Red Hat Knowledge Base (Solution) 5753111 0 None None None 2021-01-29 01:08:51 UTC
Red Hat Product Errata RHBA-2022:1967 0 None None None 2022-05-10 14:34:44 UTC

Internal Links: 2054504

Description Reid Wahl 2021-01-28 20:51:58 UTC
Description of problem:

suds Reader.mangle() invokes hashlib.md5. md5 is not FIPS-compliant and is thus disabled when FIPS is enabled.

As a result, the fence_vmware_soap fence agent for High Availability clusters is broken when FIPS is enabled. This is one of our most commonly used fence agents, and it relies on suds. There is no known workaround, as suds does not allow a client to disable mangling or choose a different mangling method. Further, for many users of fence_vmware_soap, there is no other viable fence agent for their environment.

It is crucial that we get a fix for this. Otherwise, it will render High Availability clustering unusable in many VMware environments where FIPS is enabled on the guest OS.


Below is a fence_vmware_soap demo with FIPS enabled and a traceback.print_exc() call added. These are invalid credentials and address so no need to hide them.

[root@fastvm-rhel-8-0-23 ~]# fence_vmware_soap -v -a 1.2.3.4 -l login -p password --ssl-insecure -n asdf
Traceback (most recent call last):
  File "/usr/sbin/fence_vmware_soap", line 60, in soap_login
    conn = Client(url + "/vimService.wsdl", location=url, transport=RequestsTransport(verify=verify), headers=headers)
  File "/usr/lib/python3.6/site-packages/suds/client.py", line 120, in __init__
    self.wsdl = reader.open(url)
  File "/usr/lib/python3.6/site-packages/suds/reader.py", line 101, in open
    id = self.mangle(url, "wsdl")
  File "/usr/lib/python3.6/site-packages/suds/reader.py", line 61, in mangle
    h = md5(name.encode()).hexdigest()
ValueError: [digital envelope routines: EVP_DigestInit_ex] disabled for FIPS
2021-01-28 11:43:07,219 ERROR: Unable to connect/login to fencing device

-----

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

python3-suds-0.7-0.8.94664ddd46a6.el8.noarch

-----

How reproducible:

Always

-----

Steps to Reproduce:
1. Enable FIPS mode.
2. Open a python3 interpreter and run:

>>> from suds.options import Options
>>> from suds.reader import DefinitionsReader
>>> from suds.wsdl import Definitions
>>> reader = DefinitionsReader(Options(), Definitions)
>>> reader.open('https://www.example.com')

-----

Actual results:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "/usr/lib/python3.6/site-packages/suds/reader.py", line 102, in open
    id = self.mangle(url, "wsdl")
  File "/usr/lib/python3.6/site-packages/suds/reader.py", line 61, in mangle
    h = md5(name.encode()).hexdigest()
ValueError: [digital envelope routines: EVP_DigestInit_ex] disabled for FIPS

-----

Expected results:

No "disabled for FIPS" exception. There will be a different exception if you use incorrect options like I did, or it should succeed if you use valid options.

Comment 1 Reid Wahl 2021-01-28 20:54:08 UTC
Another hashing method like sha256 should be fine if we really have to use hashlib for this.

Comment 2 Reid Wahl 2021-01-28 21:05:09 UTC
Fortunately this is not reproducible in RHEL 7. Back then, mangle used the built-in hash function.

        h = abs(hash(name))

Comment 4 Mike Murphy 2021-02-05 22:02:57 UTC
Has this been tested on RHEL 8.3?

Comment 5 Reid Wahl 2021-02-05 22:06:08 UTC
(In reply to Mike Murphy from comment #4)
> Has this been tested on RHEL 8.3?

Yes

Comment 6 Rehana 2022-02-08 15:05:21 UTC
Hi Jeff Ortel, 

We have a new customer case reported against virt-who Bug 2051883 which is caused by this bug. Curious to know if the  python3-suds team plan to fix this issue in the near future? 

thanks,
Rehana

Comment 9 Oyvind Albrigtsen 2022-02-28 10:27:44 UTC
https://github.com/suds-community/suds/pull/72

Comment 20 errata-xmlrpc 2022-05-10 14:34:37 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 (python-suds 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-2022:1967


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