LiveActive security incident?Get immediate response
CVE Record

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

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Older Puppet Discovery deployments used the same default TLS certificate in the nginx container. That weakens the assurance users expect from encrypted access because a certificate meant to identify one deployment may not be unique. Puppet changed this in version 1.4.0 so installations generate a unique certificate or allow a user-provided ingress certificate.

Executive priority

Prioritize remediation if Puppet Discovery is still deployed and reachable outside trusted administration networks. The fix path is clear, but public evidence does not show active exploitation or a critical severity rating.

Technical view

CVE-2018-11747 affects Puppet Discovery versions before 1.4.0. The issue is a default generated TLS certificate shipped in the nginx container. The public record does not provide CVSS, CWE, exploit details, or broader impact analysis. Version 1.4.0 changes certificate handling to generate a unique certificate on installation or support a supplied TLS certificate for ingress.

Likely exposure

Exposure is limited to organizations running Puppet Discovery before version 1.4.0, especially where its ingress or administrative interface is reachable by untrusted networks. Evidence does not identify other Puppet products as affected.

Exploitation context

The source bundle does not report active exploitation, public exploit code, or KEV listing. Practical risk depends on network reachability and whether the default certificate remains in use. Treat this as a trust and deployment-hardening issue rather than a confirmed remotely exploited vulnerability.

Researcher notes

The public data is sparse: no CVSS vector, CWE, proof-of-concept, or detailed attack narrative is provided. Analysis should focus on confirming old Puppet Discovery deployments, certificate reuse, ingress reachability, and whether version 1.4.0 certificate behavior is present.

Mitigation direction

  • Upgrade Puppet Discovery to version 1.4.0 or later.
  • Replace any default or reused TLS certificate with a unique certificate.
  • Use an organization-managed TLS certificate for ingress where appropriate.
  • Restrict network access to Puppet Discovery ingress during remediation.
  • Check Puppet guidance for any environment-specific remediation notes.

Validation and detection

  • Inventory Puppet Discovery instances and record installed versions.
  • Confirm no production instance remains below version 1.4.0.
  • Inspect ingress/nginx TLS certificates for default or reused certificate material.
  • Verify each deployment uses a unique generated or user-provided certificate.
  • Review external exposure of Puppet Discovery administrative access.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Container behavior lookup

The affected technology mentions containers, so container-specific ATT&CK technique review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-11747 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
PuppetPuppet Discoveryall versions prior to 1.4.0Listed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.