BigLeaf incident

A message about our response to the log4j vulnerability

Notice Resolved View vendor source →

BigLeaf experienced a notice incident on December 13, 2021 affecting Gateway Cluster: Ashburn, VA and Gateway Cluster: Atlanta, GA and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
Dec 13, 2021, 09:21 PM UTC
Resolved
Dec 13, 2021, 09:21 PM UTC
Duration
—
Detected by Pingoru
Dec 13, 2021, 09:21 PM UTC

Affected components

Gateway Cluster: Ashburn, VAGateway Cluster: Atlanta, GAGateway Cluster: Chicago, ILGateway Cluster: Dallas, TXGateway Cluster: Denver, COGateway Cluster: Los Angeles, CAGateway Cluster: New York, NYGateway Cluster: San Jose, CAGateway Cluster: Seattle, WAWeb Dashboard

Update timeline

  1. resolved Dec 13, 2021, 09:21 PM UTC

    As you may be aware due to widespread news coverage, there is a software vulnerability recently disclosed within the Java log4j library that is impacting many software solutions world-wide. On Friday we performed an in-depth review of all of the systems and software tools that we control. Since our use of Java is very limited, we had fairly low exposure. We identified a few internal tools for development and logging that were at risk, and have mitigated those risks. We now believe all systems and tools that we control are safe from exploitation of this vulnerability. We also use common third-party SaaS tools like Office365, so we are monitoring the situation with our third-party vendors and will respond if we become aware of any risks that need to be addressed. At this time we do not believe that any customer data or systems were exposed or were at risk from this log4j vulnerability. Please let us know if you have any questions - You can always reach our 24x7 support team at 888-244-3133. Thank you, Joel Mulkey | Founder and CEO Bigleaf Networks, Inc. www.bigleaf.net