[an error occurred while processing this directive]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

[an error occurred while processing this directive]

[<prev] [next>] [day] [month] [year] [list]

Message-ID: <20160111134240.GA25794@scapa.corsac.net>
Date: Mon, 11 Jan 2016 14:42:42 +0100
From: Ben Hutchings <benh@...ian.org>
To: bugtraq@...urityfocus.com
Subject: [SECURITY] [DSA 3440-1] sudo security update

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

- -------------------------------------------------------------------------
Debian Security Advisory DSA-3440-1                   security@...ian.org
https://www.debian.org/security/                            Ben Hutchings
January 11, 2016                      https://www.debian.org/security/faq
- -------------------------------------------------------------------------

Package        : sudo
CVE ID         : CVE-2015-5602
Debian Bug     : 804149

When sudo is configured to allow a user to edit files under a directory
that they can already write to without using sudo, they can actually
edit (read and write) arbitrary files. Daniel Svartman reported that a
configuration like this might be introduced unintentionally if the
editable files are specified using wildcards, for example:

    operator ALL=(root) sudoedit /home/*/*/test.txt

The default behaviour of sudo has been changed so that it does not allow
editing of a file in a directory that the user can write to, or that is
reached by following a symlink in a directory that the user can write
to. These restrictions can be disabled, but this is strongly
discouraged.

For the oldstable distribution (wheezy), this problem has been fixed
in version 1.8.5p2-1+nmu3+deb7u1.

For the stable distribution (jessie), this problem has been fixed in
version 1.8.10p3-1+deb8u3.

For the testing distribution (stretch), this problem has been fixed
in version 1.8.15-1.1.

For the unstable distribution (sid), this problem has been fixed in
version 1.8.15-1.1.

We recommend that you upgrade your sudo packages.

Further information about Debian Security Advisories, how to apply
these updates to your system and frequently asked questions can be
found at: https://www.debian.org/security/

Mailing list: debian-security-announce@...ts.debian.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQEcBAEBCgAGBQJWk7FLAAoJEG3bU/KmdcClQYwH/3LGjK0rNnxrGTcOwoVMAtWi
iK89C+0P/GDEuqVjpG+WKArvgwyWBsx9AXrHkyXKq8uFdAuYJ2BzsD1r0zmgtRR9
8+d9ez9WwJLzrjFjkrvJp2XgWbIPq2n6eEA0W00oJ+rgXNlvs52xBuWVqSThSqus
b6ta2bIKpGkIotNkXNwEHfCCwMk4BkwECNDXMlIcC9Qz2Gpy8rYSkAyJg4nmcKeb
6VFVsnVp4l8KU9hnFiRmOw2L/yCbNC/IqiboTAR/m7OJJa6HnJ6ohW6iV+ddy9cO
rLvsBlbrvP/DUUPqpIiOmjrlmXYuxnSAYaUgbwnq3odwHLn7CbZUovyIkVOCuoo=
=Yi0D
-----END PGP SIGNATURE-----