Puppet Module Tool (PMT), as used in Puppet 2.7.x before 2.7.23 and 3.2.x before 3.2.4, and Puppet Enterprise 2.8.x before 2.8.3 and 3.0.x b
Noroxi assessment
Priority: Monitor (action score 14/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.38% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: puppet (Debian:11) 3.2.4-1; puppet (Debian:7) 2.7.23-1~deb7u1; facter (Red Hat:openstack:3::el6) 0:1.6.6-1.el6_4.
Low priority for now. Upgrade to puppet (Debian:11) 3.2.4-1; puppet (Debian:7) 2.7.23-1~deb7u1; facter (Red Hat:openstack:3::el6) 0:1.6.6-1.el6_4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Puppet Module Tool (PMT), as used in Puppet 2.7.x before 2.7.23 and 3.2.x before 3.2.4, and Puppet Enterprise 2.8.x before 2.8.3 and 3.0.x before 3.0.1, installs modules with weak permissions if those permissions were used when the modules were originally built, which might allow local users to read or modify those modules depending on the original permissions.
- Published
- Aug 20, 2013
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 30th percentile
- CWE
- CWE-264
Report tools
Action score
14
Monitor
Low priority for now.
- CVSS
- 14 / 40 · 3.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| puppet | puppet | cpe:2.3:a:puppet:puppet |
| puppet | puppet enterprise | cpe:2.3:a:puppet:puppet_enterprise |
| puppetlabs | puppet | cpe:2.3:a:puppetlabs:puppet |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- puppet puppet2.7.10
- puppet puppet2.7.11
- puppet puppet2.7.12
- puppet puppet2.7.13
- puppet puppet2.7.14
- puppet puppet2.7.16
- puppet puppet2.7.17
- puppet puppet2.7.18
- puppet puppet2.7.2
- puppet puppet2.7.21
- puppet puppet2.7.22
- puppet puppet2.7.3
- puppet puppet2.7.4
- puppet puppet2.7.5
- puppet puppet2.7.6
- puppet puppet2.7.7
- puppet puppet2.7.8
- puppet puppet2.7.9
- puppet puppet3.2.1
- puppet puppet3.2.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:11 | puppet | before 3.2.4-1 | 3.2.4-1 |
| Debian:7 | puppet | before 2.7.23-1~deb7u1 | 2.7.23-1~deb7u1 |
| Red Hat:openstack:3::el6 | facter | before 0:1.6.6-1.el6_4 | 0:1.6.6-1.el6_4 |
| Red Hat:openstack:3::el6 | hiera | before 0:1.0.0-3.el6_4 | 0:1.0.0-3.el6_4 |
| Red Hat:openstack:3::el6 | puppet | before 0:3.2.4-1.el6_4 | 0:3.2.4-1.el6_4 |
| Red Hat:openstack:3::el6 | puppet-server | before 0:3.2.4-1.el6_4 | 0:3.2.4-1.el6_4 |
| Red Hat:openstack:3::el6 | ruby-augeas | before 0:0.4.1-1.el6_4 | 0:0.4.1-1.el6_4 |
| Red Hat:openstack:3::el6 | ruby-augeas-debuginfo | before 0:0.4.1-1.el6_4 | 0:0.4.1-1.el6_4 |
| Red Hat:openstack:3::el6 | ruby-shadow | before 0:1.4.1-13.el6_4 | 0:1.4.1-13.el6_4 |
| Red Hat:openstack:3::el6 | ruby-shadow-debuginfo | before 0:1.4.1-13.el6_4 | 0:1.4.1-13.el6_4 |
| Red Hat:openstack:3::el6 | ruby193-puppet | before 0:3.1.1-11.1.el6ost | 0:3.1.1-11.1.el6ost |
| Red Hat:openstack:3::el6 | ruby193-puppet-server | before 0:3.1.1-11.1.el6ost | 0:3.1.1-11.1.el6ost |
Same product
puppet: all recordsOther highest-scoring records for the same primary product.
- CVE-2016-2785Puppet Server before 2.3.2 and Ruby puppetmaster in Puppet 4.x before 4.4.2 and in Puppet Agent before 1.4.2 might allow remote attackers to40Plan
- CVE-2013-1640The (1) template and (2) inline_template functions in the master server in Puppet before 2.6.18, 2.7.x before 2.7.21, and 3.1.x before 3.1.137Monitor
- CVE-2021-27021A flaw was discovered in Puppet DB, this flaw results in an escalation of privileges which allows the user to delete tables via an SQL query35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2013-3567Aug 19, 2013 · Puppet 2.7.x before 2.7.22 and 3.2.x before 3.2.2, and Puppet Enterprise before 2.8.2, deserializes untrusted YAML, which allows remote atta31Monitor
- ← EarlierCVE-2013-4761Aug 20, 2013 · Unspecified vulnerability in Puppet 2.7.x before 2.7.23 and 3.2.x before 3.2.4, and Puppet Enterprise 2.8.x before 2.8.3 and 3.0.x before 3.20Monitor
- Later →CVE-2011-0528Feb 17, 2014 · Puppet 2.6.0 through 2.6.3 does not properly restrict access to node resources, which allows remote authenticated Puppet nodes to read or mo22Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:puppet | 3.2.4-1 · Debian:11 | Package registry (OSV) |
| red hat:facter | 0:1.6.6-1.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:hiera | 0:1.0.0-3.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:puppet | 0:3.2.4-1.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:puppet-server | 0:3.2.4-1.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:ruby-augeas | 0:0.4.1-1.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:ruby-augeas-debuginfo | 0:0.4.1-1.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:ruby-shadow | 0:1.4.1-13.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:ruby-shadow-debuginfo | 0:1.4.1-13.el6_4 · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:ruby193-puppet | 0:3.1.1-11.1.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
| red hat:ruby193-puppet-server | 0:3.1.1-11.1.el6ost · Red Hat:openstack:3::el6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- None
Weakness class (CWE)
CWE-264 · Permissions, Privileges, and Access ControlsCVSS vector
AV:L/AC:L/Au:N/C:P/I:P/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (3 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.