sudo 1.8.32 (legacy) released
"Todd C. Miller" <[email protected]> Tue, 09 Feb 2021 16:02:52 -0700
| Newsgroups | gmane.comp.tools.sudo.announce |
|---|---|
| Message-ID | <[email protected]> |
--===============7957592352175647864==
Content-Type: multipart/signed; protocol="application/pgp-signature";
micalg=pgp-; boundary="85854_Tue_Feb__9_16_02_43_MST_2021"
--85854_Tue_Feb__9_16_02_43_MST_2021
Content-Type: text/plain; charset=us-ascii
Sudo 1.8.32 is now available. This is a legacy version of sudo
that contains security fixes for CVE-2021-23239, CVE-2021-23240 and
CVE-2021-3156, backported from the sudo 1.9 branch.
Source:
https://www.sudo.ws/dist/sudo-1.8.32.tar.gz
ftp://ftp.sudo.ws/pub/sudo/sudo-1.8.32.tar.gz
SHA256 checksum:
5ce3c18c5efbecd5437a0945f314f1822423eaf9a2d7eb7ecf80857bc32246c5
MD5 checksum:
a7318202ba391079a0e32933f0fb8bd6
Binary packages:
https://github.com/sudo-project/sudo/releases/tag/SUDO_1_8_32
For a list of download mirror sites, see:
https://www.sudo.ws/download_mirrors.html
Sudo web site:
https://www.sudo.ws/
Sudo web site mirrors:
https://www.sudo.ws/mirrors.html
Major changes between sudo 1.8.32 and 1.8.31p2
* Fixed a regression introduced in sudo 1.8.9 where the "closefrom"
sudoers option could not be set to a value of 3. Bug #950.
* Fixed a regression introduced in sudo 1.8.24 in the LDAP back-end
where sudoNotBefore and sudoNotAfter were applied even when the
SUDOERS_TIMED setting was not present in ldap.conf. Bug #945.
* Fixed a buffer size mismatch when serializing the list of IP
addresses for configured network interfaces. This bug is not
actually exploitable since the allocated buffer is large enough
to hold the list of addresses.
* If sudo is executed with a name other than "sudo" or "sudoedit",
it will now fall back to "sudo" as the program name. This affects
warning, help and usage messages as well as the matching of Debug
lines in the /etc/sudo.conf file. Previously, it was possible
for the invoking user to manipulate the program name by setting
argv[0] to an arbitrary value when executing sudo.
* Sudo now checks for failure when setting the close-on-exec flag
on open file descriptors. This should never fail but, if it
were to, there is the possibility of a file descriptor leak to
a child process (such as the command sudo runs).
* Fixed CVE-2021-23239, a potential information leak in sudoedit
that could be used to test for the existence of directories not
normally accessible to the user in certain circumstances. When
creating a new file, sudoedit checks to make sure the parent
directory of the new file exists before running the editor.
However, a race condition exists if the invoking user can replace
(or create) the parent directory. If a symbolic link is created
in place of the parent directory, sudoedit will run the editor
as long as the target of the link exists. If the target of the
link does not exist, an error message will be displayed. The
race condition can be used to test for the existence of an
arbitrary directory. However, it _cannot_ be used to write to
an arbitrary location.
* Fixed CVE-2021-23240, a flaw in the temporary file handling of
sudoedit's SELinux RBAC support. On systems where SELinux is
enabled, a user with sudoedit permissions may be able to set the
owner of an arbitrary file to the user-ID of the target user.
On Linux kernels that support "protected symlinks", setting
/proc/sys/fs/protected_symlinks to 1 will prevent the bug from
being exploited. For more information see
https://www.sudo.ws/alerts/sudoedit_selinux.html.
* Added writability checks for sudoedit when SELinux RBAC is in use.
This makes sudoedit behavior consistent regardless of whether
or not SELinux RBAC is in use. Previously, the "sudoedit_checkdir"
setting had no effect for RBAC entries.
* When invoked as sudoedit, the same set of command line options
are now accepted as for "sudo -e". The -H and -P options are
now rejected for sudoedit and "sudo -e" which matches the sudo
1.7 behavior. This is part of the fix for CVE-2021-3156.
* Fixed a potential buffer overflow when unescaping backslashes
in the command's arguments. Normally, sudo escapes special
characters when running a command via a shell (sudo -s or sudo
-i). However, it was also possible to run sudoedit with the -s
or -i flags in which case no escaping had actually been done,
making a buffer overflow possible. This fixes CVE-2021-3156.
--85854_Tue_Feb__9_16_02_43_MST_2021
Content-Type: application/pgp-signature
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEWdHpzLorN2cE/dNbqfTAIc6kcPsFAmAjFJMACgkQqfTAIc6k
cPsy0RAAmrtYTYGK5RUdTPfFmy/nmC1BcDkTZYFObhcfXXGWXf0RectZrPSFldGj
yIcuIsGvCI+brCEIXC98DjZ04pBw5e7NwdkTwIiB2HZS9sG3nO/wqjmqnKiHOW9e
OcQ14IzWnnE7cEmiWHs8HVxwmzyjviOb2flS9nRdcnAbK9xYsuVePMwHtSewi9da
2iMt3gtTw6/53j1oHia52Bx4E3AptMMCxJmj0LrnMrmY+0jaHqFoN2q6ZiPKlGWk
FtmH87dCCX2HSii5gNlRsYv921N13fLLMQeA81YVucIYxIUnscpRkuHU6FnGVs5w
m1ICFnnHm/SQyrrvitOBGcdsmp3ZWK9PDWf24WG+1GTWUu0B6zaQMa6EvY3ZFWbw
poLaga9LrF/VYpU9JtBTx3ekzFnP6dt21xVMtBwUx54SGwEWMffVBEGcsyJV0utR
bkhggBMlRgn6ScOCIWbmUtmSQlMnxJdLGot8NwQ08sU1LTljW0bYPs3hJ504VnPB
fl8r6tVZAXVRR51ZBECUbSwQTE9cULiRtE5htbda1WuIvFgjWTGdidsMz6G4MKTN
owlirS/3sT+pyjkQ6lGvWCBN3bEiyj09fou4ArQd3z64xv3zf1JNPHNK4dELU7vd
N7rV8ymCmAgL1jjWHy4RNtjGUEXRPX/hkYkICI+Se6jrm9macqg=
=0kf7
-----END PGP SIGNATURE-----
--85854_Tue_Feb__9_16_02_43_MST_2021--
--===============7957592352175647864==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
____________________________________________________________
sudo-announce mailing list <[email protected]>
For list information, options, or to unsubscribe, visit:
https://www.sudo.ws/mailman/listinfo/sudo-announce
--===============7957592352175647864==--