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 2083581 - capinfos aborts in FIPS
Summary: capinfos aborts in FIPS
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: wireshark
Version: 9.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Michal Ruprich
QA Contact: František Hrdina
URL:
Whiteboard:
Depends On:
Blocks: 2227004
TreeView+ depends on / blocked
 
Reported: 2022-05-10 12:05 UTC by Ondrej Moriš
Modified: 2023-09-25 14:09 UTC (History)
1 user (show)

Fixed In Version: wireshark-3.4.10-4.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2227004 (view as bug list)
Environment:
Last Closed: 2023-05-09 07:52:12 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Testing pcap (44.39 KB, application/vnd.tcpdump.pcap)
2022-05-10 12:05 UTC, Ondrej Moriš 		no flags Details
Patch (1.90 KB, patch)
2022-07-22 12:23 UTC, Michal Ruprich 		no flags Details | Diff
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-121562 0 None None None 2022-05-10 12:18:03 UTC
Red Hat Product Errata RHSA-2023:2373 0 None None None 2023-05-09 07:52:14 UTC

Description Ondrej Moriš 2022-05-10 12:05:23 UTC 
Created attachment 1878294 [details]
Testing pcap

Description of problem:

When capinfos is used in FIPS mode, it aborts.

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

wireshark-3.4.10-1.el9

How reproducible:

100% in FIPS

Steps to Reproduce:

1. Enable FIPS mode.
   # fips-mode-setup --enable && reboot

2. Use capinfos on attached pcap file:
   # capinfos ./testsetpackets.pcap ./testsetpackets.pcap

Actual results:

fatal error in libgcrypt, file misc.c, line 92, function _gcry_fatal_error: requested algo not in md context

Fatal error: requested algo not in md context
Aborted (core dumped)
Comment 1 Michal Ruprich 2022-07-22 12:23:23 UTC 
Created attachment 1898725 [details]
Patch
Comment 10 Ondrej Moriš 2023-03-28 14:49:08 UTC 
Folks, I still see the aborts in RHEL-9.2.0-20230327.16:

# rpm -q wireshark
wireshark-3.4.10-4.el9.x86_64

# fips-mode-setup --check
FIPS mode is enabled.

#  tshark -nVxr segfault-pcap/fuzz-2010-05-02-27948.pcap >/dev/null
Running as user "root" and group "root". This could be dangerous.

(process:69782): packet-wireguard-WARNING **: 10:45:16.996: proto_register_wg: decryption will not be possible due to lack of algorithms support
Ohhhh jeeee: gcry_md_open failed for algo 301: Invalid digest algorithmfatal error in libgcrypt, file misc.c, line 146, function _gcry_logv: internal error (fatal or bug)
Aborted (core dumped)

# tshark -nVxr sample_captures/Obsolete_Packets.cap >/dev/null
Running as user "root" and group "root". This could be dangerous.

(process:69798): packet-wireguard-WARNING **: 10:45:43.863: proto_register_wg: decryption will not be possible due to lack of algorithms support
Ohhhh jeeee: gcry_md_open failed for algo 301: Invalid digest algorithmfatal error in libgcrypt, file misc.c, line 146, function _gcry_logv: internal error (fatal or bug)
Aborted (core dumped)

# tshark -nVxr sample_captures/smbtorture.cap.gz >/dev/null
Running as user "root" and group "root". This could be dangerous.

(process:69806): packet-wireguard-WARNING **: 10:46:04.948: proto_register_wg: decryption will not be possible due to lack of algorithms support
Ohhhh jeeee: gcry_md_open failed for algo 301: Invalid digest algorithmfatal error in libgcrypt, file misc.c, line 146, function _gcry_logv: internal error (fatal or bug)
Aborted (core dumped)

# tshark -nVxr segfault-pcap/fuzz-2010-05-02-27948.pcap >/dev/null
Running as user "root" and group "root". This could be dangerous.

(process:69814): packet-wireguard-WARNING **: 10:46:22.923: proto_register_wg: decryption will not be possible due to lack of algorithms support
Ohhhh jeeee: gcry_md_open failed for algo 301: Invalid digest algorithmfatal error in libgcrypt, file misc.c, line 146, function _gcry_logv: internal error (fatal or bug)
Aborted (core dumped)

Is this wireshark or libgcrypt issue?
Comment 12 errata-xmlrpc 2023-05-09 07:52:12 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 (Moderate: wireshark security and bug fix 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/RHSA-2023:2373
Comment 13 Michal Ruprich 2023-07-31 15:29:27 UTC 
After looking at this in a Fedora bug for this, it seems to me that there is not much to do with the last core dump. This one is actually a result of reading a packet capture with crypto that is not permitted by FIPS. Not sure if there is a mechanism to allow this particular case in RHEL?
Comment 14 Ondrej Moriš 2023-09-25 14:09:39 UTC 
The question is if segfault is the correct behavior in this case, is it? Shouldn't it fail gracefully when it cannot use FIPS-forbidden crypto?
Note You need to log in before you can comment on or make changes to this bug.