Skip to content
Noroxi
CVE-2012-3408· NVD / CVE Program· CNA redhat

lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames witho

lib/puppet/network/authstore.rb in Puppet before 2.7.18, and Puppet Enterprise before 2.5.2, supports use of IP addresses in certnames without warning of potential risks, which might allow remote attackers to spoof an agent by acquiring a previously used IP address.

LowCVSS 2.6 · v2.0—No exploit Fix available
Published
Aug 6, 2012
Updated
Jun 16, 2026
EPSS
1.6% · 75th 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

10

Monitor

Low priority for now.

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

Affected systems

VendorProduct
puppetpuppet enterprise
puppetlabspuppet

Affected versions

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

  • puppet puppet enterprisebefore 2.5.2
  • puppetlabs puppetbefore 2.7.18

Package-level exposure

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

EcosystemPackageAffected rangeFix
Debian:11puppetbefore 2.7.18-12.7.18-1
RubyGemspuppetbefore 2.7.182.7.18

Same product

puppet: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-5309Broken Session Management in Puppet Enterprise
    39Monitor
  • CVE-2023-2530A privilege escalation allowing remote code execution was discovered in the orchestration service.
    39Monitor
  • CVE-2019-10694The express install, which is the suggested way to install Puppet Enterprise, gives the user a URL at the end of the install to set the admi
    39Monitor
  • CVE-2018-11749When users are configured to use startTLS with RBAC LDAP, at login time, the user's credentials are sent via plaintext to the LDAP server.
    39Monitor
  • CVE-2016-5716The console in Puppet Enterprise 2015.x and 2016.x prior to 2016.4.0 includes unsafe string reads that potentially allows for remote code ex
    36Monitor
  • CVE-2015-7330Puppet Enterprise 2015.3 before 2015.3.1 allows remote attackers to bypass a host whitelist protection mechanism by leveraging the Puppet co
    36Monitor

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.18-1 · Debian:11Package registry (OSV)
RubyGems:puppet2.7.18Package 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.

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.

Credits

All researchers

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

Attack conditions

  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
P · data can be read
Integrity
none
Availability
none
Attack complexity
High
Confidentiality impact
P
Integrity impact
None
Availability impact
None

Weakness class (CWE)

CWE-287 · Improper Authentication

CVSS vector

AV:N/AC:H/Au:N/C:P/I:N/A:N

nvd-primary

Root cause

Authentication is added route by route instead of being enforced in one place. When a route added later bypasses the shared middleware, the session check never runs for it.

The bug in code

The whole CWE-287 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

ts
app.use("/admin", requireSession, adminRouter);
// Route added later skips the middlewareapp.post("/admin-api/config", updateConfig);

Fixed

ts
const admin = express.Router();admin.use(requireSession, requireRole("admin"));
admin.post("/config", updateConfig);app.use("/admin", admin);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; 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

Change log

  1. Fix✗ → ✓

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

References

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

All records