From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ludovic =?UTF-8?Q?Court=C3=A8s?= Subject: bug#37744: Per-user profile directory hijack (CVE-2019-17365 for Nix) Date: Wed, 16 Oct 2019 15:25:56 +0200 Message-ID: <878spksty3.fsf@gnu.org> References: <87o8yjsr8o.fsf@gnu.org> <87blujsqq0.fsf@gnu.org> <87y2xno85o.fsf@nckx> <87d0eyuqzd.fsf@gnu.org> <87mue2nkrj.fsf@nckx> <8736fttby6.fsf@gnu.org> <87tv89rnva.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:470:142:3::10]:57146) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1iKjKR-00081F-Mr for bug-guix@gnu.org; Wed, 16 Oct 2019 09:27:04 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1iKjKQ-0000HJ-Ie for bug-guix@gnu.org; Wed, 16 Oct 2019 09:27:03 -0400 Received: from debbugs.gnu.org ([209.51.188.43]:36599) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1iKjKQ-0000HD-Fn for bug-guix@gnu.org; Wed, 16 Oct 2019 09:27:02 -0400 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1iKjKQ-0008Rl-9p for bug-guix@gnu.org; Wed, 16 Oct 2019 09:27:02 -0400 Sender: "Debbugs-submit" Resent-Message-ID: In-Reply-To: <87tv89rnva.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Wed, 16 Oct 2019 12:22:33 +0200") List-Id: Bug reports for GNU Guix List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-guix-bounces+gcggb-bug-guix=m.gmane.org@gnu.org Sender: "bug-Guix" To: 37744@debbugs.gnu.org, guix-security@gnu.org Hello! In addition to the news entry that =E2=80=98guix pull=E2=80=99 will display= , we may want to publicize the issue. In particular, should we: 1. Apply for a new CVE? 2. Post an article on the blog to explain in detail what happened? That should probably include an analysis like that at , given that Guix does things not entirely like Nix here. 3. Email that analysis to oss-security? 4. Push a new release? I=E2=80=99m tempted to think that we should do 1 to 3, as quickly as we can. Help welcome, in particular on #2! As for #4, I think we should push a new release soon anyway, but maybe not just specifically for this issue since it can be addressed simply by upgrading. Thoughts? Ludo=E2=80=99.