Didomi incident

Apache Log4j2 vulnerability (CVE-2021-44228)

Notice Resolved View vendor source →

Didomi experienced a notice incident on December 14, 2021 affecting Console and Consents APIs and 1 more component, lasting —. The incident has been resolved; the full update timeline is below.

Started
Dec 14, 2021, 01:59 PM UTC
Resolved
Dec 14, 2021, 01:59 PM UTC
Duration
Detected by Pingoru
Dec 14, 2021, 01:59 PM UTC

Affected components

ConsoleConsents APIsPlatform APIMobile and CTV SDKs (Android and iOS)AnalyticsPreference CentersPrivacy Centers APIAWS cloudfrontCompliance ReportsWeb SDK (Desktop & Mobile)

Update timeline

  1. resolved Dec 14, 2021, 01:59 PM UTC

    On Dec 9th, 2021, the "log4j vulnerability" (https://www.f5.com/labs/articles/threat-intelligence/explaining-the-widespread-log4j-vulnerability) was disclosed that allows remote code execution on many common Java-based applications. Didomi mostly uses Node.js for our backend systems and, after conducting an audit, we have determined that we are not affected by this vulnerability. We are monitoring AWS' fixes on the topic (https://aws.amazon.com/security/security-bulletins/AWS-2021-006/) and most critical services that Didomi uses in production (EC2, S3, Cloudfront, etc.) have already been patched.