From: Taylan Kammer <taylan.kammer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Exim CVEs (21Nails)
Date: Mon, 17 May 2021 17:26:36 +0200 [thread overview]
Message-ID: <05916828-a36c-3d65-79fe-6ca1a6c543f1@gmail.com> (raw)
In-Reply-To: <YKKBT3JBQsrw+xbl@jasmine.lan>
On 17.05.2021 16:44, Leo Famulari wrote:
> On Mon, May 17, 2021 at 12:10:26PM +0200, Taylan Kammer wrote:
>> Hi Guix people,
>>
>> Just wanted to make sure everyone's aware, since we package Exim:
>>
>> https://blog.qualys.com/vulnerabilities-research/2021/05/04/21nails-multiple-vulnerabilities-in-exim-mail-server
>>
>> "Last fall, the Qualys Research Team engaged in a thorough code audit of Exim
>> and discovered 21 unique vulnerabilities. Ten of these vulnerabilities can be
>> exploited remotely. Some of them leading to provide root privileges on the
>> remote system. And eleven can be exploited locally with most of them can be
>> exploited in either default configuration or in a very common configuration.
>> Some of the vulnerabilities can be chained together to obtain a full remote
>> unauthenticated code execution and gain root privileges on the Exim Server.
>> Most of the vulnerabilities discovered by the Qualys Research Team for e.g.
>> CVE-2020-28017 affects all versions of Exim going back all the way to 2004
>> (going back to the beginning of its Git history 17 years ago)."
>
> Fixed in commit 4ca8a00263 (gnu: Exim: Update to 4.94.2 [security
> fixes].)
>
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=4ca8a002633f5d5c88c689fd41a686b5cdff33ec
>
On the same day that article was published, neat! :-)
--
Taylan
next prev parent reply other threads:[~2021-05-17 15:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 10:10 Exim CVEs (21Nails) Taylan Kammer
2021-05-17 14:44 ` Leo Famulari
2021-05-17 15:26 ` Taylan Kammer [this message]
2021-05-17 16:20 ` 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=05916828-a36c-3d65-79fe-6ca1a6c543f1@gmail.com \
--to=taylan.kammer@gmail.com \
--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).