dbcve.org
Ubuntu LinuxOperating system · Canonical

CVE-2013-3567

HIGH · 7.5 CVSS v2.0 Published 2013-08-19
Fix available
A fix is available. Upgrade to after 2.8.1 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
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 attackers to instantiate arbitrary Ruby classes and execute arbitrary code via a crafted REST API call.

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 · high confidence

Puppet's REST API deserializes YAML without proper validation, allowing remote attackers to send crafted YAML that instantiates arbitrary Ruby classes and executes arbitrary code.

MitigationUpgrade Puppet to version 2.7.22, 3.2.2, or 2.8.2 or later. Until patched, restrict network access to the Puppet REST API.

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
Ubuntu LinuxOperating system
Affected:= 12.04= 12.10= 13.04
Suse Linux Enterprise ServerOperating system
Affected:= 11.0
PuppetApplication
Affected:= 2.7.2= 2.7.10= 2.7.11= 2.7.12= 2.7.13= 2.7.14= 2.7.16= 2.7.17= 2.7.18= 2.7.21= 3.2.1
PuppetApplication
Affected:= 2.7.0= 2.7.1= 2.7.19= 2.7.20= 3.2.0= 1.0.0= 1.1.0= 1.2.0= 2.5.0= 2.6.0= 2.7.2
Suse Linux Enterprise DesktopOperating system
Affected:= 11= 11.0
Puppet EnterpriseApplication
Affected:<= 2.8.1= 1.0= 1.1= 1.2.0= 2.0.0= 2.5.1= 2.5.2= 2.8.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
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/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 installed Puppet version
    Run 'puppet --version' or check the installed package via 'dpkg -l puppet' (Debian/Ubuntu), 'rpm -qa puppet' (RHEL/SUSE), or check the Gem version with 'gem list puppet'
    Affected if The installed version matches one of the affected versions listed: Puppet 2.7.x before 2.7.22, Puppet 3.2.x before 3.2.2, Puppet 2.8.x before 2.8.2, Puppet Enterprise <= 2.8.1, or specific point releases like 1.0.0, 1.1.0, 1.2.0, 2.0.0, 2.5.0, 2.5.1, 2.5.2, 2.6.0, 2.7.2, 3.2.0, 3.2.1
  2. Check if Puppet master or Puppet server is running
    Run 'ps aux | grep puppet' or check for the master process, and verify port 8140 is listening with 'netstat -tlnp | grep 8140' or 'ss -tlnp | grep 8140'
    Affected if A Puppet master/server process is running and exposing the REST API on port 8140 or another port
  3. Verify Puppet REST API network accessibility
    Check firewall rules and network configuration to determine if the Puppet master port (default 8140) is accessible from untrusted networks. Review /etc/puppet/puppet.conf for 'listen = true' setting under the [master] section
    Affected if The Puppet REST API port is exposed to network segments that are not fully trusted, or the 'listen' setting is enabled allowing REST API access
  4. Confirm YAML deserialization endpoint is active
    Examine Puppet configuration files in /etc/puppet/ for auth.conf rules and verify the REST API endpoints are not restricted to localhost only. Check if the master is configured to accept YAML reports or external node classifier connections
    Affected if The Puppet REST API accepts YAML submissions from remote clients without additional network-level restrictions

A system is affected if it runs a vulnerable Puppet version (2.7.x before 2.7.22, 3.2.x before 3.2.2, 2.8.x before 2.8.2, or Puppet Enterprise <= 2.8.1) AND has the REST API network-accessible to untrusted clients.

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
Upgrade available Upgrade to a release after 2.8.1
Interim mitigation

Upgrade Puppet to version 2.7.22, 3.2.2, or 2.8.2 or later. Until patched, restrict network access to the Puppet REST API.

Fix this in Ubuntu Linux Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3567 — 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-2013-3567 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