Date: Thu, 25 Sep 2014 11:57:38 -0500 From: Bryan Drewery <bdrewery@FreeBSD.org> To: freebsd-ports@freebsd.org, freebsd-security <freebsd-security@freebsd.org> Subject: Re: bash velnerability Message-ID: <54244982.8010002@FreeBSD.org> In-Reply-To: <54243F0F.6070904@FreeBSD.org> References: <CAHFU5H5WOnAXuFmfQEGkTvwoECATTCC3eKYE3yts%2BBqh1M_8ww@mail.gmail.com> <00000148ab969845-5940abcc-bb88-4111-8f7f-8671b0d0300b-000000@us-west-2.amazonses.com> <54243F0F.6070904@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --RTJRMSCV8MwWaNdi3x9p81JjwPQ5tLPgP Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable On 9/25/2014 11:13 AM, Jung-uk Kim wrote: > On 2014-09-25 02:54:06 -0400, Koichiro Iwao wrote: >> Please let me make corrections. The "shellshock" bash=20 >> vulnerabilities are described by 2 CVEs. - CVE-2014-6271 -=20 >> CVE-2014-7169 >> >> The first CVE is already fixed in latest freebsd ports tree=20 >> (r369185), so far the second CVE is not fixed yet. >=20 > CVE-2014-7169 is fixed now (r369261). >=20 > http://svnweb.freebsd.org/changeset/ports/369261 >=20 > Note the commit log says CVE-2014-3659 but it was actually reassigned > as CVE-2014-7169. >=20 > Jung-uk Kim >=20 The port is fixed with all known public exploits. The package is building currently. However bash still allows the crazy exporting of functions and may still have other parser bugs. I would recommend for the immediate future not using bash for forced ssh commands as well as these guidelines: 1. Do not ever link /bin/sh to bash. This is why it is such a big problem on Linux, as system(3) will run bash by default from CGI. 2. Web/CGI users should have shell of /sbin/nologin. 3. Don't write CGI in shell script / Stop using CGI :) 4. httpd/CGId should never run as root, nor "apache". Sandbox each application into its own user. 5. Custom restrictive shells, like scponly, should not be written in bash= =2E 6. SSH authorized_keys/sshd_config forced commands should also not be written in bash. Cheers, Bryan Drewery --RTJRMSCV8MwWaNdi3x9p81JjwPQ5tLPgP Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQEcBAEBAgAGBQJUJEmCAAoJEDXXcbtuRpfP7PYH/0xaUF1M55vD8+EjDS7Nc9eF zLC5Akrxc9DtoBWmmUnvfpTKsIVQe1m/eUsRAD63zXf0Jt/EsWNllMS+rfkDp4i/ IEbAPvaxsvr5xtZc/vfU3H3/WDAvKFiaVfEwhWjPPiPzFk4Q4NGL0i8epoZPlMMg QJRtlLAlMzPZR2U/w0PZYUeSMPKfmce9YNJNbB3durvHRbuv7KMIP0hL+DM9lyB7 NPv5/1ShSmrvLuORto2iDPluuuDG3FM70J0QIndK+r0nMaH4e0xB68a0hddcTbE5 SeDuHuosY6Af3cCRx4rLUCxVw3ITySmGsEE+BAdOXifJw0oJfAxlB8dwoYx5B/0= =pqt8 -----END PGP SIGNATURE----- --RTJRMSCV8MwWaNdi3x9p81JjwPQ5tLPgP--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54244982.8010002>