Your message dated Sat, 26 Mar 2022 11:59:13 +0000
with message-id 
<c4d20274f6d76a43fb574d2177f6e3af4235e4be.ca...@adam-barratt.org.uk>
and subject line Closing p-u requests for updates in 11.3
has caused the Debian Bug report #1005351,
regarding bullseye-pu: package apache-log4j2/2.16.0-1~deb11u1
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
1005351: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1005351
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: release.debian.org
Severity: normal
Tags: bullseye
User: release.debian....@packages.debian.org
Usertags: pu
X-Debbugs-Cc: a...@debian.org

Hi,

I would like to fix CVE-2021-44832 in Bullseye. Apache Log4j2 has been
affected by some serious remote code execution vulnerabilities in the
past months. The most severe ones have been already addressed in
buster-security with version 2.17.0-1~deb11u1. CVE-2021-44832 is less
severe thus the security team decided to mark this issue as no-dsa.

I have prepared a backport of the current Log4j2 version in testing
which again is a new upstream release instead of a targeted fix. I am
confident this one works as well as the other upgrades before and I
recommend to use it in stable from now on.

[ Checklist ]
  [x] *all* changes are documented in the d/changelog
  [x] I reviewed all changes and I approve them
  [x] attach debdiff against the package in (old)stable
  [x] the issue is verified as fixed in unstable

Regards,

Markus

Attachment: apache-log4j2_bullseye.debdiff.gz
Description: application/gzip


--- End Message ---
--- Begin Message ---
Package: release.debian.org
Version: 11.3

Hi,

The updates referenced by these bugs were included in stable as part of
this morning's 11.3 point release.

Regards,

Adam

--- End Message ---

Reply via email to