Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Description of problem:
The issue was found on a RHEL 7 derivative. It was also reported to the-tcpdump-group/libpcap and CentOS community
- https://github.com/the-tcpdump-group/libpcap/issues/1071
- https://bugs.centos.org/view.php?id=18365
Quote:
To summarize, pcap file written with `tcpdump -i any -w a.pcap` will be rejected by tcpdump 4.99 which adds sanity checks on pkthdr struct.
The other issue as analyzed there by @guyharris is that when inspecting the bad pcap file with tcpdump 4.9, it may access 16 bytes of data out of bounds. See https://github.com/the-tcpdump-group/libpcap/issues/1071#issuecomment-980442403
Version-Release number of selected component (if applicable):
libpcap-1.5.3-12.1.al7.src.rpm
How reproducible:
Always
Steps to Reproduce:
Run the following commands to dump a few packets
tcpdump -i any -w a.pcap -c 8
Hexdump check on first few bytes of the file. snaplen is 16 bytes bigger than actual len field for each packet header
00000000 d4 c3 b2 a1 02 00 04 00 00 00 00 00 00 00 00 00 |................|
00000010 00 00 04 00 71 00 00 00 cb 5e 9f 61 ae 80 04 00 |....q....^.a....|
00000020 c9 03 00 00 b9 03 00 00 00 00 00 01 00 06 ee ff |................|
^^ ^^
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 (libpcap 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:1201