Red Hat Bugzilla – Bug 1341167
lastlog segfaults when last login timestamp contains very large number
Last modified: 2016-11-03 23:41:47 EDT
+++ This bug was initially created as a clone of Bug #1313537 +++ shadow-utils-4.1.5.1-20.el7.s390x used 1F54D654574D56C3 as a timestamp, lastlog segfaults. # lastlog Username Port From Latest root pts/0 ovpn-204-98.brq. Út kvě 31 05:06:36 -0400 2016 bin **Never logged in** daemon **Never logged in** adm **Never logged in** lp **Never logged in** sync **Never logged in** shutdown **Never logged in** halt **Never logged in** mail **Never logged in** operator **Never logged in** games **Never logged in** ftp **Never logged in** nobody **Never logged in** systemd-bus-proxy **Never logged in** systemd-network **Never logged in** dbus **Never logged in** polkitd **Never logged in** tss **Never logged in** sshd **Never logged in** postfix **Never logged in** chrony **Never logged in** Segmentation fault (core dumped)
It looks like lastlog segfault also in case the ll_time is zero.
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, 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://rhn.redhat.com/errata/RHBA-2016-2322.html