From: Leo Famulari <leo@famulari.name>
To: "Nicolò Balzarotti" <anothersms@gmail.com>
Cc: 47674@debbugs.gnu.org
Subject: bug#47674: dnsmasq is vulnerable to CVE-2021-3448
Date: Fri, 9 Apr 2021 15:33:22 -0400 [thread overview]
Message-ID: <YHCsAioNoPoTh5EH@jasmine.lan> (raw)
In-Reply-To: <87pmz3mr2k.fsf@guixSD.i-did-not-set--mail-host-address--so-tickle-me>
[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]
On Fri, Apr 09, 2021 at 05:10:43PM +0200, Nicolò Balzarotti wrote:
> CVE-2021-3448
>
> A flaw was found in dnsmasq in versions before 2.85. When configured to
> use a specific server for a given network interface, dnsmasq uses a
> fixed port while forwarding queries. An attacker on the network, able to
> find the outgoing port used by dnsmasq, only needs to guess the random
> transmission ID to forge a reply and get it accepted by dnsmasq. This
> flaw makes a DNS Cache Poisoning attack much easier. The highest threat
> from this vulnerability is to data integrity.
>
> guix ships dnsmasq@2.84. guix refresh shows version 2.85 is available,
> and there are 43 dependent packages so this can go directly to master.
>
> All dependent packages (refresh -l) build fine except for
> python2-libvirt@7.2.0, which is failing also on master
> (libvirt-python requires Python >= 3.5 to build). Since it's a python2
> package and no other packages depends on it, can we just drop it?
Yes, sounds good.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-04-09 19:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-09 15:10 bug#47674: dnsmasq is vulnerable to CVE-2021-3448 Nicolò Balzarotti
2021-04-09 19:33 ` Leo Famulari [this message]
2021-04-09 19:34 ` Leo Famulari
2021-04-09 19:38 ` Leo Famulari
2021-04-09 19:47 ` Nicolò Balzarotti
2021-04-09 20:07 ` Leo Famulari
2021-04-10 21:39 ` Nicolò Balzarotti
2021-04-10 22:05 ` Leo Famulari
2021-04-10 22:27 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
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=YHCsAioNoPoTh5EH@jasmine.lan \
--to=leo@famulari.name \
--cc=47674@debbugs.gnu.org \
--cc=anothersms@gmail.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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.