• 1

LogicMonitor collectors running vulnerable version of Log4j are affected by "Log4shell" CVE-2021-44228 vulnerability?


Umesh Parab
 Share

Question

Recommended Posts

  • 1
  • LogicMonitor Staff

Hey everyone, here's an official communication you can pass on to customers, clients, stakeholders, etc. about what's going on with LM and the Log4shell vulnerability:

https://www.logicmonitor.com/support/log4shell-security-vulnerability-cve-2021-44228

It goes over the details and how to confirm that your collectors are safe. We will update this document as things progress.

  • Like 1
Link to comment
Share on other sites

  • 0

Pls find the recent update:

 

At this time the Log4Shell mitigation has already been released to the LM platform and each Collector will have automatically updated its configuration file to incorporate the fix on Saturday, Dec 11th. Because each Collector restarts itself on a daily cadence, the updated configuration will automatically take effect on all Collectors no later than Sunday, Dec 12th.


No updates to the Collector software are required to enable the Log4Shell mitigation and no manual intervention is required.

Hope this helps!!!

  • Upvote 1
Link to comment
Share on other sites

  • 0
14 hours ago, Manish Arora said:

Pls find the recent update:

 

At this time the Log4Shell mitigation has already been released to the LM platform and each Collector will have automatically updated its configuration file to incorporate the fix on Saturday, Dec 11th. Because each Collector restarts itself on a daily cadence, the updated configuration will automatically take effect on all Collectors no later than Sunday, Dec 12th.


No updates to the Collector software are required to enable the Log4Shell mitigation and no manual intervention is required.

Hope this helps!!!

 

Hi Manish,

Where was that posted?

Link to comment
Share on other sites

  • 0

I spoke to our Customer Success Manager just now and they have provided me the following information, this doesn't seem to be posted anywhere but this came directly from our CSM and provides a little more information. Hope this helps!

LogicMonitor has evaluated our exposure to the Log4Shell vulnerability and determined that the LM SaaS platform is not affected. We are aware that some versions of the LM Collector include a defective version of log4j, but its architecture has been purposely designed to mitigate such vulnerabilities. 

However, out of an abundance of caution, we have developed a mitigation to the  Log4Shell exposure and automatically deployed the fix to all Collectors. Instead of updating the Collector software itself, we were able to address the issue by updating the Collector configuration files.

On Dec 11th, all Collectors automatically updated their configuration files to include a directive -Dlog4j2.formatMsgNoLookups=true which neutralizes the Log4Shell attack vector. Because Collectors restart themselves on a 24-hour cadence, the updated configuration will have been applied to each Collector by Dec 12th.
If you want to verify with positive confirmation, you can check your Collectors’ wrapper.conf, watchdog.conf, and websites.conf/services.conf files for the above configuration directive. Also, each Collector that has been updated will include a line in its event log indicating Watchdog restarted by AddLog4jPropertyForWatchdog health check script.

  • Like 2
Link to comment
Share on other sites

  • 0
Guest Stuart Weenig

Yes, the above pop up should have appeared the first time an administrator logged in after Saturday:

Quote

On Dec 9th, 2021, various cybersecurity organizations began reporting that a critical-severity vulnerability has been discovered in an application logging component known as “log4j” which is widely used in Java-based applications. 

LogicMonitor has evaluated our exposure to the Log4Shell vulnerability and determined that the LM SaaS platform is not affected. We are aware that some versions of the LM Collector include a defective version of log4j, but its architecture has been purposely designed to mitigate such vulnerabilities. However, out of an abundance of caution, we have developed a mitigation strategy for this vulnerability that will definitively prevent exposure. 

At this time the Log4Shell mitigation has already been released to the LM platform and each Collector will have automatically updated its configuration file to incorporate the fix on Saturday, Dec 11th. Because each Collector restarts itself on a daily cadence, the updated configuration will automatically take effect on all Collectors no later than Sunday, Dec 12th.

No updates to the Collector software are required to enable the Log4Shell mitigation and no manual intervention is required.

Please reach out to LogicMonitor Technical Support or your Customer Success Manager if you have any questions or concerns.

 

Link to comment
Share on other sites

  • 0

Is there something that LM will release more official that we can share with our clients. I've been asked many times today if we can delete these files or uninstall LM Collectors b/c these boxes are still turning up as still 'venerable' by this vulnerability scans. 

 

Link to comment
Share on other sites

  • 0
Guest Stuart Weenig

I believe this is the highest priority activity for us right now. It should drop soon; i believe the decision has been to remove it entirely since it's not being used anyway. I understood log4j to be included in the Collector but not actually used in any capacity. Most vulnerability scanners can detect whether or not log4j is present, but not if the vulnerability can actually be exploited. So while the current version of the Collector may show up as containing log4j, that doesn't necessarily mean that the vulnerability exists and can be exploited. To be clear, a new collector version will be the third method of protecting against any log4j exploitation on the Collectors. The second is the configuration change that was already pushed out; the first is the fact that log4j isn't actively used by any of the Collector components.

Link to comment
Share on other sites

  • 0
  • LogicMonitor Staff

GD 31.001 is now available in portals. It has log4j 2.16 to mitigate the log4shell vulnerabilities.

We'll continue to update our official communication as things progress: https://www.logicmonitor.com/support/log4shell-security-vulnerability-cve-2021-44228

Thanks for your patience!

  • Like 1
Link to comment
Share on other sites

  • 0

@Michael Rodrigues@Stuart Weenig

For info, Log4J 2.16 also have a exploitable vulnerability:

https://nvd.nist.gov/vuln/detail/CVE-2021-45105
https://logging.apache.org/log4j/2.x/security.html

We are upgrading all of our own enterprise products to use 2.17.  Will LogicMonitor be upgrading to 2.17?

Edited by Mosh
Added a link
  • Like 3
Link to comment
Share on other sites

  • 0
4 hours ago, Mosh said:

@Michael Rodrigues@Stuart Weenig

For info, Log4J 2.16 also have a exploitable vulnerability:

https://nvd.nist.gov/vuln/detail/CVE-2021-45105
https://logging.apache.org/log4j/2.x/security.html

We are upgrading all of our own enterprise products to use 2.17.  Will LogicMonitor be upgrading to 2.17?

2nd this. Though the vulnerability is less severe, does LogicMonitor plan to update to 2.17 given the high visibility of these vulnerabilities? If so, when can we expect an updated collector?

Thank you 

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share