This is an automatically created tracking bug! It was created to ensure that one or more security vulnerabilities are fixed in affected versions of fedora-all. For comments that are specific to the vulnerability please use bugs filed against the "Security Response" product referenced in the "Blocks" field. For more information see: http://fedoraproject.org/wiki/Security/TrackingBugs When submitting as an update, use the fedpkg template provided in the next comment(s). This will include the bug IDs of this tracking bug as well as the relevant top-level CVE bugs. Please also mention the CVE IDs being fixed in the RPM changelog and the fedpkg commit message. NOTE: this issue affects multiple supported versions of Fedora. While only one tracking bug has been filed, please correct all affected versions at the same time. If you need to fix the versions independent of each other, you may clone this bug as appropriate.
Use the following template to for the 'fedpkg update' request to submit an update for this issue as it contains the top-level parent bug(s) as well as this tracking bug. This will ensure that all associated bugs get updated when new packages are pushed to stable. ===== # bugfix, security, enhancement, newpackage (required) type=security # low, medium, high, urgent (required) severity=high # testing, stable request=testing # Bug numbers: 1234,9876 bugs=2030932,2030945 # Description of your update notes=Security fix for [PUT CVEs HERE] # Enable request automation based on the stable/unstable karma thresholds autokarma=True stable_karma=3 unstable_karma=-3 # Automatically close bugs when this marked as stable close_bugs=True # Suggest that users restart after update suggest_reboot=False ====== Additionally, you may opt to use the bodhi web interface to submit updates: https://bodhi.fedoraproject.org/updates/new
https://www.lunasec.io/docs/blog/log4j-zero-day/
FEDORA-2021-f0f501d01f has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-f0f501d01f
FEDORA-2021-f0f501d01f has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-f0f501d01f` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-f0f501d01f See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
Don't we also need this for F34? It seems to be in the affected range of log4j versions.
@sergio - Please prepare build + release for Fedora 34 as well.
it is blocked by jansi https://src.fedoraproject.org/rpms/jansi/pull-request/10 I'm ok with intervention of a proven packager .
FEDORA-2021-f0f501d01f has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.
mizdebsk has a valid point, there; we should not need to make unsafe changes to jansi in order to address the bug in log4j. As he said, we either need to figure out a way to build 2.15.0 with the older jansi, or backport just the CVE fixes to log4j 2.13.3. Do you need help with this, Sergio? If so, it can be arranged...
Re-opening for F34.
FWIW it looks like the CentOS Stream 9 package is also 2.13.3 https://gitlab.com/redhat/centos-stream/rpms/log4j/-/tree/c9s; presumably there will be a backported patch for that landing soon which theoretically should apply.
Oh, no — CS9 package got retired before the release. So nope to that.
There are no plans to patch log4j package in CentOS Stream 9. It was removed in June on my request: https://issues.redhat.com/browse/CS-626
(In reply to Adam Williamson from comment #10) TLDR, I'm going orphan the log4j, I took log4j to avoid Javapocalypse and because it was one dependency of ant. Now just 2 packages depends on log4j . jericho-html (maintained by: terjeros) jericho-html-3.3-21.fc35.src requires log4j = 2.15.0-1.fc36 jglobus (maintained by: ellert) jglobus-2.1.0-24.fc36.src requires mvn(log4j:log4j) = 2.15.0, jglobus-ssl-proxies-2.1.0-24.fc36.noarch requires mvn(log4j:log4j) = 2.15.0
OK. I'm out right now. If nobody else has taken care of it when I get home I'll try and sort something out then.
Update: working on this now. I've backported the thing log4j needed to jansi 2.1.1 (I hope). With that we should be able to build log4j 2.16.0 with no breaking changes to jansi. I've just submitted the buildroot override for the jansi change, have a scratch build for log4j lined up, if that scratch build works I'll do an official build then submit an update for both packages.
FEDORA-2021-66d6c484f3 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2021-66d6c484f3
FEDORA-2021-66d6c484f3 has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-66d6c484f3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-66d6c484f3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-66d6c484f3 has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report.