Reload4j
 | This article has multiple issues. Please help improve it or discuss these issues on the talk page. (Learn how and when to remove these messages)
|
 |
Reload4j [1] was created by the original author of log4j 1.x, Ceki Gülcü. Reload4j is a fork of log4j version 1.2.17. It preserves the same java package name space, in this case org.apache.log4j. However, for reasons of trademark protection, it is published under the "ch.qos.reload4j" groupId[2] in Apache Maven Central. It can be thus considered as a drop-in replacement for log4j.
The aim of the reload4j project is to provide a migration path to those users wishing to correct log4j 1.x security issues.[3] For many companies this is a requirement by the FTC.[4] Upgrading to a newer version of log4j 1.x is not possible since the project has been declared EOL [5] by the Apache Software Foundation. This decision was reaffirmed in 2022[6] and could not be rescinded despite the best efforts of several volunteers.[7][8][9] Moreover, log4j 2.x has a considerably different API and configuration style. While some users see the benefit, the pertinence of reload4j and the necessity of a fork is subject of debate.[10]
Corrected Common Vulnerabilities and Exposures (CVE)
Reload4j fixes the following vulnerabilities:
- CVE-2021-4104[11]
- CVE-2019-17571[12]
- CVE-2022-23302
- CVE-2020-9493 aka CVE-2022-23307
- CVE-2020-9488
- XML entity injection attacks
Contrary to log4j 2.x, log4j 1.x and reload4j do not suffer from the notorious log4shell vulnerability.
First release and features
Version 1.2.18.0 of reload4j was released on January the 12th, 2022 and is available for public consumption.[13]
Reload4j 1.2.18 does not add any new features with respect to log4j 1.2.17 although future versions are likely to provide backward compatible performance improvements.
slf4j-reload4j module
Subsequent to the first release of reload4j, the SLF4J project has released SLF4J version 1.7.33[14] with direct support for reload4j via the slf4j-reload4j module.[15]
As of version 1.7.35, SLF4J slf4j-log4j12 was replaced by slf4j-reload4j. By virtue of Maven relocation attribute, references to slf4j-log4j12 of will be automatically redirected to use slf4j-reload4j.
References
- ^ "reload4j". reload4j.qos.ch. Retrieved 2022-01-14.
- ^ "Maven – Guide to Naming Conventions". maven.apache.org. Retrieved 2022-01-14.
- ^ "SLF4J". www.slf4j.org. Retrieved 2022-01-16.
- ^ "FTC warns companies to remediate Log4j security vulnerability". Federal Trade Commission. 2022-01-04. Retrieved 2022-01-14.
- ^ "Apache™ Logging Services™ Project Announces Log4j™ 1 End-Of-Life; Recommends Upgrade to Log4j 2". Apache Logging Services.
- ^ Ron, Grabowski (2022-01-06). "Log4j 1 End-of-Life Statement". lists.apache.org. Apache Logging Services.
{{cite web}}: CS1 maint: url-status (link) - ^ "Looking for a champion: resurrect log4j 1.x".
{{cite web}}: CS1 maint: url-status (link) - ^ "[DISCUSS][VOTE] Future of Log4j 1.x". lists.apache.org. Retrieved 2022-01-14.
{{cite web}}: CS1 maint: url-status (link) - ^ "standardizing the Maven build". lists.apache.org. Retrieved 2022-01-14.
{{cite web}}: CS1 maint: url-status (link) - ^ hugith (2022-01-17). "Reload4j. A drop-in replacement for log4j 1.2.17 (with the security issues fixed)". r/java. Retrieved 2022-01-17.
- ^ CVE.report; CVE. "CVE-2021-4104". CVE.report. Retrieved 2022-01-14.
- ^ CVE.report; CVE. "CVE-2019-17571". CVE.report. Retrieved 2022-01-14.
- ^ "Central Repository: ch/qos/reload4j/reload4j". repo.maven.apache.org. Retrieved 2022-01-14.
- ^ SLF4J.ORG (2022-01-13). "Release of version 1.7.33". SLF4J. SLF4J.ORG.
{{cite web}}: CS1 maint: numeric names: authors list (link) - ^ "Reload4jLoggerAdapter (SLF4J 2.0.0-alpha6 API)". www.slf4j.org. Retrieved 2022-01-14.
 | This redirect has not been added to any content categories. Please help out by adding categories to it so that it can be listed with similar redirects, in addition to a stub category. (January 2022) |
 | This computer-programming-related article is a stub. You can help Wikipedia by expanding it. |