Bug 1326662 - Traceroute segfaults during MTU discovery
Summary: Traceroute segfaults during MTU discovery
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: traceroute
Version: 7.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Jan Synacek
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-13 10:09 UTC by Joshua Lamorie
Modified: 2016-04-13 10:33 UTC (History)
0 users

Fixed In Version: traceroute-2.0.22-1.el7
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-04-13 10:32:47 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
CentOS 10704 0 None None None 2016-04-13 10:09:57 UTC
Launchpad 1330558 0 None None None 2016-04-13 10:10:51 UTC

Description Joshua Lamorie 2016-04-13 10:09:58 UTC 
Description of problem:

When attempting to determine MTU size with traceroute, the application crashes with segmentation fault.

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

Tested on CentOS 7

The version of traceroute:

$ traceroute --version
Modern traceroute for Linux, version 2.0.19, Jun 10 2014
Copyright (c) 2008 Dmitry Butskoy, License: GPL v2 or any later

How reproducible:

Every time.

Steps to Reproduce:
1. Execute 'traceroute --mtu 8.8.8.8'
2. Observe segfault.

Actual results:

$ traceroute --mtu 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 65000 byte packetsSegmentation fault (core dumped)

Expected results:


Additional info:

This issue has been seen in other distros:

* https://bugs.launchpad.net/ubuntu/+source/traceroute/+bug/1330558

This has been partially noted upstream.

* https://sourceforge.net/p/traceroute/bugs/8/

Someone tried to reference a previous traceroute bug related to this:

* https://bugzilla.redhat.com/show_bug.cgi?id=903290
Comment 3 Jan Synacek 2016-04-13 10:33:54 UTC 
The fix is already scheduled for RHEL-7.3.
Note You need to log in before you can comment on or make changes to this bug.