From: Alexei Starovoitov <email@example.com> To: Andy Lutomirski <firstname.lastname@example.org> Cc: Song Liu <email@example.com>, Kees Cook <firstname.lastname@example.org>, Networking <email@example.com>, bpf <firstname.lastname@example.org>, Alexei Starovoitov <email@example.com>, Daniel Borkmann <firstname.lastname@example.org>, Kernel Team <Kernelemail@example.com>, Lorenz Bauer <firstname.lastname@example.org>, Jann Horn <email@example.com>, Greg KH <firstname.lastname@example.org>, Linux API <email@example.com>, LSM List <firstname.lastname@example.org> Subject: Re: [PATCH v2 bpf-next 1/4] bpf: unprivileged BPF access via /dev/bpf Date: Mon, 5 Aug 2019 18:11:36 -0700 Message-ID: <20190806011134.p5baub5l3t5fkmou@ast-mbp> (raw) In-Reply-To: <CALCETrVtPs8gY-H4gmzSqPboid3CB++n50SvYd6RU9YVde_-Ow@mail.gmail.com> On Mon, Aug 05, 2019 at 02:25:35PM -0700, Andy Lutomirski wrote: > It tries to make the kernel respect the access modes for fds. Without > this patch, there seem to be some holes: nothing looked at program fds > and, unless I missed something, you could take a readonly fd for a > program, pin the program, and reopen it RW. I think it's by design. iirc Daniel had a use case for something like this. The key to understand is that bpf is not about security. It's about safety. All features are geared to safety. The users are trusted most of the time. The number of unprivileged bpf use cases is tiny compared to trusted. Hence unprivileged bpf is actually something that can be deprecated. > Other than the issue that this patch partially fixes, can you see any > reason that loading a program should require privilege? Obviously the > verifier is weakened a bit when called by privileged users, but a lot > of that is about excessive resource usage and various less-well-tested > features. It seems to me that most of the value of bpf() should be > available to programs that should not need privilege to load. Are > there things I'm missing? see below. > LPM: I don't see why this requires privilege at all. It indeed checks > capable(CAP_SYS_ADMIN), but I don't see why. see below. > > > > > Attaching to a cgroup already has file based permission checks. > > The user needs to open cgroup directory to attach. > > acls on cgroup dir can already be used to prevent attaching to > > certain parts of cgroup hierarchy. > > The current checks seem inadequate. > > $ echo 'yay' </sys/fs/cgroup/systemd/system.slice/ > > The ability to obtain an fd to a cgroup does *not* imply any right to > modify that cgroup. The ability to write to a cgroup directory > already means something else -- it's the ability to create cgroups > under the group in question. I'm suggesting that a new API be added > that allows attaching a bpf program to a cgroup without capabilities > and that instead requires write access to a new file in the cgroup > directory. (It could be a single file for all bpf types or one file > per type. I prefer the latter -- it gives the admin finer-grained > control.) This is something to discuss. I don't mind something like this, but in general bpf is not for untrusted users. Hence I don't want to overdesign. > > > What we need is to drop privileges sooner in daemons like systemd. > > This is doable right now: systemd could fork off a subprocess and > delegate its cgroup operations to it. It would be maybe a couple > hundred lines of code. As an added benefit, that subprocess could > verify that the bpf operations in question are reasonable. > Alternatively, if there was a CAP_BPF_ADMIN, systemd could retain that > capability and flip it on and off as needed. See https://github.com/systemd/systemd/blob/01234e1fe777602265ffd25ab6e73823c62b0efe/src/core/bpf-firewall.c#L671-L674 bpf based IP sandboxing doesn't work in 'systemd --user'. That is just one of the problems that people complained about. Note that systemd bpf usage is basic. There is ongoing work to adopt libbpf in systemd, so more features and more use cases will open up. Inside containers and inside nested containers we need to start processes that will use bpf. All of the processes are trusted. We need to drop root not to be secure, but to be safe. Consider a bug in a code that accidently did sys_kill(-1). Dropping root is a mitigation for bugs like this. > > > Container management daemon runs in the nested containers. > > These trusted daemons need to have access to full bpf, but they > > don't want to be root all the time. > > They cannot flip back and forth via seteuid to root every time they > > need to do bpf. > > Hence the idea is to have a file that this daemon can open, > > then drop privileges and still keep doing bpf things because FD is held. > > Outer container daemon can pass this /dev/bpf's FD to inner daemon, etc. > > This /dev/bpf would be accessible to root only. > > There is no desire to open it up to non-root. > > This seems extremely dangerous right now. A program that can bypass > *all* of the capable() checks in bpf() can do a whole lot. Among > other things, it can read all of kernel memory. It's 'dangerous' only if you think about it from security point of view. The tracing (and sometimes networking) bpf progs need to read all of kernel memory without being root. That is the whole point of the /dev/bpf. > This seems to have most of the same problems. My main point is that > it conflates a whole lot of different permissions, and I really don't > think it's that much work to mostly disentangle the permissions in > question. My little series (if completed) plus a patch to allow > unprivileged cgroup attach operations if you have an FMODE_WRITE fd to > an appropriate file should get most of the way there. I think I understand your concern. One /dev/bpf magic to by-pass all of capable() checks in bpf doesn't look nice indeed. Now to answer your question about capable(sys_admin) in the verifier. See this bugfix: https://git.kernel.org/pub/scm/linux/kernel/git/bpf/bpf.git/commit/?id=7c2e988f400e83501e0a3568250780609b7c8263 It's a bug in the JIT that was there pretty much forever, but it got exposed due to two new bpf features. Initially syzbot complained that bounded loops allow jmp to 1st insn. syzbot reproducer contained 'never taken' branch, so buggy JIT wouldn't have caused a kernel panic for this reproducer though JITed x86 code is broken. It took me few days to realize that with bpf2bpf calls _and_ bounded loops I can craft a test that will expose this JIT bug and will crash the kernel. So a combination of two recent verifier features exposed old JIT bug that would have been a security issue if we didn't gate these verifier features for root only. Now it's simply a kernel bugfix. Such subtle bugs happen all the time when new verifier features are introduced. Hence we always start them with root only. bpf2bpf calls, bounded loops, precision tracking, dead code elimination, LPM maps, many programs type are root only. We don't want cve-s to be filed for every bug like this. Even if we start relaxing features (like dropping root from LPM map) at any given time there will be a lot of useful verifier features, maps and program types that are root only. For root == for trusted users only. Unfortunately this approach creates adoption problem. The trusted users don't want to be root to use bpf. Hence this /dev/bpf. To solve your concern of bypassing all capable checks... How about we do /dev/bpf/full_verifier first? It will replace capable() checks in the verifier only. How to delegate cgroup attach permission is a follow up discussion. Could be special files in cgroup dir as you proposed or something else. Let's table that and focus on the verifier first.
next prev parent reply index Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <email@example.com> [not found] ` <firstname.lastname@example.org> [not found] ` <email@example.com> [not found] ` <3C595328-3ABE-4421-9772-8D41094A4F57@fb.com> [not found] ` <CALCETrWBnH4Q43POU8cQ7YMjb9LioK28FDEQf7aHZbdf1eBZWg@mail.gmail.com> [not found] ` <0DE7F23E-9CD2-4F03-82B5-835506B59056@fb.com> [not found] ` <CALCETrWBWbNFJvsTCeUchu3BZJ3SH3dvtXLUB2EhnPrzFfsLNA@mail.gmail.com> [not found] ` <201907021115.DCD56BBABB@keescook> [not found] ` <CALCETrXTta26CTtEDnzvtd03-WOGdXcnsAogP8JjLkcj4-mHvg@mail.gmail.com> [not found] ` <4A7A225A-6C23-4C0F-9A95-7C6C56B281ED@fb.com> [not found] ` <CALCETrX2bMnwC6_t4b_G-hzJSfMPrkK4YKs5ebcecv2LJ0rt3w@mail.gmail.com> [not found] ` <514D5453-0AEE-420F-AEB6-3F4F58C62E7E@fb.com> [not found] ` <1DE886F3-3982-45DE-B545-67AD6A4871AB@amacapital.net> [not found] ` <7F51F8B8-CF4C-4D82-AAE1-F0F28951DB7F@fb.com> [not found] ` <77354A95-4107-41A7-8936-D144F01C3CA4@fb.com> [not found] ` <369476A8-4CE1-43DA-9239-06437C0384C7@fb.com> 2019-07-30 20:24 ` Andy Lutomirski 2019-07-31 8:10 ` Song Liu 2019-07-31 19:09 ` Andy Lutomirski 2019-08-02 7:21 ` Song Liu 2019-08-04 22:16 ` Andy Lutomirski 2019-08-05 0:08 ` Andy Lutomirski 2019-08-05 5:47 ` Andy Lutomirski 2019-08-05 7:36 ` Song Liu 2019-08-05 17:23 ` Andy Lutomirski 2019-08-05 19:21 ` Alexei Starovoitov 2019-08-05 21:25 ` Andy Lutomirski 2019-08-05 22:21 ` Andy Lutomirski 2019-08-06 1:11 ` Alexei Starovoitov [this message] 2019-08-07 5:24 ` Andy Lutomirski 2019-08-07 9:03 ` Lorenz Bauer 2019-08-07 13:52 ` Andy Lutomirski 2019-08-13 21:58 ` Alexei Starovoitov 2019-08-13 22:26 ` Daniel Colascione 2019-08-13 23:24 ` Andy Lutomirski 2019-08-13 23:06 ` Andy Lutomirski 2019-08-14 0:57 ` Alexei Starovoitov 2019-08-14 17:51 ` Andy Lutomirski 2019-08-14 22:05 ` Alexei Starovoitov 2019-08-14 22:30 ` Andy Lutomirski 2019-08-14 23:33 ` Alexei Starovoitov 2019-08-14 23:59 ` Andy Lutomirski 2019-08-15 0:36 ` Alexei Starovoitov 2019-08-15 11:24 ` Jordan Glover 2019-08-15 17:28 ` Alexei Starovoitov 2019-08-15 18:36 ` Andy Lutomirski 2019-08-15 23:08 ` Alexei Starovoitov 2019-08-16 9:34 ` Jordan Glover 2019-08-16 9:59 ` Thomas Gleixner 2019-08-16 11:33 ` Jordan Glover 2019-08-16 19:52 ` Alexei Starovoitov 2019-08-16 20:28 ` Thomas Gleixner 2019-08-17 15:02 ` Alexei Starovoitov 2019-08-17 15:44 ` Andy Lutomirski 2019-08-19 9:15 ` Thomas Gleixner 2019-08-19 17:27 ` Alexei Starovoitov 2019-08-19 17:38 ` Andy Lutomirski 2019-08-15 18:43 ` Jordan Glover 2019-08-15 19:46 ` Kees Cook 2019-08-15 23:46 ` Alexei Starovoitov 2019-08-16 0:54 ` Andy Lutomirski 2019-08-16 5:56 ` Song Liu 2019-08-16 21:45 ` Alexei Starovoitov 2019-08-16 22:22 ` Christian Brauner 2019-08-17 15:08 ` Alexei Starovoitov 2019-08-17 15:16 ` Christian Brauner 2019-08-17 15:36 ` Alexei Starovoitov 2019-08-17 15:42 ` Christian Brauner 2019-08-22 14:17 ` Daniel Borkmann 2019-08-22 15:16 ` Andy Lutomirski 2019-08-22 15:17 ` RFC: very rough draft of a bpf permission model Andy Lutomirski 2019-08-22 23:26 ` Alexei Starovoitov 2019-08-23 23:09 ` Andy Lutomirski 2019-08-26 22:36 ` Alexei Starovoitov 2019-08-27 0:05 ` Andy Lutomirski 2019-08-27 0:34 ` Alexei Starovoitov 2019-08-22 22:48 ` [PATCH v2 bpf-next 1/4] bpf: unprivileged BPF access via /dev/bpf Alexei Starovoitov
Reply instructions: You may reply publically 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 * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20190806011134.p5baub5l3t5fkmou@ast-mbp \ --firstname.lastname@example.org \ --cc=Kernelemail@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ /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
Linux-Security-Module Archive on lore.kernel.org Archives are clonable: git clone --mirror https://lore.kernel.org/linux-security-module/0 linux-security-module/git/0.git # If you have public-inbox 1.1+ installed, you may # initialize and index your mirror using the following commands: public-inbox-init -V2 linux-security-module linux-security-module/ https://lore.kernel.org/linux-security-module \ firstname.lastname@example.org email@example.com public-inbox-index linux-security-module Newsgroup available over NNTP: nntp://nntp.lore.kernel.org/org.kernel.vger.linux-security-module AGPL code for this site: git clone https://public-inbox.org/ public-inbox