Bug 31358 - libpcap bugfix release 1.10.2 and tcpdump bugfix release 4.99.2
Summary: libpcap bugfix release 1.10.2 and tcpdump bugfix release 4.99.2
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL:
Whiteboard: MGA8-64-OK
Keywords: advisory, validated_update
Depends on:
Blocks:
 
Reported: 2023-01-03 19:13 CET by David Walser
Modified: 2023-01-24 09:00 CET (History)
5 users (show)

See Also:
Source RPM: libpcap-1.10.0-1.mga8.src.rpm, tcpdump-4.99.0-1.mga8.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2023-01-03 19:13:18 CET
New versions of libpcap and tcpdump have been released on December 31:
https://git.tcpdump.org/libpcap/blob/HEAD:/CHANGES
https://git.tcpdump.org/tcpdump/blob/HEAD:/CHANGES

Overflow and crash fixes in the libpcap update could also be considered security issues, so we should go ahead and update these for Mageia 8 (already updated in Cauldron).
Comment 1 Lewis Smith 2023-01-03 21:47:09 CET
Neither SRPM involved has a visible packager, so assigning this globally.

Assignee: bugsquad => pkg-bugs

Comment 2 Nicolas Salguero 2023-01-06 11:07:15 CET
Suggested advisory:
========================

The updated packages fix several issues including some overflows and crashes.

References:
https://git.tcpdump.org/libpcap/blob/HEAD:/CHANGES
https://git.tcpdump.org/tcpdump/blob/HEAD:/CHANGES
========================

Updated packages in core/updates_testing:
========================
libpcap-doc-1.10.2-1.mga8
lib(64)pcap1-1.10.2-1.mga8
lib(64)pcap-devel-1.10.2-1.mga8
tcpdump-4.99.2-1.mga8

from SRPMS:
libpcap-1.10.2-1.mga8.src.rpm
tcpdump-4.99.2-1.mga8.src.rpm

CC: (none) => nicolas.salguero
Status: NEW => ASSIGNED
Assignee: pkg-bugs => qa-bugs

Comment 3 Herman Viaene 2023-01-19 16:52:22 CET
MGA8-64 MATE on Acer Aspire 5253
No installation issues
Exercising the command
# tcpdump -i wlp7s0 -nn -s0 -v
tcpdump: listening on wlp7s0, link-type EN10MB (Ethernet), snapshot length 262144 bytes
16:48:17.379840 IP (tos 0x0, ttl 64, id 42698, offset 0, flags [DF], proto TCP (6), length 184)
    192.168.2.7.895 > 192.168.2.1.2049: Flags [P.], cksum 0x9d29 (correct), seq 4167477446:4167477578, ack 2414818600, win 7100, options [nop,nop,TS val 1465068231 ecr 2612597886], length 132: NFS request xid 733274798 128 getattr fh 0,2/53
16:48:17.381862 IP (tos 0x0, ttl 63, id 11840, offset 0, flags [DF], proto TCP (6), length 136)
    192.168.2.1.2049 > 192.168.2.7.895: Flags [P.], cksum 0x1567 (correct), seq 1:85, ack 132, win 9798, options [nop,nop,TS val 2612599168 ecr 1465068231], length 84: NFS reply xid 733274798 reply ok 80 getattr NON 1 ids 0/-688666525 sz 3996184949
16:48:17.382040 IP (tos 0x0, ttl 64, id 42699, offset 0, flags [DF], proto TCP (6), length 52)
    192.168.2.7.895 > 192.168.2.1.2049: Flags [.], cksum 0x2bb5 (correct), ack 85, win 7100, options [nop,nop,TS val 1465068233 ecr 2612599168], length 0
16:48:18.182845 34:31:c4:80:a9:b4 > ff:ff:ff:ff:ff:ff, ethertype Unknown (0x88e1), length 60: 
	0x0000:  0000 a000 b052 a07f a47f 0000 0000 0000  .....R..........
	0x0010:  0000 0000 0000 0000 0000 0000 0000 0000  ................
	0x0020:  0000 0000 0000 0000 0000 0000 0000       ..............
etc .....
And when I stop the command with Ctrl-C I get at the end
^C
21 packets captured
21 packets received by filter
0 packets dropped by kernel
Looks good enough to me.

CC: (none) => herman.viaene
Whiteboard: (none) => MGA8-64-OK

Comment 4 Thomas Andrews 2023-01-19 22:12:24 CET
Validating. Advisory in comment 2.

CC: (none) => andrewsfarm, sysadmin-bugs
Keywords: (none) => validated_update

Dave Hodgins 2023-01-24 02:24:48 CET

CC: (none) => davidwhodgins
Keywords: (none) => advisory

Comment 5 Mageia Robot 2023-01-24 09:00:05 CET
An update for this issue has been pushed to the Mageia Updates repository.

https://advisories.mageia.org/MGAA-2023-0007.html

Resolution: (none) => FIXED
Status: ASSIGNED => RESOLVED


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