How severe is CVE-2017-2299?

CVE-2017-2299 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.

Is CVE-2017-2299 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2017-2299?

CVE-2017-2299 primarily affects Puppet Puppetlabs-apache. In total, 26 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.

How do I fix CVE-2017-2299?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

When was CVE-2017-2299 published?

CVE-2017-2299 was published on 2017-09-15 and last updated on 2026-06-17.

CVE-2017-2299

CVE-2017-2299 is a high-severity vulnerability in Puppet Puppetlabs-apache with a CVSS 3.x base score of 7.5. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-295.

Key facts

Severity: High (CVSS 3.x base score 7.5)
CVSS v2: 5.0
EPSS exploit prediction: 1% (54th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-295
Affected product: Puppet Puppetlabs-apache
Published: 2017-09-15
Last modified: 2026-06-17

Description

Versions of the puppetlabs-apache module prior to 1.11.1 and 2.1.0 make it very easy to accidentally misconfigure TLS trust. If you specify the `ssl_ca` parameter but do not specify the `ssl_certs_dir` parameter, a default will be provided for the `ssl_certs_dir` that will trust certificates from any of the system-trusted certificate authorities. This did not affect FreeBSD.

Frequently asked questions

What is CVE-2017-2299?: Versions of the puppetlabs-apache module prior to 1.11.1 and 2.1.0 make it very easy to accidentally misconfigure TLS trust. If you specify the `ssl_ca` parameter but do not specify the `ssl_certs_dir` parameter, a default will be provided for the `ssl_certs_dir` that will trust certificates from any of the system-trusted certificate authorities. This did not affect FreeBSD.
How severe is CVE-2017-2299?: CVE-2017-2299 has a CVSS 3.x base score of 7.5, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity none, and availability none.
Is CVE-2017-2299 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2017-2299?: CVE-2017-2299 primarily affects Puppet Puppetlabs-apache. In total, 26 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2017-2299?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2017-2299 published?: CVE-2017-2299 was published on 2017-09-15 and last updated on 2026-06-17.

References

Affected products (26)

cpe:2.3:a:puppet:puppetlabs-apache:0.0.4:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.4.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.6.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.7.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.8.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.8.1:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.9.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.10.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:0.11.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.0.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.0.1:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.1.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.1.1:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.2.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.3.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.4.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.4.1:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.5.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.6.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.7.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.7.1:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.8.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.8.1:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.10.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:1.11.0:*:*:*:*:puppet:*:*
cpe:2.3:a:puppet:puppetlabs-apache:2.0.0:*:*:*:*:puppet:*:*

Other CWE-295 (Improper Certificate Validation) vulnerabilities

CVE-2026-4370 — Critical (CVSS 10.0): A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the…
CVE-2026-30836 — Critical (CVSS 10.0): Step CA is an online certificate authority for secure, automated certificate management for DevOps. Versions 0.30.0-rc6…
CVE-2025-68121 — Critical (CVSS 10.0): During session resumption in crypto/tls, if the underlying Config has its ClientCAs or RootCAs fields mutated between…
CVE-2022-20703 — Critical (CVSS 10.0): Multiple vulnerabilities in Cisco Small Business RV160, RV260, RV340, and RV345 Series Routers could allow an attacker…
CVE-2021-1471 — Critical (CVSS 9.9): Multiple vulnerabilities in Cisco Jabber for Windows, Cisco Jabber for MacOS, and Cisco Jabber for mobile platforms…
CVE-2026-20184 — Critical (CVSS 9.8): A vulnerability in the integration of single sign-on (SSO) with Control Hub in Cisco Webex Services could have allowed…

Browse all CWE-295 (Improper Certificate Validation) vulnerabilities →