Skip to content
Fencer Intel
high 7.5

CVE-2017-2299 json

Versions of the puppetlabs-apache module prior to 1.11.1 and 2.1.0 make it very easy to accidentally misconfigure TLS trust.

published 2017-09-15 9 y ago modified 2026-06-17 4 mo ago also EUVD-2017-11482

cvss
7.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

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.

Patch / fix

  • puppet-module-puppetlabs-apache Debian 13, Debian 12 3.0.0-1

debian advisories DEBIAN-CVE-2017-2299

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2017-2299 updated cvss 7.5

puppet-apache: Possible TLS trust misconfiguration in puppetlabs-apache

  • Red Hat OpenStack Platform 10 (Newton) puppet-apache Red Hat OpenStack Platform 11 (Ocata) puppet-apache
    affected: no fix planned “Will not fix”
  • Red Hat OpenStack Platform 12 (Pike) puppet-apache Red Hat Satellite 6 puppet, puppet-server
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.85% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.0 7.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:P/I:N/A:N

Affected products

  • Puppet puppetlabs-apache

Classification

Weakness
  • CWE-295 Improper Certificate Validation

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.