#12647: sudo-1.8.28 (CVE-2019-14287)
-------------------------+-----------------------
Reporter: renodr | Owner: renodr
Type: enhancement | Status: assigned
Priority: high | Milestone: 9.1
Component: BOOK | Version: SVN
Severity: normal | Resolution:
Keywords: |
-------------------------+-----------------------
Comment (by renodr):
{{{
Major changes between version 1.8.28 and 1.8.27:
Sudo will now only set PAM_TTY to the empty string when no terminal is
present on Solaris and Linux. This workaround is only needed on those
systems which may have PAM modules that misbehave when PAM_TTY is not set.
The mailerflags sudoers option now has a default value even if
sendmail support was disabled at configure time. Fixes a crash when the
mailerpath sudoers option is set but mailerflags is not. Bug #878.
Sudo will now filter out last login messages on HP-UX unless it a
shell is being run via sudo -s or sudo -i. Otherwise, when trusted mode is
enabled, these messages will be displayed for each command.
On AIX, when the user's password has expired and PAM is not in use,
sudo will now allow the user to change their password. Bug #883.
Sudo has a new -B command line option that will ring the terminal bell
when prompting for a password.
Sudo no longer refuses to prompt for a password when it cannot
determine the user's terminal as long as it can open /dev/tty. This allows
sudo to function on systems where /proc is unavailable, such as when
running in a chroot environment.
The env_editor sudoers flag is now on by default. This makes source
builds more consistent with the packages generated by sudo's mkpkg script.
Sudo no longer ships with pre-formatted copies of the manual pages.
These were included for systems like IRIX that don't ship with an nroff
utility. There are now multiple Open Source nroff replacements so this
should no longer be an issue.
Fixed a bad interaction with configure's --prefix and --disable-shared
options. Bug #886.
More verbose error message when a password is required and no terminal
is present. Bug #828.
Command tags, such as NOPASSWD, are honored when a user tries to run a
command that is allowed by sudoers but which does not actually exist on
the file system. Bug #888.
Asturian translation for sudoers from translationproject.org.
I/O log timing files now store signal suspend and resume information
in the form of a signal name instead of a number.
Fixed a bug introduced in 1.8.24 that prevented sudo from honoring the
value of ipa_hostname from sssd.conf, if specified, when matching the host
name.
Fixed a bug introduced in 1.8.21 that prevented the core dump resource
limit set in the pam_limits module from taking effect. Bug #894.
Fixed parsing of double-quoted Defaults group and netgroup bindings.
The user ID is now used when matching sudoUser attributes in LDAP.
Previously, the user name, group name and group IDs were used when
matching but not the user ID.
Sudo now writes PAM messages to the user's terminal, if available,
instead of the standard output or standard error. This prevents PAM output
from being intermixed with that of the command when output is sent to a
file or pipe. Bug #895.
Sudoedit now honors the umask and umask_override settings in sudoers.
Previously, the user's umask was used as-is.
Fixed a bug where the terminal's file context was not restored when
using SELinux RBAC. Bug #898.
Fixed a security issue where a sudo user may be able to run a command
as root when the Runas specification explicitly disallows root access as
long as the ALL keyword is listed first. This vulnerability has been
assigned CVE-2019-14287
}}}
--
Ticket URL: <http://wiki.linuxfromscratch.org/blfs/ticket/12647#comment:2>
BLFS Trac <http://wiki.linuxfromscratch.org/blfs>
Beyond Linux From Scratch
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
