Improper certificate validation in Puppet Discovery
Priority MEDIUM 43CWE-295Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 3.0 · NVD. Fix status from CNA. Impact type from CWE-295.
Summary
Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container. In version 1.4.0, a unique certificate will be generated on installation or the user will be able to provide their own TLS certificate for ingress.
Why it matters now
EPSS 0.00724 54th percentileScored 2026-11-07
Fix Fixed Puppet Discovery (Puppet): 1.4.0
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
Remediation
- Fix · CNA Puppet Discovery (Puppet) Fixed in 1.4.0
Timeline
- 2026-10-02 Threatist record created from CVE-2018-11747
- 2026-10-03 Alias added: GHSA-x45j-4g47-7hxx
References
More Puppet Discovery vulnerabilities
- TI-2018-08406 Puppet Discovery can leak authentication information CVSS 3.0CRITICAL 9.8
Sources
- CVE-2018-11747 · CVE Program
- CVE-2018-11747 · NVD
- FIRST EPSS
- GHSA-x45j-4g47-7hxx · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences