dbcve.org
StdlibApplication · Puppet

CVE-2015-1029

MEDIUM · 6.5 CVSS v2.0 Published 2015-01-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The puppetlabs-stdlib module 2.1 through 3.0 and 4.1.0 through 4.5.x before 4.5.1 for Puppet 2.8.8 and earlier allows remote authenticated users to gain privileges or obtain sensitive information by prepopulating the fact cache.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The puppetlabs-stdlib module versions 2.1-3.0 and 4.1.0-4.5.x for Puppet 2.8.8 and earlier contains a vulnerability where authenticated remote users can prepopulate the fact cache to elevate privileges or obtain sensitive information.

MitigationUpgrade puppetlabs-stdlib to version 4.5.1 or later, or upgrade Puppet beyond version 2.8.8 to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
StdlibApplication
Affected:= 2.1.0= 2.1.1= 2.1.2= 2.1.3= 2.2.0= 2.2.1= 2.3.0= 2.3.1= 2.3.2= 2.3.3= 2.4.0= 2.5.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed puppetlabs-stdlib module version
    Run 'puppet module list' or check the module metadata in the Puppet modulepath to find the installed version of puppetlabs-stdlib
    Affected if The installed version matches 2.1.0 through 3.0, or 4.1.0 through 4.5.x
  2. Identify the Puppet version
    Run 'puppet --version' to determine the Puppet master or agent version
    Affected if Puppet version is 2.8.8 or earlier
  3. Confirm fact caching is enabled
    Inspect Puppet configuration files (puppet.conf) for the 'factsync' setting or any fact cache related configuration under the [master] or [agent] sections
    Affected if Fact caching or fact synchronization is enabled in the Puppet configuration
  4. Assess network exposure
    Review network access controls and authentication settings for the Puppet master to determine if remote authenticated users can submit custom facts
    Affected if The Puppet master accepts authenticated remote connections without strict fact submission controls

You are affected if your environment runs Puppet 2.8.8 or earlier with puppetlabs-stdlib version 2.1-3.0 or 4.1.0-4.5.x and has fact caching enabled with accessible Puppet master services.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade puppetlabs-stdlib to version 4.5.1 or later, or upgrade Puppet beyond version 2.8.8 to remediate this vulnerability.

Fix this in Stdlib Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-1029 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-1029 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data