From: Peter Korsgaard <peter@korsgaard.com>
To: Arnout Vandecappelle via buildroot <buildroot@buildroot.org>
Subject: Re: [Buildroot] [git commit] package/dbus: security bump to version 1.2.28
Date: Sun, 16 Jul 2023 08:06:15 +0200 [thread overview]
Message-ID: <87cz0se6g8.fsf@48ers.dk> (raw)
In-Reply-To: <20230625192619.D571E84CA1@busybox.osuosl.org> (Arnout Vandecappelle via buildroot's message of "Sun, 25 Jun 2023 21:24:32 +0200")
>>>>> "Arnout" == Arnout Vandecappelle via buildroot <buildroot@buildroot.org> writes:
> commit: https://git.buildroot.net/buildroot/commit/?id=52ae2a4e1d10da4ea46bc730db69a40d79eb835a
> branch: https://git.buildroot.net/buildroot/commit/?id=refs/heads/master
> Fixes the following security issues:
> - CVE-2023-34969: Fix an assertion failure in dbus-daemon when a privileged
> Monitoring connection (dbus-monitor, busctl monitor, gdbus monitor or
> similar) is active, and a message from the bus driver cannot be delivered
> to a client connection due to <deny> rules or outgoing message quota.
> This is a denial of service if triggered maliciously by a local attacker.
> - Fix an incorrect assertion that could be used to crash dbus-daemon or
> other users of DBusServer prior to authentication, if libdbus was compiled
> with assertions enabled.
> For details, see the NEWS file:
> https://gitlab.freedesktop.org/dbus/dbus/blob/dbus-1.12/NEWS
> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
Committed to 2023.02.x and 2023.05.x, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-16 6:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-25 19:24 [Buildroot] [git commit] package/dbus: security bump to version 1.2.28 Arnout Vandecappelle via buildroot
2023-07-16 6:06 ` Peter Korsgaard [this message]
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=87cz0se6g8.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.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