CVE-2009-3564: Medium severity puppet vulnerability

Published Dec 8, 2008
·
Updated

Description of problem: I noticed that puppetmasterd does not initialize its supplementary groups, which may lead to allow puppetmasterd to access files, it should not. E.g. if it is started with "service puppetmaster start", it still has access to all files that allow read access for the supplementary groups of root, e.g. raw disk devices.

I filed an upstream bug report including patches (one needs still to be tested) here: http://projects.reductivelabs.com/issues/show/1806

Version-Release number of selected component (if applicable): puppet-0.24.6-1.fc10 puupet-0.24.6-1.el5

How reproducible: always

Steps to Reproduce: 1. # service puppetmaster start 2. # cat /proc/$(ps --User puppet -o pid | tail -n 1)/status | grep Group Actual results: The output matches "id -G root".

Expected results: The output should match "id -G puppet", i.e. the process should run with the supplementary groups of puppet.

The default supplementary groups of root include the group disk, which e.g. provides raw read access on disk devices.

Additional info: I am not sure, whether this really classifies as a security vulnerability, because https://fedoraproject.org/wiki/Security/Classifications only mentions code execution and denial of service, but imho unwanted access to restricted information is a security vulnerability, too.

Other sources

puppetmasterd in puppet 0.24.6 does not reset supplementary groups when it switches to a different user, which might allow local users to access restricted files.

Affected Software

6 affected componentsFixes available
redhat/0.24.8<4.el4
4.el4
All of the following
reductivelabs puppet=0.24.6
Fedoraproject Fedora
reductivelabs puppet=0.24.6
CentOS CentOS
Fedoraproject Fedora

Event History

Dec 8, 2008
CVE Published
via Red Hat·12:00 AM
Data Sourced
via Red Hat·12:00 AM
RemedyDescriptionSeverity
Oct 6, 2009
CVE Published
via MITRE·05:22 PM
Data Sourced
via MITRE·05:22 PM
Description
Data Sourced
05:30 PM
DescriptionWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2009-3564?

CVE-2009-3564 has a moderate severity rating due to the potential for local users to access restricted files.

2

How do I fix CVE-2009-3564?

To fix CVE-2009-3564, upgrade Puppet to version 0.24.8 or later.

3

What versions are affected by CVE-2009-3564?

CVE-2009-3564 affects Puppet version 0.24.6 specifically.

4

Is there any workaround for CVE-2009-3564?

There are no documented workarounds for CVE-2009-3564; upgrading is recommended.

5

Who is impacted by CVE-2009-3564?

Local users on systems running Puppet 0.24.6 may be impacted by CVE-2009-3564.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203