CVE-2020-7942

mediumpriority · track · 26EPSS 0.008 · 56 %ileEURUUS

grimoire priorityP3 · Track

Exploitable?

—

no known exploitation

Likely / severe?

0.80% (56th) EPSS

CVSS 4 · medium

Is it mine?

18 products

Check your exposure

Who says so?

5 sources

cnnvd · enisa_euvd · fstec_bdu · nvd

EPSS · scored 2026-10-27

Previously, Puppet operated on a model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 and 5.5.19 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior. Affected software versions: Puppet 6.x prior to 6.13.0 Puppet Agent 6.x prior to 6.13.0 Puppet 5.5.x prior to 5.5.19 Puppet Agent 5.5.x prior to 5.5.19 Resolved in: Puppet 6.13.0 Puppet Agent 6.13.0 Puppet 5.5.19 Puppet Agent 5.5.19

cvss

Technical severity, 0–10. One row per scoring source.

6.5

010

base score 0–10 · higher = more severe · hover a vector to decode

v2.04mediumAV:N/AC:L/Au:S/C:P/I:N/A:Nprimary · NVD / NIST USexploitability 8 · impact 2.9

v3.16.5mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Nprimary · NVD / NIST USexploitability 2.8 · impact 3.6

v3.16.5mediumAV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Nsecondary · FSTEC (BDU) RU

v3.16.5mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:Nsecondary · OSV

v3.16mediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:Usecondary · CVSS-BT (t0sche)

weaknesses

The CWE weakness classes this flaw belongs to.

CWE-295USprimaryCWE-295USCWE-295US

affected products (18)

Products and version ranges known to be affected.

Puppet Puppet≤ 6.x prior to 6.13.0enisa_euvdEU
Puppet Puppet≤ 5.5.x prior to 5.5.19enisa_euvdEU
Puppet Puppet≤ Fixed in 6.13.0enisa_euvdEU
Puppet Puppet≤ Fixed in 5.5.19enisa_euvdEU
Puppet Puppet Agent≤ Fixed in 6.13.0enisa_euvdEU
Puppet Puppet Agent≤ 5.5.x prior to 5.5.19enisa_euvdEU
Puppet Puppet Agent≤ 6.x prior to 6.13.0enisa_euvdEU
Puppet Puppet Agent≤ Fixed in 5.5.19enisa_euvdEU
Puppet Labs Puppet5.5.0 → 5.5.19fstec_bduRU
Puppet Labs Puppet6.0 → 6.13.0fstec_bduRU
Puppet Labs Puppet Agent5.5.0 → 5.5.19fstec_bduRU
Puppet Labs Puppet Agent6.0 → 6.13.0fstec_bduRU
puppet puppet5.5.0 → 5.5.19nvdUScpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*
puppet puppet6.0.0 → 6.13.0nvdUScpe:2.3:a:puppet:puppet:*:*:*:*:*:*:*:*
puppet puppet agent5.5.0 → 5.5.19nvdUScpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*
puppet puppet agent6.0.0 → 6.13.0nvdUScpe:2.3:a:puppet:puppet_agent:*:*:*:*:*:*:*:*
RubyGems puppet< 5.5.19osvUSpkg:gem/puppet
RubyGems puppet6.0.0 → 6.13.0osvUSpkg:gem/puppet

advisories (1)

Vendor and ecosystem advisories describing this.

GHSA-gqvf-892r-vjm5Improper Certificate Validation in Puppet2021-04-13ghsa · osvUS
Previously, Puppet operated on the model that a node with a valid certificate was entitled to all information in the system and that a compromised certificate allowed access to everything in the infrastructure. When a node's catalog falls back to the `default` node, the catalog can be retrieved for a different node by modifying facts for the Puppet run. This issue can be mitigated by setting `strict_hostname_checking = true` in `puppet.conf` on your Puppet master. Puppet 6.13.0 changes the default behavior for strict_hostname_checking from false to true. It is recommended that Puppet Open Source and Puppet Enterprise users that are not upgrading still set strict_hostname_checking to true to ensure secure behavior.

also known as (4)

Other names and identifiers for this entity.

sources

Which sources assert this record, and when.

cnnvd enisa_euvd fstec_bdu nvd osv NVD CVE.org MITRE

published 2020-02-19modified 2026-06-17

related (1,894)

Related entries.

ID	severity	EPSS	exploitable	published
CVE-2026-85102US	—OT critical	54.1% (99th)	KEV	2026-09-09
Improper certificate trust validation during VPN negotiation in Check Point Quantum Security Gateway may allow an unauthenticated remote attacker to execute arbitrary code on the G…
CVE-2023-41991US	medium5.5OT critical	13.4% (96th)	KEV	2023-09-21
A certificate validation issue was addressed. This issue is fixed in macOS Ventura 13.6, iOS 16.7 and iPadOS 16.7. A malicious app may be able to bypass signature validation. Apple…
CVE-2023-20963US	high7.8OT critical	1.47% (74th)	KEV	2023-03-24
In WorkSource, there is a possible parcel mismatch. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed…
CVE-2022-26923US	high9.0OT critical	83.5% (100th)	KEV	2022-05-10
Active Directory Domain Services Elevation of Privilege Vulnerability
CVE-2022-20703US	high8.0OT critical	9.20% (95th)	KEV	2022-02-10
Multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker to do any of the following: Execute arbitrary code Elevate pr…

+1889 more

references (8)

External citations — patches, advisories, analysis.

scry

Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.

Free scan