CVE-2018-6513: Puppet Enterprise 2016.4.x prior to 2016.4.12, Puppet Enterprise 2017.3.x prior to 2017.3.7, Puppet Enterprise

This month

HIGH 8.8UPGRADEUPGRADE

CVE-2018-6513 is a high-severity flaw (CVSS 8.8) affecting puppet, puppet enterprise. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

Puppet 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, Puppet 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, were vulnerable to an attack where an unprivileged user on Windows agents could write custom facts that can escalate privileges on the next puppet run. This was possible through the loading of shared

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	1.1% (top 34%)
CISA exploited list	No
Weakness	CWE-426
Published	2018-06-11
Last modified	2026-06-17

Publisher (CNA): Perforce · Vendor: puppet

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-06-11 20:29 UTCPublished CVE record published
2026-06-17 02:01 UTCUpdated Record last modified

puppet puppet UPGRADE

Affected: >= 1.10.0 and < 1.10.13 · >= 5.3.0 and < 5.3.7 · >= 5.5.0 and < 5.5.2

Fixed in: 1.10.13, 5.3.7, 5.5.2

Safe to downgrade to: a release before 1.10.0

1. Check installed version

apt-cache policy puppet || rpm -q puppet || puppet --version

2. UPGRADE to 1.10.13 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade puppet

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade puppet

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 1.10.0 (Debian / Ubuntu)

apt-cache madison puppet sudo apt install puppet=<VERSION_BEFORE_1.10.0> sudo apt-mark hold puppet

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list puppet sudo dnf downgrade puppet-<VERSION_BEFORE_1.10.0> sudo dnf versionlock add puppet

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

puppet puppet enterprise UPGRADE

Affected: >= 2016.4.0 and < 2016.4.12 · >= 2017.3.0 and < 2017.3.7 · >= 2018.1.0 and < 2018.1.1

Fixed in: 2016.4.12, 2017.3.7, 2018.1.1

Safe to downgrade to: a release before 2016.4.0

1. Check installed version

apt-cache policy puppet-enterprise || rpm -q puppet-enterprise || puppet-enterprise --version

2. UPGRADE to 2016.4.12 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade puppet-enterprise

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade puppet-enterprise

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 2016.4.0 (Debian / Ubuntu)

apt-cache madison puppet-enterprise sudo apt install puppet-enterprise=<VERSION_BEFORE_2016.4.0> sudo apt-mark hold puppet-enterprise

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list puppet-enterprise sudo dnf downgrade puppet-enterprise-<VERSION_BEFORE_2016.4.0> sudo dnf versionlock add puppet-enterprise

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2018-6513?

puppet: upgrade to 1.10.13, 5.3.7, 5.5.2; puppet enterprise: upgrade to 2016.4.12, 2017.3.7, 2018.1.1. Exact commands for each OS are on this page.

Is CVE-2018-6513 being exploited?

CVE-2018-6513 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2018-6513 affect?

CVE-2018-6513 affects puppet, puppet enterprise. Severity is high (CVSS 8.8). Puppet 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, Puppet 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

How urgent is CVE-2018-6513?

Priority 47/100. High severity

Software pages

Windows vulnerabilities

Related CVEs

CVE-2021-27026 MEDIUM 4.4 UPGRADE UPGRADE A flaw was divered in Puppet Enterprise and other Puppet products where sensitive plan parameters may be logge
CVE-2021-27025 MEDIUM 6.5 UPGRADE UPGRADE A flaw was discovered in Puppet Agent where the agent may silently ignore Augeas settings or may be vulnerable
CVE-2021-27022 MEDIUM 4.9 UPGRADE UPGRADE A flaw was discovered in bolt-server and ace where running a task with sensitive parameters results in those s
CVE-2021-27021 HIGH 8.8 UPGRADE UPGRADE A flaw was discovered in Puppet DB, this flaw results in an escalation of privileges which allows the user to
CVE-2020-7942 MEDIUM 6.5 UPGRADE UPGRADE Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in

References

← Back to latest CVEs