Red Hat OpenShift Container Platform 4.12
Approved changes feed: RSS · Atom
cpe:2.3:a:redhat:openshift_container_platform:4.12:*:*:*:*:*:*:*
part: a version: 4.12 update: *
| Vendor | Redhat (e942785a-ca89-506e-bd99-50782639cde3) |
|---|---|
| Product | Openshift Container Platform (9ad0e47d-6be9-5586-9c65-14660705c34d) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from NVD CPE 2.0 feed |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
pkg:github/openshift/okd |
purl2cpe | 2026-06-01 10:12:53.578278 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2025-6021 |
vulnerable | 2026-06-08 07:43:14.041516 |
Libxml2: integer overflow in xmlbuildqname() leads to stack buffer overflow in libxml2
HIGH (7.5)
A flaw was found in libxml2's xmlBuildQName function, where integer overflows in buffer size calculations can lead to a stack-based buffer overflow. This issue can result in memory corruption or a denial of service when processing crafted input.
Published: 2025-06-12T12:49:16.157Z
Updated: 2026-06-30T10:40:18.068Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2025-13601 |
vulnerable | 2026-06-08 07:04:32.656238 |
Glib: integer overflow in in g_escape_uri_string()
HIGH (7.7)
A heap-based buffer overflow problem was found in glib through an incorrect calculation of buffer size in the g_escape_uri_string() function. If the string to escape contains a very large number of unacceptable characters (which would need escaping), the calculation of the length of the escaped string could overflow, leading to a potential write off the end of the newly allocated string.
Published: 2025-11-26T14:44:22.680Z
Updated: 2026-06-29T23:29:30.203Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9676 |
vulnerable | 2026-06-08 07:00:28.492630 |
Podman: buildah: cri-o: symlink traversal vulnerability in the containers/storage library can cause denial of service (dos)
MEDIUM (6.5)
A vulnerability was found in Podman, Buildah, and CRI-O. A symlink traversal vulnerability in the containers/storage library can cause Podman, Buildah, and CRI-O to hang and result in a denial of service via OOM kill when running a malicious image using an automatically assigned user namespace (`--userns=auto` in Podman and Buildah). The containers/storage library will read /etc/passwd inside the container, but does not properly validate if that file is a symlink, which can be used to cause the library to read an arbitrary file on the host.
Published: 2024-10-15T15:27:33.665Z
Updated: 2026-04-24T15:07:44.878Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-9341 |
vulnerable | 2026-06-08 07:00:27.149965 |
Podman: buildah: cri-o: fips crypto-policy directory mounting issue in containers/common go library
MEDIUM (5.4)
A flaw was found in Go. When FIPS mode is enabled on a system, container runtimes may incorrectly handle certain file paths due to improper validation in the containers/common Go library. This flaw allows an attacker to exploit symbolic links and trick the system into mounting sensitive host directories inside a container. This issue also allows attackers to access critical host files, bypassing the intended isolation between containers and the host system.
Published: 2024-10-01T18:52:00.686Z
Updated: 2026-03-19T17:19:44.851Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-8883 |
vulnerable | 2026-06-08 07:00:25.928709 |
Keycloak: vulnerable redirect uri validation results in open redirec
MEDIUM (6.1)
A misconfiguration flaw was found in Keycloak. This issue can allow an attacker to redirect users to an arbitrary URL if a 'Valid Redirect URI' is set to http://localhost or http://127.0.0.1, enabling sensitive information such as authorization codes to be exposed to the attacker, potentially leading to session hijacking.
Published: 2024-09-19T15:48:28.468Z
Updated: 2026-04-01T13:27:25.248Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-5154 |
vulnerable | 2026-06-08 06:56:15.026716 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-4629 |
vulnerable | 2026-06-08 06:50:18.322389 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1635 |
vulnerable | 2026-06-08 06:27:13.929727 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-1132 |
vulnerable | 2026-06-08 06:25:39.332852 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-12085 |
vulnerable | 2026-06-08 06:23:51.154599 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6563 |
vulnerable | 2026-06-08 06:21:54.901754 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6291 |
vulnerable | 2026-06-08 06:19:46.865289 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-6134 |
vulnerable | 2026-06-08 06:19:46.313790 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-5408 |
vulnerable | 2026-06-08 06:19:43.539724 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-4853 |
vulnerable | 2026-06-08 06:16:14.741311 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-4066 |
vulnerable | 2026-06-08 06:16:11.385779 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-4065 |
vulnerable | 2026-06-08 06:16:11.376646 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-3223 |
vulnerable | 2026-06-08 06:09:38.880860 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-2585 |
vulnerable | 2026-06-08 06:02:42.579605 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-2422 |
vulnerable | 2026-06-08 06:02:42.278738 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1260 |
vulnerable | 2026-06-08 05:52:34.290175 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-1108 |
vulnerable | 2026-06-08 05:52:33.887286 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2023-0056 |
vulnerable | 2026-06-08 05:52:04.181124 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-4361 |
vulnerable | 2026-06-08 05:51:37.340822 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2022-3466 |
vulnerable | 2026-06-08 05:48:21.128053 | db.gcve.eu details were skipped to keep the page responsive. | Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.