CVE-2021-44228Critical

Microsoft security update for CVE-2021-44228

Published
December 16, 2021
Last Modified
—

🔗 CVE IDs covered (1)

CVE-2021-44228 →

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2021-44228. This page also shows what EchelonGraph holds for CVE-2021-44228, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products15

  • Azure Application Insights Java SDK
  • Azure Arc-enabled Data Services
  • Azure Data Lake Store Java client SDK
  • Azure Data Lake Store Java tool
  • Azure Databricks
  • Azure DevOps
  • Azure DevOps Server
  • Azure Spring Cloud
  • Azure VMware Solution
  • Cosmos DB Kafka Connector
  • Events Hub Extension
  • Microsoft Defender for IoT
  • Minecraft Java Edition
  • SQL Server 2019 Big Data Clusters
  • Team Foundation Server

✅ Updates Microsoft lists: 6 updates

6 rows: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update—
—Security Update—
—Security Update—
—Security Update10.5.2
—Security Update1.18.1
—Security Update—

🧭 EchelonGraph on CVE-2021-44228

EchelonGraph score
10.0 CRITICAL
CISA KEV
Listed since December 10, 2021
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

Apache Log4j2 2.0-beta9 through 2.15.0 (excluding security releases 2.12.2, 2.12.3, and 2.3.1) JNDI features used in configuration, log messages, and parameters do not protect against attacker controlled LDAP and other JNDI related endpoints. An attacker who can control log messages or log message parameters can execute arbitrary code loaded from LDAP servers when message lookup substitution is enabled. From log4j 2.15.0, this behavior has been disabled by default. From version 2.16.0 (along with 2.12.2, 2.12.3, and 2.3.1), this functionality has been completely removed. Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects.

Published by Apache Software Foundation, the CVE Numbering Authority that assigned CVE-2021-44228, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (6)