From: Tobias Geerinckx-Rice via Bug reports for GNU Guix <bug-guix@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 37744@debbugs.gnu.org,
GNU Guix maintainers <guix-maintainers@gnu.org>,
guix-security@gnu.org
Subject: bug#37744: Per-user profile directory hijack (CVE-2019-17365 for Nix)
Date: Mon, 14 Oct 2019 13:53:35 +0200 [thread overview]
Message-ID: <87y2xno85o.fsf@nckx> (raw)
In-Reply-To: <87blujsqq0.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 642 bytes --]
Ludo',
Thanks for your report :-p
The 1777 is obviously very bad, no question. However: question:
Ludovic Courtès 写道：
> I don’t see how to let the daemon create ‘per-user/$USER’ on
> behalf of
> the client for clients connecting over TCP. Or we’d need to add
> a
> challenge mechanism or authentication.
I need more cluebat please: say I'm an attacker and connect to
your daemon (over TCP, why not), asking it to create an empty
‘per-user/ludo’.
Assuming the daemon creates it with sane permissions (say 0755) &
without any race conditions, what's my evil plan now?
Kind regards,
T G-R
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2019-10-14 11:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 7:47 bug#37744: Per-user profile directory hijack (CVE-2019-17365 for Nix) Ludovic Courtès
2019-10-14 7:58 ` Ludovic Courtès
2019-10-14 11:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix [this message]
2019-10-14 16:37 ` Maxim Cournoyer
2019-10-15 12:34 ` Ludovic Courtès
2019-10-15 14:31 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 6:57 ` Ludovic Courtès
2019-10-16 10:22 ` Ludovic Courtès
2019-10-16 13:25 ` Ludovic Courtès
2019-10-16 14:22 ` pelzflorian (Florian Pelz)
2019-10-16 15:16 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 15:19 ` pelzflorian (Florian Pelz)
2019-10-16 15:23 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 17:05 ` Ludovic Courtès
2019-10-16 19:50 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 19:55 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 21:40 ` Ludovic Courtès
2019-10-16 21:41 ` Ludovic Courtès
2019-10-16 19:58 ` Julien Lepiller
2019-10-16 21:38 ` Ludovic Courtès
2019-10-16 15:37 ` pelzflorian (Florian Pelz)
2019-10-16 21:39 ` Ludovic Courtès
2019-10-17 2:58 ` pelzflorian (Florian Pelz)
2019-10-17 3:01 ` pelzflorian (Florian Pelz)
2019-10-16 20:28 ` Ludovic Courtès
2019-10-17 16:18 ` Ludovic Courtès
2019-10-17 19:01 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-17 20:25 ` Ludovic Courtès
2019-10-18 2:21 ` Bengt Richter
2019-10-18 14:36 ` Ludovic Courtès
2019-10-19 1:32 ` Bengt Richter
2019-10-16 14:12 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2019-10-16 20:01 ` Ludovic Courtès
2019-10-16 16:28 ` Julien Lepiller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y2xno85o.fsf@nckx \
--to=bug-guix@gnu.org \
--cc=37744@debbugs.gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=guix-security@gnu.org \
--cc=ludo@gnu.org \
--cc=me@tobias.gr \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).