Hi Team, We have facing some log4j related vulnerability on our windows host for MS SQL Server 2017 / 2019.
I have check so many articles, but in that I have not found any proper solution for resolving that issue. We want some solution for updating the version of log4j to log4j 2.16 + or if it's not possible for windows host then what is the next approach for that ? Regards, Pritesh Sawant Software Engineer Ingram Micro India SSC Private. Limited G-2, Akruti Corporate Park, Kanjurmarg West. Email : pritesh.saw...@ingrammicro.com<mailto:pritesh.saw...@ingrammicro.com> Phone No. : +91 7208817149 [cid:image001.png@01D97ED3.DEF1AD40] ---------------------------- This e-mail is for the use of the intended recipient(s) only. If you have received in error, please notify the sender immediately and delete it. If you are not the intended recipient, you must not use, disclose or distribute this e-mail without the author prior permission. Ingram Micro checks outgoing mail and accepts no liability for any loss or damage caused by software viruses. ---------------------------- [Ingram_2818e5de]
