Skip to content

1.9.1 - upgrade log4j api & logback
Compare
Choose a tag to compare
@DaspawnW DaspawnW released this 15 Dec 11:24
· 39 commits to master since this release
1.9.1
6d0c019
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

Upgrade for security reasons log4j & logback.

  • As only log4j api is used it's not affected by the log4shell. Various scanners (e.g. trivy) still mark log4j-api as vulnerabile even it it's not the case.
  • logback has also a vulnerability which not affects vault-crd as scan=true must be set but to be also safe upgrade for it.
Assets 2
Loading