From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 0/1] Dbus update 1.10.12 for core-updates
Date: Mon, 10 Oct 2016 22:57:47 +0200 [thread overview]
Message-ID: <87wphfgbw4.fsf@gnu.org> (raw)
In-Reply-To: <cover.1476121251.git.leo@famulari.name> (Leo Famulari's message of "Mon, 10 Oct 2016 13:44:16 -0400")
Hello!
Leo Famulari <leo@famulari.name> skribis:
> There's a format string vulnerability (with unknown impact) in our dbus:
>
> http://seclists.org/oss-sec/2016/q4/85
>
> Please read that message and the linked bug report.
>
> My understanding of the upsream analysis of the format string
> vulnerability is that only the bus owner can trigger it. So, if the
> vulnerability allows arbitrary code execution, it would mean that root
> could execute arbitrary code via the system bus... not a huge problem.
> But still undesirable.
Yeah, seems hard to exploit. Apparently even if we’re not using systemd
activations we could be vulnerable, because it’s about how specific
messages are processed, IIUC.
> What do you think? Should we update this on core-updates?
I think so.
> Should we graft it on master?
Unless there are possible ABI incompatibilies, it probably doesn’t hurt
to do that.
Thank you!
Ludo’.
next prev parent reply other threads:[~2016-10-10 20:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-10 17:44 [PATCH 0/1] Dbus update 1.10.12 for core-updates Leo Famulari
2016-10-10 17:44 ` [PATCH 1/1] gnu: dbus: Update to 1.10.12 Leo Famulari
2016-10-10 18:10 ` [PATCH 0/1] Dbus update 1.10.12 for core-updates Kei Kebreau
2016-10-10 18:39 ` John Darrington
2016-10-10 19:30 ` Kei Kebreau
2016-10-10 20:57 ` Ludovic Courtès [this message]
2016-10-12 16:41 ` Leo Famulari
2016-10-13 20:19 ` Ludovic Courtès
2016-10-14 3:01 ` Leo Famulari
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=87wphfgbw4.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).