CVE Intelligence

OpenStack Folsom vulnerabilities

🔔 Create alert RSS Version checker

Published CVEs affecting OpenStack Folsom: 4 record(s), with affected versions and fixes.
cpe:2.3:a:openstack:folsom

CVE-2013-0266 Medium · 5.5 CWE-276 Mar 8, 2013
manifests/base.pp in the puppetlabs-cinder module, as used in PackStack, uses world-readable...
A flaw was found in the `puppetlabs-cinder` module, as used in PackStack. This vulnerability is due to incorrect file permissions, specifically world-readable permissions, on the `cinder.conf` and `api-paste.ini` configuration files. A local user can exploit this by reading these files, which leads to the disclosure of OpenStack administrative passwords. This information disclosure could allow unauthorized access to sensitive OpenStack resources.
CVE-2013-0261 High · 8.8 CWE-59 Mar 8, 2013
Packstack: packstack: arbitrary file overwrite via symlink attack
A flaw was found in PackStack. A local user could exploit a symlink attack on a temporary file with a predictable name in the `/tmp` directory. This vulnerability allows the local user to overwrite arbitrary files on the system, potentially leading to system compromise or data corruption.
CVE-2012-5625 Medium · 6.5 CWE-212 Dec 26, 2012
Openstack nova: information leak in libvirt lvm-backed instances
OpenStack Compute (Nova) Folsom before 2012.2.2 and Grizzly, when using libvirt and LVM backed instances, does not properly clear physical volume (PV) content when reallocating for instances, which allows attackers to obtain sensitive information by reading the memory of the previous logical volume (LV).
CVE-2012-5571 Medium · 5.4 CWE-639 Dec 17, 2012
Openstack keystone: openstack keystone: authorization bypass via improper ec2 token handling
A flaw was found in OpenStack Keystone. This vulnerability allows remote authenticated users to bypass intended authorization restrictions. This occurs because OpenStack Keystone does not properly handle EC2 (Elastic Compute Cloud) tokens when a user's role has been removed from a tenant. An attacker can leverage a token associated with a removed user role to gain unauthorized access.