Skip to main content

Advisory: Analysis of the Log4j Vulnerability CVE-2021-44228

15 December 2021

Introduction

As described in NIST vulnerability report CVE-2021-44228, certain versions of Log4j contain a CRITICAL security vulnerability.

Log4j is a widely used logging framework for Java applications. Fortunately, the Ed-Fi product portfolio has very little Java code in it. Many of Ed-Fi's .NET Framework-based applications use log4net, which was originally based on Log4j. However, NIST confirms that log4net is not impacted:

"Note that this vulnerability is specific to log4j-core and does not affect log4net, log4cxx, or other Apache Logging Services projects."

Vulnerability Assessment

Core Ed-Fi Products

None of these products is subject to the Log4j vulnerability.

Ed-Fi AssetMain LanguageUses Log4j
ODS / API Platform, Suite 2 and Suite 3C#No
MetaEd IDEJavaScriptNo
MappingEDUAngularJS + C# .NETNo
Sample Data GeneratorC#No
Analytics Middle TierT-SQLNo
Admin AppC#No
Data ImportC#No
LMS ToolkitPythonNo
Learning Standards Sync UtilityC#No
Docker DeploymentDockerNo
Migration UtilityC#No
Tech Suite InstallerInstallShieldNo

Ed-Fi Exchange Contributions

After a manual scan through the solutions posted to the Ed-Fi Exchange, one was found that is potentially vulnerable: Chronic Absenteeism Quick Start (Metabase).

Metabase is a business intelligence tool built on Java, and it does use Log4j. Metabase has published their own security advisoryon this with information on how to upgrade or work around the problem. The maintainer of this Exchange contribution has been notified of the need to upgrade.

info

The following is community-sourced information. The Ed-Fi Alliance does not directly support these products and does not make any guarantees about the accuracy of the statements below or the stated claims for security. The following is provided for informational purposes only and is not to be relied upon in lieu of direct and independent analysis.

AssetProgramming LanguageUses Log4j
Swagger Code Generation Tool (for SDK auto-generation)Java​Yes. SmartBear is researching the impact on their tools. Ed-Fi's analysis: unlikely to be a problem, since this is a command-line tool that does not operate over the Internet.
TeamCityJavaYes. JetBrains states that TeamCity is safe from this attack. However, this might not apply to all plugins (see below).
Octopus Deploy.NETWhile Octopus Deploy itself does not use Log4j, the Octopus Deploy plugin for TeamCity does use it. Please see this advisoryfor more information on mitigating this attack vector.