Hi Francisco, As far as I know, log4j 1x is not vulnerable if you don't use jmsappender configurations. So we should be good here.
On Wednesday, December 15, 2021, Francisco Herrera < [email protected]> wrote: > Hi just to ask if i need to worry about the latest discovered > vulnerability for the Log4j I saw Ctakes it's using an older version > log4j-1.2.17.jar > > let me know if I need to do any kind of upgrade > > > > *Francisco Herrera * > > AWS Solutions Architect & Sysadmin > > > > *Email*: [email protected] > > > > 1000 NW 57 > <https://www.google.com/maps/search/1000+NW+57?entry=gmail&source=g>th Ct, > STE 400 > Miami, FL 33126 > > > > *www.careoptimize.com > <https://binaries.templates.cdn.office.net/support/templates/en-us/www.careoptimize.com>* > > > > *[image: Title: Facebook - Description: Facebook icon]* > <https://www.facebook.com/careoptimize/> *[image: Title: instagram - > Description: instagram icon]* > <https://instagram.com/careoptimize?utm_medium=copy_link> *[image: > Title: linkedin - Description: linkedin icon]* > <https://www.linkedin.com/company/careoptimize> *[image: Title: Twitter > - Description: twitter icon]* <https://twitter.com/careoptimize_?lang=en> > > > > > -- Regards, Gandhi "The best way to find urself is to lose urself in the service of others !!!"
