A flaw was found in tcpdump's TCP printer. A remote attacker could use this flaw to cause tcpdump to crash, resulting in a denial of service, or possibly execute arbitrary code. Upstream patch: http://www.ca.tcpdump.org/cve/0002-test-case-files-for-CVE-2015-2153-2154-2155.patch
Created tcpdump tracking bugs for this issue: Affects: fedora-all [bug 1201799]
The problem here is a simple missing length check in the rpki_rtr_pdu_print() function in print-rpki-rtr.c when processing RPKI-RTR PDUs (Protocol Data Units) with an incorrect header length. Without this check, the function will try to operate on invalid data when processing certain packets, leading to all kinds of unwanted side effects, including crashes due to invalid reads, writes and general memory corruption. Due to the memory corruption aspect I'm simply assuming that code execution may be a possibility (I've not performed an in-depth enough analysis to see if this assumption is really correct).
tcpdump-4.7.3-1.fc21 has been pushed to the Fedora 21 stable repository. If problems still persist, please make note of it in this bug report.
tcpdump-4.7.3-1.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
tcpdump-4.5.1-4.fc20 has been pushed to the Fedora 20 stable repository. If problems still persist, please make note of it in this bug report.
This issue has been addressed in the following products: Red Hat Enterprise Linux 7 Via RHSA-2017:1871 https://access.redhat.com/errata/RHSA-2017:1871