github.com/quay/claircore@v1.5.28/rhel/rhcc/testdata/cve-2021-44228-ose-metering-hive.xml

<?xml version="1.0" encoding="utf-8"?>
<cvemap updated="2022-01-11T20:03:28" license="CC BY 4.0, https://creativecommons.org/licenses/by/4.0/">

<Vulnerability name="CVE-2021-44228">
    <ThreatSeverity>Critical</ThreatSeverity>
    <PublicDate>2021-12-10T02:01:00</PublicDate>
    <Bugzilla id="2030932" url="https://bugzilla.redhat.com/show_bug.cgi?id=2030932" xml:lang="en:us">
CVE-2021-44228 log4j-core: Remote code execution in Log4j 2.x when logs contain an attacker-controlled string value
    </Bugzilla>
    <CVSS3 status="verified">
        <CVSS3BaseScore>9.8</CVSS3BaseScore>
        <CVSS3ScoringVector>CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H</CVSS3ScoringVector>
    </CVSS3>
    <CWE>CWE-20</CWE>
    <Details source="Mitre" xml:lang="en:us">
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.
    </Details>
    <Details source="Red Hat" xml:lang="en:us">
A flaw was found in the Apache Log4j logging library in versions from 2.0.0 and before 2.15.0. A remote attacker who can control log messages or log message parameters, can execute arbitrary code on the server via JNDI LDAP endpoint.
    </Details>
    <Statement xml:lang="en:us">
This issue only affects log4j versions between 2.0  and 2.14.1. In order to exploit this flaw you need:
- A remotely accessible endpoint with any protocol (HTTP, TCP, etc) that allows an attacker to send arbitrary data,
- A log statement in the endpoint that logs the attacker controlled data.

In Red Hat OpenShift Logging the vulnerable log4j library is shipped in the Elasticsearch components. Because Elasticsearch is not susceptible to remote code execution with this vulnerability due to use of the Java Security Manager and because access to these components is limited, the impact by this vulnerability is reduced to Moderate.

As per upstream applications using Log4j 1.x may be impacted by this flaw if their configuration uses JNDI. However, the risk is much lower. This flaw in Log4j 1.x is tracked via https://access.redhat.com/security/cve/CVE-2021-4104 and has been rated as having Moderate security impact.

The following products are NOT affected by this flaw and have been explicitly listed here for the benefit of our customers.
- Red Hat Enterprise Linux
- Red Hat Advanced Cluster Management for Kubernetes 
- Red Hat Advanced Cluster Security for Kubernetes
- Red Hat Ansible Automation Platform (Engine and Tower)
- Red Hat Certificate System
- Red Hat Directory Server
- Red Hat Identity Management
- Red Hat CloudForms 
- Red Hat Update Infrastructure
- Red Hat Satellite
- Red Hat Ceph Storage
- Red Hat Gluster Storage
- Red Hat OpenShift Data Foundation
- Red Hat OpenStack Platform
- Red Hat Virtualization
- Red Hat Single Sign-On
    </Statement>
    <Mitigation xml:lang="en:us">
For Log4j versions &gt;=2.10
set the system property log4j2.formatMsgNoLookups or the environment variable LOG4J_FORMAT_MSG_NO_LOOKUPS to true

For Log4j versions &gt;=2.7 and &lt;=2.14.1
all PatternLayout patterns can be modified to specify the message converter as %m{nolookups} instead of just %m

For Log4j versions &gt;=2.0-beta9 and &lt;=2.10.0
remove the JndiLookup class from the classpath. For example: 
```
zip -q -d log4j-core-*.jar org/apache/logging/log4j/core/lookup/JndiLookup.class
```

On OpenShift 4 and in OpenShift Logging, the above mitigation can be applied by following the steps in this article: https://access.redhat.com/solutions/6578421

On OpenShift 3.11, mitigation to the affected Elasticsearch component can be applied by following the steps in this article: https://access.redhat.com/solutions/6578441
    </Mitigation>
    <!-- <AffectedRelease cpe="cpe:/a:redhat:logging:5" impact="moderate">
        <ProductName>OpenShift Logging 5.0</ProductName>
        <ReleaseDate>2021-12-14T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5137">RHSA-2021:5137</Advisory>
        <Package name="openshift-logging/elasticsearch6-rhel8">openshift-logging/elasticsearch6-rhel8:v5.0.10-1</Package>
    </AffectedRelease>
    <AffectedRelease cpe="cpe:/a:redhat:logging:5.1::el8">
        <ProductName>OpenShift Logging 5.1</ProductName>
        <ReleaseDate>2021-12-14T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5128">RHSA-2021:5128</Advisory>
        <Package name="openshift-logging/elasticsearch6-rhel8">openshift-logging/elasticsearch6-rhel8:v6.8.1-67</Package>
    </AffectedRelease>
    <AffectedRelease cpe="cpe:/a:redhat:logging:5.2::el8">
        <ProductName>OpenShift Logging 5.2</ProductName>
        <ReleaseDate>2021-12-14T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5127">RHSA-2021:5127</Advisory>
        <Package name="openshift-logging/elasticsearch6-rhel8">openshift-logging/elasticsearch6-rhel8:v6.8.1-66</Package>
    </AffectedRelease>
    <AffectedRelease cpe="cpe:/a:redhat:logging:5.3::el8">
        <ProductName>OpenShift Logging 5.3</ProductName>
        <ReleaseDate>2021-12-14T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5129">RHSA-2021:5129</Advisory>
        <Package name="openshift-logging/elasticsearch6-rhel8">openshift-logging/elasticsearch6-rhel8:v6.8.1-65</Package>
    </AffectedRelease> -->
    <!-- <AffectedRelease cpe="cpe:/a:redhat:openshift:3.11" impact="moderate">
        <ProductName>Red Hat OpenShift Container Platform 3.11</ProductName>
        <ReleaseDate>2021-12-14T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5094">RHSA-2021:5094</Advisory>
        <Package name="openshift3/ose-logging-elasticsearch5">openshift3/ose-logging-elasticsearch5:v3.11.570-2.gd119820</Package>
    </AffectedRelease>
    <AffectedRelease cpe="cpe:/a:redhat:openshift:4" impact="moderate">
        <ProductName>Red Hat OpenShift Container Platform 4.6</ProductName>
        <ReleaseDate>2021-12-16T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5106">RHSA-2021:5106</Advisory>
        <Package name="openshift4/ose-logging-elasticsearch6">openshift4/ose-logging-elasticsearch6:v4.6.0-202112132021.p0.g2a13a81.assembly.stream</Package>
    </AffectedRelease> -->
    <AffectedRelease cpe="cpe:/a:redhat:openshift:4" impact="moderate">
        <ProductName>Red Hat OpenShift Container Platform 4.6</ProductName>
        <ReleaseDate>2021-12-16T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5106">RHSA-2021:5106</Advisory>
        <Package name="openshift4/ose-metering-hive">openshift4/ose-metering-hive:v4.6.0-202112140546.p0.g8b9da97.assembly.stream</Package>
    </AffectedRelease>
    <!-- <AffectedRelease cpe="cpe:/a:redhat:openshift:4">
        <ProductName>Red Hat OpenShift Container Platform 4.6</ProductName>
        <ReleaseDate>2021-12-16T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5141">RHSA-2021:5141</Advisory>
        <Package name="openshift4/ose-metering-presto">openshift4/ose-metering-presto:v4.6.0-202112150545.p0.g190688a.assembly.art3595</Package>
    </AffectedRelease> -->
    <AffectedRelease cpe="cpe:/a:redhat:openshift:4">
        <ProductName>Red Hat OpenShift Container Platform 4.7</ProductName>
        <ReleaseDate>2021-12-16T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5107">RHSA-2021:5107</Advisory>
        <Package name="openshift4/ose-metering-hive">openshift4/ose-metering-hive:v4.7.0-202112140553.p0.g091bb99.assembly.stream</Package>
    </AffectedRelease>
    <!-- <AffectedRelease cpe="cpe:/a:redhat:openshift:4">
        <ProductName>Red Hat OpenShift Container Platform 4.7</ProductName>
        <ReleaseDate>2021-12-16T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5107">RHSA-2021:5107</Advisory>
        <Package name="openshift4/ose-metering-presto">openshift4/ose-metering-presto:v4.7.0-202112150631.p0.gd502108.assembly.4.7.40</Package>
    </AffectedRelease> -->
    <AffectedRelease cpe="cpe:/a:redhat:openshift:4.8::el8">
        <ProductName>Red Hat OpenShift Container Platform 4.8</ProductName>
        <ReleaseDate>2021-12-14T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5108">RHSA-2021:5108</Advisory>
        <Package name="openshift4/ose-metering-hive">openshift4/ose-metering-hive:v4.8.0-202112132154.p0.g57dd03a.assembly.stream</Package>
    </AffectedRelease>
    <!-- <AffectedRelease cpe="cpe:/a:redhat:openshift:4.8::el8">
        <ProductName>Red Hat OpenShift Container Platform 4.8</ProductName>
        <ReleaseDate>2021-12-15T00:00:00</ReleaseDate>
        <Advisory type="RHSA" url="https://access.redhat.com/errata/RHSA-2021:5148">RHSA-2021:5148</Advisory>
        <Package name="openshift4/ose-metering-presto">openshift4/ose-metering-presto:v4.8.0-202112150431.p0.g4b934ae.assembly.art3599</Package>
    </AffectedRelease> -->
    <UpstreamFix>log4j 2.15.0</UpstreamFix>
    <References xml:lang="en:us">
https://github.com/advisories/GHSA-jfh8-c2jp-5v3q
https://logging.apache.org/log4j/2.x/security.html
https://www.lunasec.io/docs/blog/log4j-zero-day/
    </References>
    <CSAw>True</CSAw>
</Vulnerability>

</cvemap>