OpenStack Essex vulnerabilities
🔔 Create alert RSS Version checker
Published CVEs affecting OpenStack Essex: 4 record(s), with affected versions and fixes.cpe:2.3:a:openstack:essex
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-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.
CVE-2012-3426
Medium · 4.9
CWE-264 Jul 31, 2012
OpenStack Keystone token expiration issues
OpenStack Keystone before 2012.1.1, as used in OpenStack Folsom before Folsom-1 and OpenStack Essex, does not properly implement token expiration, which allows remote authenticated users to bypass intended authorization restrictions by (1) creating new tokens through token chaining, (2) leveraging possession of a token for a disabled user account, or (3) leveraging possession of a token for an account with a changed password.