Red Hat Openstack Platform 17.0

CPE Details

Red Hat Openstack Platform 17.0
17.0
2023-04-14
13h45 +00:00
2023-08-11
21h44 +00:00
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
Notifications manage

CPE Name: cpe:2.3:a:redhat:openstack_platform:17.0:*:*:*:*:*:*:*

Informations

Vendor

redhat

Product

openstack_platform

Version

17.0

Related CVE

Open and find in CVE List

CVE ID Published Description Score Severity
CVE-2024-7319 2024-08-02 20h36 +00:00 An incomplete fix for CVE-2023-1625 was found in openstack-heat. Sensitive information may possibly be disclosed through the OpenStack stack abandon command with the hidden feature set to True and the CVE-2023-1625 fix applied.
5
Medium
CVE-2023-1633 2023-09-24 00h09 +00:00 A credentials leak flaw was found in OpenStack Barbican. This flaw allows a local authenticated attacker to read the configuration file, gaining access to sensitive credentials.
6.6
Medium
CVE-2023-1636 2023-09-24 00h09 +00:00 A vulnerability was found in OpenStack Barbican containers. This vulnerability is only applicable to deployments that utilize an all-in-one configuration. Barbican containers share the same CGROUP, USER, and NET namespace with the host system and other OpenStack services. If any service is compromised, it could gain access to the data transmitted to and from Barbican.
6
Medium
CVE-2023-1625 2023-09-24 00h08 +00:00 An information leak was discovered in OpenStack heat. This issue could allow a remote, authenticated attacker to use the 'stack show' command to reveal parameters which are supposed to remain hidden. This has a low impact to the confidentiality, integrity, and availability of the system.
7.4
High
CVE-2023-1668 2023-04-09 22h00 +00:00 A flaw was found in openvswitch (OVS). When processing an IP packet with protocol 0, OVS will install the datapath flow without the action modifying the IP header. This issue results (for both kernel and userspace datapath) in installing a datapath flow matching all IP protocols (nw_proto is wildcarded) for this flow, but with an incorrect action, possibly causing incorrect handling of other IP packets with a != 0 IP protocol that matches this dp flow.
8.2
High