all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: Julien Lepiller <julien@lepiller.eu>
Cc: 52421@debbugs.gnu.org
Subject: [bug#52421] [PATCH][SECURITY] gnu: java-log4j-api: Update to 2.15.0.
Date: Sat, 11 Dec 2021 22:08:27 +0100	[thread overview]
Message-ID: <87o85m6e9g.fsf@gnu.org> (raw)
In-Reply-To: <20211211031159.29aa79db@tachikoma.lepiller.eu> (Julien Lepiller's message of "Sat, 11 Dec 2021 03:11:59 +0100")

Hi,

Julien Lepiller <julien@lepiller.eu> skribis:

> today I learnt about a CVE on log4j. Looking more closely, it seems
> that log4j2 has had 3 CVEs (at least 3 are listed on
> https://logging.apache.org/log4j/2.x/security.html) and we're
> vulnerable to all of them \o/
>
> This series updates to the latest version. Thankfully, log4j keeps a
> stable API, so there's no breakage in dependents, but a few
> dependencies had to be added/updated.

I had a quick look and it all LGTM.

Thanks for taking care of it!

Ludo’.




      parent reply	other threads:[~2021-12-11 21:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-11  2:11 [bug#52421] [PATCH][SECURITY] gnu: java-log4j-api: Update to 2.15.0 Julien Lepiller
2021-12-11  2:23 ` [bug#52421] [PATCH 1/5] gnu: java-jansi: Update to 2.4.0 Julien Lepiller
2021-12-11  2:23 ` [bug#52421] [PATCH 2/5] gnu: Add java-jctools-core-1 Julien Lepiller
2021-12-11 21:09   ` [bug#52421] [PATCH][SECURITY] gnu: java-log4j-api: Update to 2.15.0 Ludovic Courtès
2021-12-12 18:25     ` bug#52421: " Julien Lepiller
2021-12-11  2:23 ` [bug#52421] [PATCH 3/5] gnu: Add java-conversant-disruptor Julien Lepiller
2021-12-11  2:23 ` [bug#52421] [PATCH 4/5] gnu. java-lmax-disruptor: Update to 3.4.4 Julien Lepiller
2021-12-11  2:23 ` [bug#52421] [PATCH 5/5] gnu: java-log4j-api: Update to 2.15.0 Julien Lepiller
2021-12-11 21:08 ` Ludovic Courtès [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=87o85m6e9g.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=52421@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    /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.