diff options
| author | Florian Zschocke <f.zschocke+git@gmail.com> | 2023-10-31 19:07:35 +0100 |
|---|---|---|
| committer | Florian Zschocke <f.zschocke+git@gmail.com> | 2023-10-31 19:07:35 +0100 |
| commit | d2a3322b280c408184cfe8618375b47cef09657a (patch) | |
| tree | 4e1df96befe3845068d18b7c34b3e05e3d0c0b1c /HOME.md | |
| parent | f124dfca7f8ec97b1f28cb5d258d8ee5d1da9b30 (diff) | |
| download | gitblit-d2a3322b280c408184cfe8618375b47cef09657a.tar.gz gitblit-d2a3322b280c408184cfe8618375b47cef09657a.zip | |
dep: Update slf4j to 1.7.36 and switch from log4j1 to reload4j
Replace log4j 1.2.17 with reload4j 1.2.25.
log4j 1.x was caught in the fire of the Log4Shell vulnerability, even
though the 1.x line was not affected by the vulnerability. Still, this
looks bad when it shows up in security scanners even though it doesn't
mean it has the Log4Shell vulnerability.
Switch to reload4j instead. This is a drop-in replacement of log4j.
Actually, it is log4j rebooted by the same author. The reload4j 1.x
line fixes security issues that have since surfaced.
At the same time we update to the latest slf4j version, which also
switched to reload4j for the log4j12 line.
Diffstat (limited to 'HOME.md')
0 files changed, 0 insertions, 0 deletions