Update log4j version due to security vulnerability 84/126484/1
authorliamfallon <liam.fallon@est.tech>
Thu, 6 Jan 2022 09:59:36 +0000 (09:59 +0000)
committerliamfallon <liam.fallon@est.tech>
Thu, 6 Jan 2022 09:59:40 +0000 (09:59 +0000)
SECCOM has recommended going to log4j 2.17.1.

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

index c53cbd0..2bbb71a 100644 (file)
             <dependency>
                 <groupId>org.apache.logging.log4j</groupId>
                 <artifactId>log4j-to-slf4j</artifactId>
-                <version>2.16.0</version>
+                <version>2.17.1</version>
             </dependency>
 
             <!-- AAF Client -->