Update log4j version due to security vulnerability 75/126475/1
authorliamfallon <liam.fallon@est.tech>
Wed, 5 Jan 2022 12:46:27 +0000 (12:46 +0000)
committerliamfallon <liam.fallon@est.tech>
Wed, 5 Jan 2022 12:50:20 +0000 (12:50 +0000)
SECCOM has recommended going to log4j 2.17.1.

Issue-ID: POLICY-3862
Change-Id: I804307f46de9e9f270bbc81b079f8621d1bcba0e
Signed-off-by: liamfallon <liam.fallon@est.tech>
integration/pom.xml

index 101e1ed..c53cbd0 100644 (file)
@@ -2,7 +2,7 @@
   ============LICENSE_START=======================================================
    Copyright (C) 2018 Ericsson. All rights reserved.
    Modifications Copyright (C) 2018-2021 AT&T. All rights reserved.
-   Modifications Copyright (C) 2019-2021 Nordix Foundation.
+   Modifications Copyright (C) 2019-2022 Nordix Foundation.
    Modifications Copyright (C) 2020-2021 Bell Canada.
   ================================================================================
   Licensed under the Apache License, Version 2.0 (the "License");
             <dependency>
                 <groupId>org.apache.logging.log4j</groupId>
                 <artifactId>log4j-api</artifactId>
-                <version>2.16.0</version>
+                <version>2.17.1</version>
             </dependency>
             <dependency>
                 <groupId>org.apache.logging.log4j</groupId>