From: David Craven <david@craven.ch>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Add murmur.
Date: Sun, 12 Feb 2017 18:54:57 +0100 [thread overview]
Message-ID: <CAL1_imnE-BXrxOW=Yt-beANiCsah2-jE-jqJtZsG0FEgg4_eHA@mail.gmail.com> (raw)
In-Reply-To: <05c09e9a-eda3-d41e-b02c-b7d52ba1a5c5@crazy-compilers.com>
Hi Hartmut,
Sorry for my snide remark...
>> This hypothetical attacker is trying to escalate privileges. I don't
>> see how starting an unprivileged process would help with that.
>
> Well, simply by an exploiting a bug in that software. This is a quite
> common case :-)
It is my understanding that exploiting a bug in that software can not
help gaining access to privileges that the exploited software does not
have, since this would be a kernel bug.
All attacks that I'm aware of buffer overflow, cross site scripting, sql
injection rely on inserting some code that gets run. But this code
shares the process of the vulnerable program so by extension it shares
it's privileges.
If an attacker already has the privileges required to start the software
I don't think it's possible to gain any more privileges unless that software
has the setuid bit set.
But I have a tendency to oversimplify things, because it gives me the
feeling that I understand it =P
David
next prev parent reply other threads:[~2017-02-12 17:55 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-01 20:43 Add murmur contact.ng0
2017-02-01 20:43 ` [PATCH] gnu: mumble: Add 'murmur' output contact.ng0
2017-02-01 21:15 ` Add murmur ng0
2017-02-09 16:50 ` Ludovic Courtès
2017-02-09 18:20 ` ng0
2017-02-09 22:50 ` Ludovic Courtès
2017-02-10 21:39 ` ng0
2017-02-10 21:54 ` Marius Bakke
2017-02-10 22:15 ` ng0
2017-02-11 14:31 ` Ludovic Courtès
2017-02-11 14:39 ` ng0
2017-02-12 13:37 ` Ludovic Courtès
2017-02-12 13:53 ` ng0
2017-02-12 13:57 ` David Craven
2017-02-12 14:02 ` ng0
2017-02-12 14:37 ` David Craven
2017-02-12 17:01 ` Hartmut Goebel
2017-02-12 17:42 ` pelzflorian (Florian Pelz)
2017-02-13 14:15 ` Ludovic Courtès
2017-02-12 17:54 ` David Craven [this message]
2017-02-14 10:13 ` Hartmut Goebel
2017-02-14 9:00 ` ng0
2017-02-12 12:23 ` server and client in one package -> security issue (was: Add murmur) Hartmut Goebel
2017-02-12 12:31 ` ng0
2017-02-12 12:53 ` David Craven
2017-02-12 16:52 ` server and client in one package -> security issue Hartmut Goebel
2017-02-13 14:13 ` Ludovic Courtès
2017-02-14 10:28 ` Hartmut Goebel
2017-02-14 11:19 ` Andy Wingo
2017-02-14 9:16 ` server and client in one package -> security issue (was: Add murmur) Danny Milosavljevic
2017-02-14 9:51 ` ng0
2017-02-14 10:44 ` server and client in one package -> security issue Hartmut Goebel
2017-04-24 7:01 ` Maxim Cournoyer
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='CAL1_imnE-BXrxOW=Yt-beANiCsah2-jE-jqJtZsG0FEgg4_eHA@mail.gmail.com' \
--to=david@craven.ch \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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
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).