Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2011-3872: Puppet 2.6.x before 2.6.12 and 2.7.x before 2.7.6, and Puppet Enterprise (PE) Users 1.0, 1.1, and 1.2 before 1.2.4, when signing an agent…

LowCVSS 2.6 · v2.0—Proof of concept Fix available

Noroxi assessment

Priority: Monitor (action score 11/100)

  • Public proof-of-concept code exists (GitHub); there is no record of exploitation in the wild.
  • Probability of exploitation in the next 30 days: 2.5% (FIRST EPSS); higher than 85.1% of all records.
  • Special conditions such as timing or configuration are required.
  • Fixed version: puppet (Debian:11) 2.7.6-1; puppet (Debian:5.0) 0.24.5-3+lenny2; puppet (Debian:6.0) 2.6.2-5+squeeze3.

Low priority for now. Upgrade to puppet (Debian:11) 2.7.6-1; puppet (Debian:5.0) 0.24.5-3+lenny2; puppet (Debian:6.0) 2.6.2-5+squeeze3 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 2.6.x before 2.6.12 and 2.7.x before 2.7.6, and Puppet Enterprise (PE) Users 1.0, 1.1, and 1.2 before 1.2.4, when signing an agent certificate, adds the Puppet master's certdnsnames values to the X.509 Subject Alternative Name field of the certificate, which allows remote attackers to spoof a Puppet master via a man-in-the-middle (MITM) attack against an agent that uses an alternate DNS name for the master, aka "AltNames Vulnerability."

Published
Oct 27, 2011
Updated
Jun 16, 2026
EPSS
2.5% · 85th percentile

Report tools

JSON

Action score

11

Monitor

Low priority for now.

CVSS
10 / 40 · 2.6 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.5%

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • Proof of concept exists, no weaponized module
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2011-3872

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for puppet records
Is your version affected? Check it

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 help

Affected 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.

VendorProduct
puppetpuppet
puppetpuppet enterprise
puppetlabspuppet
puppetlabspuppet enterprise users

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • puppet puppet2.6.0
  • puppet puppet2.6.1
  • puppet puppet2.6.10
  • puppet puppet2.6.11
  • puppet puppet2.6.2
  • puppet puppet2.6.3
  • puppet puppet2.6.4
  • puppet puppet2.6.5
+12 more rows
  • puppet puppet2.6.6
  • puppet puppet2.6.7
  • puppet puppet2.6.8
  • puppet puppet2.6.9
  • puppet puppet2.7.2
  • puppet puppet2.7.3
  • puppet puppet2.7.4
  • puppet puppet2.7.5
  • puppet puppet enterprise1.2.0
  • puppet puppet enterprise1.2.1
  • puppet puppet enterprise1.2.2
  • puppet puppet enterprise1.2.3

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:11puppetbefore 2.7.6-12.7.6-1
Debian:5.0puppetbefore 0.24.5-3+lenny20.24.5-3+lenny2
Debian:6.0puppetbefore 2.6.2-5+squeeze32.6.2-5+squeeze3

Same product

puppet: all records

Other 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…
    40Plan
  • 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…
    37Monitor
  • 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…
    35Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2011-3870Oct 27, 2011 · Puppet 2.7.x before 2.7.5, 2.6.x before 2.6.11, and 0.25.x allows local users to modify the permissions of arbitrary files via a symlink…
    25Monitor
  • ← EarlierCVE-2011-3871Oct 27, 2011 · Puppet 2.7.x before 2.7.5, 2.6.x before 2.6.11, and 0.25.x, when running in --edit mode, uses a predictable file name, which allows local…
    24Monitor
  • Later →CVE-2012-1053May 29, 2012 · The change_user method in the SUIDManager (lib/puppet/util/suidmanager.rb) in Puppet 2.6.x before 2.6.14 and 2.7.x before 2.7.11, and…
    27Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:puppet2.7.6-1 · Debian:11Package registry (OSV)

Exploit status

Proof of concept available

A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.

Evidence

  • Proof-of-concept repository on GitHub ×1

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Proof-of-concept repository on GitHubstars:52011-10-17

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.

  1. First PoC-11 d
  2. Published
  3. TodayNov 15, 2026+5498 d

Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
P · data or configuration can be modified
Availability
none
Attack complexity
High
Confidentiality impact
None
Integrity impact
P
Availability impact
None

Weakness class (CWE)

CWE-20 · Improper Input Validation

CVSS vector

AV:N/AC:H/Au:N/C:N/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.

References

Show all references (10 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records