* Ask about cgroups security
@ 2014-02-27 3:59 nguyen thai
[not found] ` <CACBeRbYh58m+MuCefJP0SzT5AQADDJh==KyeDFG8UdRb=NQvQg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
0 siblings, 1 reply; 2+ messages in thread
From: nguyen thai @ 2014-02-27 3:59 UTC (permalink / raw)
To: Cgroups maillist
Hi everyone,
I'm working with SELinux and cgroups to implement SELinux on cgroups
file. This is expected to improve cgroups security. But i'm having a
confusion identifying the possible vulnerabilities of current cgroups
DAC check and what need to be improved.
I know the cgroup interface is the filesystem. But how this can be the
drawback of current implementation. I mean how hackers may use this to
attack the system. Tejun Heo said that the biggest issue with cgroup
is the ability for non-root users to gain access to the raw kernel
control knobs. anyone you explain more about this?
Thank you very much.
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Ask about cgroups security
[not found] ` <CACBeRbYh58m+MuCefJP0SzT5AQADDJh==KyeDFG8UdRb=NQvQg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
@ 2014-02-28 11:39 ` Eric W. Biederman
0 siblings, 0 replies; 2+ messages in thread
From: Eric W. Biederman @ 2014-02-28 11:39 UTC (permalink / raw)
To: nguyen thai; +Cc: Cgroups maillist
nguyen thai <thai.bkset-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Hi everyone,
>
> I'm working with SELinux and cgroups to implement SELinux on cgroups
> file. This is expected to improve cgroups security. But i'm having na
> confusion identifying the possible vulnerabilities of current cgroups
> DAC check and what need to be improved.
> I know the cgroup interface is the filesystem. But how this can be the
> drawback of current implementation. I mean how hackers may use this to
> attack the system. Tejun Heo said that the biggest issue with cgroup
> is the ability for non-root users to gain access to the raw kernel
> control knobs. anyone you explain more about this?
The problem is poor design of the basic mechanisms. The result is that
in some that in several instances a poor/unmaintainable choice of
abstractions were exposed. That is there are values exposed for
tweaking that if a non-root user is allowed to change them can lead to
subversion of the policy framework that it is the intetion of cgroups to
implement.
The only sane fix is to go through the exported control knobs and
catalogue them as safe or not safe. And then work towards removing the
unsafe knobs.
Eric
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2014-02-28 11:39 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2014-02-27 3:59 Ask about cgroups security nguyen thai
[not found] ` <CACBeRbYh58m+MuCefJP0SzT5AQADDJh==KyeDFG8UdRb=NQvQg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2014-02-28 11:39 ` Eric W. Biederman
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 NNTP newsgroup(s).