INKY incident

Inky systems not exposed to log4j

Notice Resolved View vendor source →

INKY experienced a notice incident on December 15, 2021 affecting Dashboard Services US and Dashboard Services EU, lasting 21d 2h. The incident has been resolved; the full update timeline is below.

Started
Dec 15, 2021, 01:38 PM UTC
Resolved
Jan 05, 2022, 04:22 PM UTC
Duration
21d 2h
Detected by Pingoru
Dec 15, 2021, 01:38 PM UTC

Affected components

Dashboard Services USDashboard Services EU

Update timeline

  1. monitoring Dec 15, 2021, 01:38 PM UTC

    Inky systems are not affected by the recently discovered log4j vulnerability. Late last week an announcement was made of a vulnerability in the ubiquitous log4j library in Java. Inky began investigation and testing for evidence of systems vulnerable to the log4j bug. We have been able to determine that none of the Java components that we utilize have exposure to the log4j vulnerability. We have updated and or disabled the log4j components on all backend systems to ensure no future changes could lead to an exposure.

  2. resolved Jan 05, 2022, 04:22 PM UTC

    This incident has been resolved.