CVE-2017-2299
Last modified
CVE-2017-2299 is a vulnerability of currently unknown severity. 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. EPSS estimates a 0.85% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Puppet | Puppetlabs-Apache | 0.0.4 |
| Puppet | Puppetlabs-Apache | 0.4.0 |
| Puppet | Puppetlabs-Apache | 0.6.0 |
| Puppet | Puppetlabs-Apache | 0.7.0 |
| Puppet | Puppetlabs-Apache | 0.8.0 |
| Puppet | Puppetlabs-Apache | 0.8.1 |
| Puppet | Puppetlabs-Apache | 0.9.0 |
| Puppet | Puppetlabs-Apache | 0.10.0 |
| Puppet | Puppetlabs-Apache | 0.11.0 |
| Puppet | Puppetlabs-Apache | 1.0.0 |
| Puppet | Puppetlabs-Apache | 1.0.1 |
| Puppet | Puppetlabs-Apache | 1.1.0 |
| Puppet | Puppetlabs-Apache | 1.1.1 |
| Puppet | Puppetlabs-Apache | 1.2.0 |
| Puppet | Puppetlabs-Apache | 1.3.0 |
| Puppet | Puppetlabs-Apache | 1.4.0 |
| Puppet | Puppetlabs-Apache | 1.4.1 |
| Puppet | Puppetlabs-Apache | 1.5.0 |
| Puppet | Puppetlabs-Apache | 1.6.0 |
| Puppet | Puppetlabs-Apache | 1.7.0 |
| Puppet | Puppetlabs-Apache | 1.7.1 |
| Puppet | Puppetlabs-Apache | 1.8.0 |
| Puppet | Puppetlabs-Apache | 1.8.1 |
| Puppet | Puppetlabs-Apache | 1.10.0 |
| Puppet | Puppetlabs-Apache | 1.11.0 |
| Puppet | Puppetlabs-Apache | 2.0.0 |
References
- http://www.securityfocus.com/bid/100859Third Party Advisory, VDB Entry
- https://puppet.com/security/cve/CVE-2017-2299Vendor Advisory
- http://www.securityfocus.com/bid/100859Third Party Advisory, VDB Entry
- https://puppet.com/security/cve/CVE-2017-2299Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2017-2299?
How severe is CVE-2017-2299?
How do I fix CVE-2017-2299?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2017
- CVE-2017-2293Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 …
- CVE-2017-2294Versions of Puppet Enterprise prior to 2016.4.5 or 2017.2.1 …
- CVE-2017-2295Versions of Puppet prior to 4.10.1 will deserialize data off…
- CVE-2017-2296In Puppet Enterprise 2017.1.x and 2017.2.1, using specially …
- CVE-2017-2297Puppet Enterprise versions prior to 2016.4.5 and 2017.2.1 di…
- CVE-2017-2298The mcollective-sshkey-security plugin before 0.5.1 for Pupp…6.5
- CVE-2017-2300On Juniper Networks SRX Series Services Gateways chassis clu…
- CVE-2017-2301On Juniper Networks products or platforms running Junos OS 1…
- CVE-2017-2302On Juniper Networks products or platforms running Junos OS 1…
- CVE-2017-2303On Juniper Networks products or platforms running Junos OS 1…
- CVE-2017-2304Juniper Networks QFX3500, QFX3600, QFX5100, QFX5200, EX4300 …
- CVE-2017-2305On Juniper Networks Junos Space versions prior to 16.1R1, du…
Are you affected by CVE-2017-2299?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
