Details
-
Bug
-
Status: Closed (View Workflow)
-
TBD
-
Resolution: Done
-
2.3.0
-
CP: sprint 129
-
1
-
Core: Platform
Description
mvn dependency:tree -Dincludes=*log4j* -Dverbose [INFO] org.folio:mod-login-saml:jar:2.4.0-SNAPSHOT [INFO] \- org.folio:domain-models-runtime:jar:33.1.1:compile [INFO] +- org.folio:cql2pgjson:jar:33.1.1:compile [INFO] | \- org.folio:dbschema:jar:33.1.1:compile [INFO] | \- org.folio.okapi:okapi-common:jar:4.9.0:compile [INFO] | \- (org.apache.logging.log4j:log4j-api:jar:2.13.3:compile - omitted for duplicate) [INFO] +- org.apache.logging.log4j:log4j-core:jar:2.13.3:compile [INFO] | \- (org.apache.logging.log4j:log4j-api:jar:2.13.3:compile - omitted for duplicate) [INFO] \- org.apache.logging.log4j:log4j-api:jar:2.13.3:compile
mod-login-saml is affected. It gets its log4j dependency via domain-models-runtime.
TestRail: Results
Attachments
Issue Links
- defines
-
FOLIO-3364 Update everything to log4j >= 2.16.0 fixing remote execution (CVE-2021-44228)
-
- Closed
-
- is blocked by
-
RMB-888 Log4j 2.15.0 fixing remote execution (CVE-2021-44228)
-
- Closed
-