From: Jussi Kukkonen <jussi.kukkonen@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/1][fido][dizzy] dbus: Fix CVE-2015-0245
Date: Wed, 24 Jun 2015 23:04:57 +0300 [thread overview]
Message-ID: <cover.1435174534.git.jussi.kukkonen@intel.com> (raw)
This is for fido and possibly dizzy, not master.
D-Bus 1.8.16 fixes CVE-2015-0245 "prevent forged ActivationFailure from
non-root processes". This patch does not contain the same fix but a
configuration change that upstream suggests as a easily backportable
fix.
The issue is only a local denial of service so not terribly dangerous,
but should be worth fixing since the patch is not intrusive.
I've only tested this on fido, so the [dizzy] is just a suggestion.
Cheers, Jussi
The following changes since commit eb4a134a60e3ac26a48379675ad6346a44010339:
scripts/combo-layer: Fix exit codes and tty handling (2015-06-11 15:00:20 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib jku/dbus-fix-for-fido
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=jku/dbus-fix-for-fido
Jussi Kukkonen (1):
dbus: CVE-2015-0245: prevent forged ActivationFailure
meta/recipes-core/dbus/dbus.inc | 1 +
...015-0245-prevent-forged-ActivationFailure.patch | 48 ++++++++++++++++++++++
2 files changed, 49 insertions(+)
create mode 100644 meta/recipes-core/dbus/dbus/CVE-2015-0245-prevent-forged-ActivationFailure.patch
--
2.1.4
next reply other threads:[~2015-06-24 20:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-24 20:04 Jussi Kukkonen [this message]
2015-06-24 20:06 ` [PATCH 1/1] dbus: CVE-2015-0245: prevent forged ActivationFailure Jussi Kukkonen
2015-06-26 14:30 ` Joshua Lock
2015-06-28 13:24 ` [PATCH 0/1][fido][dizzy] dbus: Fix CVE-2015-0245 akuster808
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1435174534.git.jussi.kukkonen@intel.com \
--to=jussi.kukkonen@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox