Red Hat OpenShift 4.6
Red Hat OpenShift 4.6
The Red Hat OpenShift 4.6 reached end of service life on Oct 27, 2022 — Red Hat OpenShift no longer ships security patches or fixes for it. Our third-party support keeps it safe to run: 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance.
24/7 engineers own your Red Hat OpenShift 4.6 incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- red-hat-openshift
- release
- 4.6
- product Label
- Red Hat OpenShift
- release Label
- 4.6
- codename
- lts
- latest Version
- 4.6.62
- release Date
- 2020-11-09
- maintained
- source Url
- https://endoflife.date/red-hat-openshift
Lifecycle Dates
- End of Service Life
- Oct 27, 2022
- Last OEM Support
- Mar 24, 2021
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Red Hat OpenShift 4.6 — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Red Hat OpenShift 4.6?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Red Hat OpenShift 4.6 when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Red Hat OpenShift 4.6 Support: Frequently Asked Questions
Is the Red Hat OpenShift 4.6 still supported?
Red Hat OpenShift ended support for the Red Hat OpenShift 4.6 on Oct 27, 2022 — no more patches or fixes from the vendor. Third-party support keeps it covered: our engineers manage issues, remediate vulnerabilities, and help you maintain compliance for as long as you run it.
When is the Red Hat OpenShift 4.6 end of service life (EOSL) date?
Red Hat OpenShift lists the end of service life for the Red Hat OpenShift 4.6 as Oct 27, 2022.
Can I keep using the Red Hat OpenShift 4.6 after its EOSL date?
Yes. EOSL means Red Hat OpenShift stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Red Hat OpenShift 4.6 cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Red Hat OpenShift 4.6
10 published CVEs affect the Red Hat OpenShift 4.6, including 6 rated critical or high severity. Red Hat OpenShift no longer ships security patches for this release — our engineers provide mitigation guidance, workarounds and hardening support.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2013-4561 | CRITICAL | 9.1 | Jun 30, 2022 | In a openshift node, there is a cron job to update mcollective facts that mishandles a temporary file. This may lead to loss of confidentiality and integrity. |
| CVE-2021-4125 | HIGH | 8.1 | Aug 24, 2022 | 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. |
| CVE-2014-0023 | HIGH | 7.8 | Nov 15, 2019 | OpenShift: Install script has temporary file creation vulnerability which can result in arbitrary code execution |
| CVE-2023-44487 | HIGH | 7.5 | Oct 10, 2023 | The HTTP/2 protocol allows a denial of service (server resource consumption) because request cancellation can reset many streams quickly, as exploited in the wild in August through October 2023. |
| CVE-2013-0165 | HIGH | 7.3 | Nov 1, 2019 | cartridges/openshift-origin-cartridge-mongodb-2.2/info/bin/dump.sh in OpenShift does not properly create files in /tmp. |
| CVE-2020-35514 | HIGH | 7.0 | Jun 2, 2021 | An insecure modification flaw in the /etc/kubernetes/kubeconfig file was found in OpenShift. This flaw allows an attacker with access to a running container which mounts /etc/kubernetes or has local access to the node, to copy this kubeconfig file and attempt to add their own node to the OpenShift cluster. The highest threat from this vulnerability is to confidentiality, integrity, as well as system availability. This flaw affects versions before openshift4/ose-machine-config-operator v4.7.0-202 |
| CVE-2018-1257 | MEDIUM | 6.5 | May 11, 2018 | Spring Framework, versions 5.0.x prior to 5.0.6, versions 4.3.x prior to 4.3.17, and older unsupported versions allows applications to expose STOMP over WebSocket endpoints with a simple, in-memory STOMP broker through the spring-messaging module. A malicious user (or attacker) can craft a message to the broker that can lead to a regular expression, denial of service attack. |
| CVE-2021-3636 | MEDIUM | 4.6 | Jul 30, 2021 | It was found in OpenShift, before version 4.8, that the generated certificate for the in-cluster Service CA, incorrectly included additional certificates. The Service CA is automatically mounted into all pods, allowing them to safely connect to trusted in-cluster services that present certificates signed by the trusted Service CA. The incorrect inclusion of additional CAs in this certificate would allow an attacker that compromises any of the additional CAs to masquerade as a trusted in-cluster |
| CVE-2019-6648 | MEDIUM | 4.4 | Sep 4, 2019 | On version 1.9.0, If DEBUG logging is enable, F5 Container Ingress Service (CIS) for Kubernetes and Red Hat OpenShift (k8s-bigip-ctlr) log files may contain BIG-IP secrets such as SSL Private Keys and Private key Passphrases as provided as inputs by an AS3 Declaration. |
| CVE-2017-15137 | MEDIUM | 4.3 | Jul 16, 2018 | The OpenShift image import whitelist failed to enforce restrictions correctly when running commands such as "oc tag", for example. This could allow a user with access to OpenShift to run images from registries that should not be allowed. |