Log4j Vulnerability

infotex and Log4j

We are keeping our Clients’ safety in mind.

To all infotex managed security service Clients:

On Friday December 10th, infotex became aware of a zero-day vulnerability in the Apache Log4j library that allows unauthenticated remote code execution. We began incident response and took steps to proactively disable potentially vulnerable applications until we could further determine if they were impacted by the vulnerability.

The applications we proactively disabled were:
– Microsoft Cloud App Security (MCAS) SIEM Agent, used for monitoring Microsoft 365 logs
– Elasticsearch, Logstash, and Kibana services, part of our SIEM 3 beta stack

We later determined that the MCAS SIEM Agent and Kibana were not impacted by the vulnerability however Elasticsearch and Logstash were. As such, the MCAS SIEM Agent has been re-enabled and we will be patching the Elastic Stack before re-enabling it on our systems.

We also implemented multiple IDS signatures that detect exploit attempts and automatically block the source addresses for all our managed service clients with IPS. That being said, due to varying attack techniques our signatures at this time may not provide fully comprehensive coverage (we are updating them as more threat intelligence becomes available).

Like many other vendors we recommend reviewing your own software installations for potentially vulnerable applications if you have not already (the second and third links below have good lists that are being continuously updated). Apply vendor security patches and/or implement mitigation strategies as soon as possible. Lastly, please contact our SOC team if you have any other questions or investigative requests.

Additional References:
– https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2021-44228
– https://www.techsolvency.com/story-so-far/cve-2021-44228-log4j-log4shell/#affected-products
– https://gist.github.com/SwitHak/b66db3a06c2955a9cb71a8718970c592