From: classabbyamp <classabbyamp@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] log4j fallout
Date: Thu, 06 Oct 2022 10:08:24 +0200 [thread overview]
Message-ID: <20221006080824.ixQnDcNIaXnntfowaKk2vucwMNSMmCkanMrGarF_1o4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34534@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 866 bytes --]
Closed issue by leahneukirchen on void-packages repository
https://github.com/void-linux/void-packages/issues/34534
Description:
These packages contain old, vulnerable versions of log4j.
- [x] apache-jmeter-5.3_1 /usr/libexec/apache-jmeter/lib/log4j-core-2.13.1.jar
- [x] apache-storm-2.2.0_3 /usr/lib/apache-storm/external/storm-autocreds/log4j-core-2.11.2.jar
- [x] arduino-1.8.13_1 /usr/lib/arduino/lib/log4j-core-2.12.0.jar
- [x] elasticsearch-5.1.2_2 /usr/share/elasticsearch/lib/log4j-core-2.7.jar
- [x] sbt-1.3.10_2 /usr/share/sbt/lib/local-preloaded/org/apache/logging/log4j/log4j-core/2.11.2/log4j-core-2.11.2.jar
Also Log4j 1.2 is EOL and full of CVE:
- [x] davmail-5.5.1_2 /usr/share/davmail/lib/log4j-1.2.16.jar
- [x] zookeeper-3.4.13_2 /usr/share/zookeeper/lib/log4j-1.2.17.jar
cc @knusbaum @bougyman @Gottox @igorsantana @Trojan295
next prev parent reply other threads:[~2022-10-06 8:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-14 19:46 [ISSUE] " leahneukirchen
2021-12-14 19:53 ` leahneukirchen
2022-01-07 9:54 ` hiljusti
2022-01-07 9:54 ` hiljusti
2022-01-18 18:43 ` knusbaum
2022-01-18 20:12 ` knusbaum
2022-06-29 0:55 ` classabbyamp
2022-06-29 0:55 ` classabbyamp
2022-09-27 2:13 ` github-actions
2022-09-27 21:55 ` Piraty
2022-09-28 8:33 ` Anachron
2022-09-28 8:36 ` Anachron
2022-09-28 8:42 ` Anachron
2022-10-06 8:08 ` classabbyamp [this message]
2022-10-06 8:08 ` classabbyamp
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=20221006080824.ixQnDcNIaXnntfowaKk2vucwMNSMmCkanMrGarF_1o4@z \
--to=classabbyamp@users.noreply.github.com \
--cc=ml@inbox.vuxu.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;
as well as URLs for NNTP newsgroup(s).