Red Hat OpenShift 4.11
Red Hat OpenShift 4.11
The Red Hat OpenShift 4.11 reached end of service life on Feb 10, 2024 — 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.11 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.11
- product Label
- Red Hat OpenShift
- release Label
- 4.11
- codename
- lts
- latest Version
- 4.11.59
- release Date
- 2022-08-10
- maintained
- source Url
- https://endoflife.date/red-hat-openshift
Lifecycle Dates
- End of Service Life
- Feb 10, 2024
- Last OEM Support
- Apr 17, 2023
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Red Hat OpenShift 4.11 — 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.11?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Red Hat OpenShift 4.11 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.11 Support: Frequently Asked Questions
Is the Red Hat OpenShift 4.11 still supported?
Red Hat OpenShift ended support for the Red Hat OpenShift 4.11 on Feb 10, 2024 — 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.11 end of service life (EOSL) date?
Red Hat OpenShift lists the end of service life for the Red Hat OpenShift 4.11 as Feb 10, 2024.
Can I keep using the Red Hat OpenShift 4.11 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.11 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.11
10 published CVEs affect the Red Hat OpenShift 4.11, including 4 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-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-2022-2403 | MEDIUM | 6.5 | Sep 1, 2022 | A credentials leak was found in the OpenShift Container Platform. The private key for the external cluster certificate was stored incorrectly in the oauth-serving-cert ConfigMaps, and accessible to any authenticated OpenShift user or service-account. A malicious user could exploit this flaw by reading the oauth-serving-cert ConfigMap in the openshift-config-managed namespace, compromising any web traffic secured using that certificate. |
| 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-2023-0229 | MEDIUM | 6.3 | Jan 26, 2023 | A flaw was found in github.com/openshift/apiserver-library-go, used in OpenShift 4.12 and 4.11, that contains an issue that can allow low-privileged users to set the seccomp profile for pods they control to "unconfined." By default, the seccomp profile used in the restricted-v2 Security Context Constraint (SCC) is "runtime/default," allowing users to disable seccomp for pods they can create and modify. |
| CVE-2023-0296 | MEDIUM | 5.3 | Jan 17, 2023 | The Birthday attack against 64-bit block ciphers flaw (CVE-2016-2183) was reported for the health checks port (9979) on etcd grpc-proxy component. Even though the CVE-2016-2183 has been fixed in the etcd components, to enable periodic health checks from kubelet, it was necessary to open up a new port (9979) on etcd grpc-proxy, hence this port might be considered as still vulnerable to the same type of vulnerability. The health checks on etcd grpc-proxy do not contain sensitive data (only metrics |
| 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. |