Skip to content
Noroxi
CVE-2011-3872· NVD / CVE Program· CNA mitre

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 ce

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

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

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help
Published
Oct 27, 2011
Updated
Jun 16, 2026
EPSS
2.5% · 84th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

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%

Affected systems

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
  • 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

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 to
    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 3.1.1
    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 query
    35Monitor
  • CVE-2018-6513Puppet Enterprise 2016.4.x prior to 2016.4.12, Puppet Enterprise 2017.3.x prior to 2017.3.7, Puppet Enterprise 2018.1.x prior to 2018.1.1, P
    35Monitor
  • CVE-2017-2295Versions of Puppet prior to 4.10.1 will deserialize data off the wire (from the agent to the server, in this case) with a attacker-specified
    33Monitor
  • CVE-2018-6515Puppet Agent 1.10.x prior to 1.10.13, Puppet Agent 5.3.x prior to 5.3.7, and Puppet Agent 5.5.x prior to 5.5.2 on Windows only, with a speci
    31Monitor

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. TodaySep 30, 2026+5452 d
EPSS, last 120 days

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.

Finders, 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

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records