Apache has announced a Log4J vulnerability in their software and updated there guidance this weekend. We are assessing the impact to production systems that we host, taking the necessary remediation, and will update them when the assessment is complete. As new information becomes available, we will post here. We have also posted some product specific KB articles that you can also refer to:
Signals Notebook: https://support.revvitysignals.com/hc/en-us/articles/4412842493844-Is-Signals-Notebook-affected-by-the-recent-Apache-Log4J-vulnerability-
E-notebook Enterprise and ChemBioOffice Enterprise: https://support.revvitysignals.com/hc/en-us/articles/4413183545108-E-Notebook-Enterprise-and-ChemBioOffice-Enterprise-LOG4J-Vulnerability
EN Data Extractor: https://support.revvitysignals.com/hc/en-us/articles/4413189882132-EN-Data-and-Log4J-Vulnerability
Tibco Spotfire: https://support.revvitysignals.com/hc/en-us/articles/4412821488532-How-to-address-the-Apache-Log4J-vulnerability-in-TIBCO-Spotfire-Server
Signals Inventa, Signals Lead Discovery, Lead Discovery and Lead Discovery Premium: https://support.revvitysignals.com/hc/en-us/articles/4412926954644-Signals-Inventa-Signals-Lead-Discovery-Lead-Discovery-Lead-Discovery-Premium-and-Apache-Log4J-Vulnerability
Signals VitroVivo and Signals Screening: Signals Vitro Vivo and Signals Screening Log4J vulnerability
Signals Image Artist: Is Signals Image Artist (SImA) susceptible to the Log4j vulnerability?
Columbus: Is Columbus susceptible to the Log4j vulnerability?
We will update this announcement and our KB articles as new information becomes available, but please know that we are taking this on as a top priority for all of our products.