Vulnerability Details : CVE-2021-4125
It was found that the original fix for log4j CVE-2021-44228 and CVE-2021-45046 in the OpenShift metering hive containers was incomplete, as not all JndiLookup.class files were removed. This CVE only applies to the OpenShift Metering hive container images, shipped in OpenShift 4.8, 4.7 and 4.6.
Vulnerability category: Input validation
Products affected by CVE-2021-4125
- cpe:2.3:a:redhat:openshift:*:*:*:*:*:*:*:*
- cpe:2.3:a:redhat:openshift:*:*:*:*:*:*:*:*
- cpe:2.3:a:redhat:openshift:*:*:*:*:*:*:*:*
Exploit prediction scoring system (EPSS) score for CVE-2021-4125
0.61%
Probability of exploitation activity in the next 30 days
EPSS Score History
~ 78 %
Percentile, the proportion of vulnerabilities that are scored at or less
CVSS scores for CVE-2021-4125
Base Score | Base Severity | CVSS Vector | Exploitability Score | Impact Score | Score Source | First Seen |
---|---|---|---|---|---|---|
8.1
|
HIGH | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
2.2
|
5.9
|
NIST |
CWE ids for CVE-2021-4125
-
The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.Assigned by: secalert@redhat.com (Secondary)
-
The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources.Assigned by: secalert@redhat.com (Secondary)
-
The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.Assigned by:
- nvd@nist.gov (Primary)
- secalert@redhat.com (Secondary)
References for CVE-2021-4125
-
https://bugzilla.redhat.com/show_bug.cgi?id=2033121
2033121 – (CVE-2021-4125) CVE-2021-4125 kube-reporting/hive: Incomplete fix for log4j CVE-2021-44228 and CVE-2021-45046Issue Tracking;Patch;Third Party Advisory
-
https://github.com/kube-reporting/hive/pull/73
[release-4.6] Dockerfile: Account for non-log4j-core-* JAR filenames by timflannagan · Pull Request #73 · kube-reporting/hive · GitHubThird Party Advisory
-
https://github.com/kube-reporting/hive/pull/72
[release-4.7] Dockerfile: Account for non-log4j-core-* JAR filenames by timflannagan · Pull Request #72 · kube-reporting/hive · GitHubThird Party Advisory
-
https://access.redhat.com/security/cve/CVE-2021-45046
CVE-2021-45046- Red Hat Customer PortalThird Party Advisory
-
https://access.redhat.com/security/cve/CVE-2021-44228
CVE-2021-44228- Red Hat Customer PortalThird Party Advisory
-
https://access.redhat.com/security/cve/CVE-2021-4125
CVE-2021-4125- Red Hat Customer PortalThird Party Advisory
-
https://github.com/kube-reporting/hive/pull/71
[release-4.8] Bug 2033124: Account for non-log4j-core-* JAR filenames by timflannagan · Pull Request #71 · kube-reporting/hive · GitHubThird Party Advisory
Jump to