Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 137660 - ypserv segfaults when used with -p portnum
ypserv segfaults when used with -p portnum
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: ypserv (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Steve Dickson
Jay Turner
Depends On:
  Show dependency treegraph
Reported: 2004-10-30 03:52 EDT by Ion Badulescu
Modified: 2015-01-07 19:08 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-21 15:23:43 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2004:578 normal SHIPPED_LIVE Updated ypserv package 2004-12-21 00:00:00 EST

  None (edit)
Description Ion Badulescu 2004-10-30 03:52:06 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041003

Description of problem:
One of the changes in ypserv-2.8-iface-binding3.patch contains a

-      c = getopt_long (argc, argv, "vdp:buh", long_options,
+      c = getopt_long (argc, argv, "vdpi:buh", long_options,

Since "p" loses the colon after it, it no longer requires an argument,
so eventually atoi() ends up being called with a NULL argument.

The fix is obvious, is tested, and it solves the problem.

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

How reproducible:

Steps to Reproduce:
1. ypserv -p 920

Actual Results:  # ypserv -p911
Segmentation fault

Additional info:
Comment 1 Chris Feist 2004-11-03 12:04:28 EST
Bug was verified, and has been fixed in ypserv-2.8-11.
Comment 2 John Flanagan 2004-12-21 15:23:43 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


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