Redhat OpenShift Container Platform 4.7
Approved changes feed: RSS · Atom
cpe:2.3:a:redhat:openshift_container_platform:4.7:*:*:*:*:*:*:*
part: a version: 4.7 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.597638 |
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2022-1677 |
vulnerable | 2026-06-08 05:39:13.683062 |
Details available
In OpenShift Container Platform, a user with permissions to create or modify Routes can craft a payload that inserts a malformed entry into one of the cluster router's HAProxy configuration files. This malformed entry can match any arbitrary hostname, or all hostnames in the cluster, and direct traffic to an arbitrary application within the cluster, including one under attacker control.
Published: 2022-09-01T19:51:43.000Z
Updated: 2024-08-03T00:10:03.820Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-4104 |
vulnerable | 2026-06-08 05:38:08.359004 |
Deserialization of untrusted data in JMSAppender in Apache Log4j 1.2
JMSAppender in Log4j 1.2 is vulnerable to deserialization of untrusted data when the attacker has write access to the Log4j configuration. The attacker can provide TopicBindingName and TopicConnectionFactoryBindingName configurations causing JMSAppender to perform JNDI requests that result in remote code execution in a similar fashion to CVE-2021-44228. Note this issue only affects Log4j 1.2 when specifically configured to use JMSAppender, which is not the default. Apache Log4j 1.2 reached end of life in August 2015. Users should upgrade to Log4j 2 as it addresses numerous other issues from the previous versions.
Published: 2021-12-14T00:00:00.000Z
Updated: 2026-05-28T19:53:14.378Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3669 |
vulnerable | 2026-06-08 05:33:53.374073 |
Details available
A flaw was found in the Linux kernel. Measuring usage of the shared memory does not scale with large shared memory segment counts which could lead to resource exhaustion and DoS.
Published: 2022-08-26T15:25:40.000Z
Updated: 2025-11-03T21:44:59.899Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3609 |
vulnerable | 2026-06-08 05:33:53.094686 |
Details available
.A flaw was found in the CAN BCM networking protocol in the Linux kernel, where a local attacker can abuse a flaw in the CAN subsystem to corrupt memory, crash the system or escalate privileges. This race condition in net/can/bcm.c in the Linux kernel allows for local privilege escalation to root.
Published: 2022-03-03T18:24:59.000Z
Updated: 2024-08-03T17:01:07.458Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2021-3560 |
vulnerable | 2026-06-08 05:33:52.792709 |
Details available
It was found that polkit could be tricked into bypassing the credential checks for D-Bus requests, elevating the privileges of the requestor to the root user. This flaw could be used by an unprivileged local attacker to, for example, create a new local administrator. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Published: 2022-02-16T00:00:00.000Z
Updated: 2025-10-21T23:15:46.259Z Reference links |
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.