CVE-2013-0266 (published 2013-03-08T21:55Z)

manifests/base.pp in the puppetlabs-cinder module, as used in PackStack, uses world-readable permissions for the (1) cinder.conf and (2) api-paste.ini configuration files, which allows local users to read OpenStack administrative passwords by reading the files.

Severity: LOW
CVSS v2 base score: 2.1 (AV:L/AC:L/Au:N/C:P/I:N/A:N)

Weakness information:
cwe_id: CWE-362
cwe_name: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
description: The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.
extended_description: 
            This can have security implications when the expected synchronization is in security-critical code, such as recording whether a user is authenticated or modifying important state information that should not be influenced by an outsider.
            A race condition occurs within concurrent environments, and is effectively a property of a code sequence. Depending on the context, a code sequence may be in the form of a function call, a small number of instructions, a series of program invocations, etc.
            A race condition violates these properties, which are closely related:
               
                  Exclusivity - the code sequence is given exclusive access to the shared resource, i.e., no other code sequence can modify properties of the shared resource before the original sequence has completed execution.
                  Atomicity - the code sequence is behaviorally atomic, i.e., no other thread or process can concurrently execute the same sequence of instructions (or a subset) against the same resource.
               
            A race condition exists when an "interfering code sequence" can still access the shared resource, violating exclusivity. Programmers may assume that certain code sequences execute too quickly to be affected by an interfering code sequence; when they are not, this violates atomicity. For example, the single "x++" statement may appear atomic at the code layer, but it is actually non-atomic at the instruction layer, since it involves a read (the original value of x), followed by a computation (x+1), followed by a write (save the result to x).
            The interfering code sequence could be "trusted" or "untrusted." A trusted interfering code sequence occurs within the product; it cannot be modified by the attacker, and it can only be invoked indirectly. An untrusted interfering code sequence can be authored directly by the attacker, and typically it is external to the vulnerable product.
         
         

Fix information:
repo_url: https://github.com/puppetlabs/puppetlabs-cinder
commit_details: repo_url: https://github.com/puppetlabs/puppetlabs-cinder
author: Ryan Coleman
author_date: 2013-02-07 13:42:38-08:00
msg: Restrict permissions on cinder configuration

Prior to this commit, the puppetlabs-cinder module applied the mode
0644 to the File[$::cinder::params::cinder_conf] resource which
were too permissive. This commit explicitly sets the mode to 0600.
repository: repo_url: https://github.com/puppetlabs/puppetlabs-cinder
repo_name: openstack/puppet-cinder
description: OpenStack Cinder Puppet Module. Mirror of code maintained at opendev.org.
repo_language: Puppet
owner: puppetlabs
file_changes: filename: base.pp
change_type: ModificationType.MODIFY
diff: @@ -32,7 +32,10 @@ class cinder::base (
     require => Package[$::cinder::params::package_name],
   }
 
-  file { $::cinder::params::cinder_conf: }
+  file { $::cinder::params::cinder_conf:
+    mode => '0600',
+  }
+
   file { $::cinder::params::cinder_paste_api_ini: }
 
   # Temporary fixes

programming_language: Perl